Android Question State Manager - Statemgr

Can you reproduce it in a small project?

Hi Erel,
I've tried to create a small program that reproduces the problem, but it works perfectly...
In my large application, it fails sporadically, using exactly the same steps with exactly the same data, it will work, then doing it again, it will not work.
I've narrowed it down to when my application goes through Activity_Pause (with Statemanager) and runs another activity; upon return it goes through Activity_Resume (with Statemanager)

In my small program, I traced the StateManager and it doesn't appear to store and retrieve anything except VIEWS, is this correct?

The problem array that is not being restored (or kept in-tact) reliably is a large type structure of many arrays, populated with data.

I declare the type structure in Process_Globals.
(To test, I declared the array with a dimension of 2 and then later re-dimensioned it to i.e. 17 or 40 or whatever depending upon live data)

When I start another activity from MAIN, the array is OK (has many elements); when I get into the NEW activity, the array is OK; upon NEW activity finish, the array is OK; upon MAIN activity_resume, the array is back to the original (empty) dimensions.

Your help is greatly appreciated.
Rusty

I might add that this program has been running for about 4 or 5 years with the existing statemanager code and it has never failed before.

Rusty said:

In my small program, I traced the StateManager and it doesn't appear to store and retrieve anything except VIEWS, is this correct?

Click to expand...

Yes. It only stores the views state.

For StateManager to work properly the order of views must always be exactly the same.

Thanks Erel,
Have you ever seen an issue where a large type structure array gets "corrupted" or re-set upon activity_resume from another activity (that does not even refer to the array in question)?
Rusty

No. Make sure to use a different activity name for each activity.