Smells like there will be a pattern, such as they've all installed another app causing this and don't realise, or all have full internal memory etc.
On Aug 5, 10:18 am, Pent <[email protected]> wrote: > Hey Bob, > > thanks for taking the time. I was just coming to report that I noticed > A being destroyed after calling B, didn't expect that > possibility. Still don't know why it consistently picks on these > particular users but I'm happy anyway :) > > Pent > > On Aug 5, 8:50 am, Bob Kerns <[email protected]> wrote: > > > > > Activities can be destroyed to free memory. > > > Check out the left side of the activity lifecycle diagram here: > > >http://developer.android.com/intl/de/guide/topics/fundamentals.html#a... > > > On Aug 4, 10:50 pm, Pent <[email protected]> wrote: > > > > The order is: > > > > A: startActivityForResult( B ) > > > B: <dostuff>, call finish() > > > A: onCreate <---- what's this all about > > > A: onActivityResult > > > > This happens for a tiny minority of users. I havn't been able to > > > reproduce or find any common elements. A is the launch activity. > > > > <activity > > > android:name=".A" > > > android:label="A" > > > android:configChanges="orientation|keyboardHidden" > > > android:alwaysRetainTaskState="false" <--- default anyway > > > android:launchMode="singleTop" > > > > <activity > > > android:name=".B" > > > android:label="B" > > > /> > > > > Anyone recognize it ? > > > > Pent -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
