I don't know if this is relevant info or not but activity B is a
Theme.Dialog.  When user rotates the orientation with B in the
foreground, I could see A getting destroyed and recreated because part
of B is translucent.

Now even if the new B knows about the old A, it might not know about
the new A.  Is my logic correct?

On Nov 24, 1:24 pm, j <[EMAIL PROTECTED]> wrote:
> W/dalvikvm( 4397): threadid=3: thread exiting with uncaught exception
> (group=0x4
> 0013e28)
> E/AndroidRuntime( 4397): Uncaught handler: thread main exiting due to
> uncaught exception
> E/AndroidRuntime( 4397): java.lang.RuntimeException: Failure
> delivering result ResultInfo{who=null, request=1, result=-1,
> data=Intent { action=orative }} to act
> ivity {com.uc.umc/com.uc.umc.HomeScreen}:
> java.lang.NullPointerException
> E/AndroidRuntime( 4397):        at
> android.app.ActivityThread.deliverResults(ActivityThread.java:2839)
> E/AndroidRuntime( 4397):        at
> android.app.ActivityThread.handleSendResult(ActivityThread.java:2881)
> E/AndroidRuntime( 4397):        at android.app.ActivityThread.access
> $2300(ActivityThread.java:112)
> E/AndroidRuntime( 4397):        at android.app.ActivityThread
> $H.handleMessage(ActivityThread.java:1608)
> E/AndroidRuntime( 4397):        at android.os.Handler.dispatchMessage
> (Handler.java:88)
> E/AndroidRuntime( 4397):        at android.os.Looper.loop(Looper.java:
> 123)
> E/AndroidRuntime( 4397):        at android.app.ActivityThread.main
> (ActivityThread.java:3742)
> E/AndroidRuntime( 4397):        at
> java.lang.reflect.Method.invokeNative(NativeMethod)
> E/AndroidRuntime( 4397):        at java.lang.reflect.Method.invoke
> (Method.java:515)
> E/AndroidRuntime( 4397):        at com.android.internal.os.ZygoteInit
> $MethodAndArgsCaller.run(ZygoteInit.java:739)
> E/AndroidRuntime( 4397):        at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:497)
> E/AndroidRuntime( 4397):        at dalvik.system.NativeStart.main
> (Native Method)
>
> On Nov 24, 12:29 pm, "Dianne Hackborn" <[EMAIL PROTECTED]> wrote:
>
> > What is the stack crawl of the crash?
>
> > On Mon, Nov 24, 2008 at 11:57 AM, j <[EMAIL PROTECTED]> wrote:
>
> > > I have this scenario:
> > > 1) activity A starts activity B via startActivityForResult.
> > > 2) User changes orientation which triggered activity B to be destroyed
> > > and its onCreate method to be called a second time.
> > > 3) Activity B calls setResult(...) and that crashes.
>
> > > It seems activity B no longer knows who to return to the result to.
> > > Is it possible to save info into the Bundle via  onSaveInstanceState
> > > so that activity B can remember who called it?
>
> > --
> > Dianne Hackborn
> > Android framework engineer
> > [EMAIL PROTECTED]
>
> > Note: please don't send private questions to me, as I don't have time to
> > provide private support.  All such questions should be posted on public
> > forums, where I and others can see and answer them.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to