CODEWITHSUNDEEP
androidsharedpreferences
Ton
Ton

Reputation: 9806

SharedPreferences reads old values

I use SharedPreferences to write and later read values within different activities in my application. It used to work ok but lately it seems like it if wasn't sincronized. I mean, I write a value but then the other activity still reads the old value. Sometimes it works correcly. Any idea?

EDIT: This is a sample code:

First, from a thread:

SharedPreferences prefs = getSharedPreferences("MyPrefs", Context.MODE_PRIVATE);
SharedPreferences.Editor editor = prefs.edit();
editor.putInt("ComandToDo", value);
editor.commit();
... some code later:
alarmmanager.set(AlarmManager.RTC_WAKEUP, Miliseconds, sender);

In the alarm receiver:

SharedPreferences prefs = contexto.getSharedPreferences("MyPrefs", Context.MODE_PRIVATE);
int value = prefs.getInt("ComandToDo", -1);

And here comes the problem because "value" is not the value written in the thread.

Upvotes: 11

Views: 5136

Answers (4)

Sergei Bubenshchikov
Sergei Bubenshchikov

Reputation: 5371

Just use IntentService instead BroadcastReceiver. It`s work for me.

ServiceClass:

public class ServiceClass extends IntentService {

    public NotificationPopupService(String name) {
        super(name);
    }

    public NotificationPopupService(){
        super("YOU_DEFAULT_NAME");
    }

    @Override
    protected void onHandleIntent(Intent intent) {
        SharedPreferences sp = PreferenceManager.getDefaultSharedPreferences(getApplicationContext());

        do magic...
    }
}

In you AndroidManifest.xml file in application tag:

<service android:name="ServiceClass"/>

Create alarm:

intent = new Intent(context, ServiceClass.class);
pendingIntent = PendingIntent.getService(context, 0, intent, PendingIntent.FLAG_UPDATE_CURRENT);
// magic after 2 seconds after the creation of alarm
alarmManager.set(AlarmManager.RTC_WAKEUP, System.currentTimeMillis() + 2000, pendingIntent);

Upvotes: 0

Kapil Jituri
Kapil Jituri

Reputation: 1261

Here is what I encountered and what I did to fix it.

I was triggering an alarm from an Activity and in Broadcast-Receiver of that alarm I was updating Shared-Preferences which were read every time the app was launched.

After the alarm was triggered, whenever the app was launched it would get old values which were set from that activity only. No changes from Broadcast-Receiver were reflected.

The trick here is to set Shared-Preferences as MODE_MULTI_PROCESS

Generally we use MODE_PRIVATE, but do as follows:

SharedPreferences prefs = this.getSharedPreferences("Preferences", MODE_MULTI_PROCESS);

Note: After changing mode in code, it is advised to clear data of app to avoid issues while debugging.

EDIT: MODE_MULTI_PROCESS need min API 11

Before API 11 the workaround which I can think of is creating a database with 2 columns KEY & VALUE. This can be accessed from other modules.

Upvotes: 6

Munish Katoch
Munish Katoch

Reputation: 517

You are writing in "MyPrefs" preference file and then trying to read from "PerfilDeSonidoPreferencias" file. Please read/write from same preference file.

Upvotes: 0

full.stack.ex
full.stack.ex

Reputation: 1747

  1. SharedPreferences are documented not to work across processes, http://developer.android.com/reference/android/content/SharedPreferences.html, "Note: currently this class does not support use across multiple processes. This will be added later."

  2. This answer recommends encapsulation of data into a content provider, and the discussion also considers some other options, including shared SQLite: https://stackoverflow.com/a/5265556/1665128

  3. You also have plain old files in the file system. We used them in several projects, with locking, without any issues. May be an option for you as well.

Upvotes: 3

Related Questions