ListPreference error when I changeSelectionListener

[Yamur]

Hi,

I have the code from MainActivity to select different map types. Once I select the map type I got an error. How could I fix it?

[USER=1021285]@override[/USER]
public void onCreate(Bundle savedInstanceState) {
  super.onCreate(savedInstanceState);
  addPreferencesFromResource(R.xml.pref_map_layers);
  setHasOptionsMenu(true);

  mapMessagesHandler.getMapLayers();

  final ListPreference listPreference = (ListPreference) findPreference("maps_list");

  if(listPreference != null) {
    HashMap<Integer, String> mapsList = MapManager.getMaps();

    for(final int value : mapsList.keySet()) {

      listPreference.setSummary(mapsList.get(value));
      listPreference.setOnPreferenceChangeListener(new Preference.OnPreferenceChangeListener() {
        [USER=1021285]@override[/USER]
        public boolean onPreferenceChange(Preference preference, Object newValue) {
          MapManager.setSelectedMapInstance(value);
          preference.setSummary(listPreference.getEntry().toString());
          return true;
        }
      });
    }
  } else {
    logger.error("No map to select");
  }
}

 

[Yamur]

When I call MapManager.setSelectedMapInstance(value) I got always error. How could I fix it?

 

[Unforgiven]

Development thread moved to the dev area for better exposure.

 

[Deleted User]

What's the error?

 

[Yamur]

The error that when I select one of items I got an error. The XML file as below.

  <PreferenceCategory>

    <ListPreference android:key="maps_list"
                    android:en
                    android:defaultValue="3" />

  </PreferenceCategory>

 

[Deleted User]

The error that when I select one of items I got an error.

and the error is...?

 

[Yamur]

and the error is...?

Once I select one of the items in the preferred list I got

AndroidRuntime: FATAL EXCEPTION: main Process: com.mobilaris.eunomia.client, PID: 2998 java.lang.IllegalStateException: ListPreference requires an entries array and an entryValues array.

 

[Deleted User]

Getting closer. Now we just need a full stack trace, not just one line because that provides no context to your code.
The full stack trace can be found in your Logcat view, and tells us what sequence of method calls produced your error.
And we also need to see the corresponding code, with accurate line numbers, matching up to the stack trace.