Thanks dude.

Actually, I was expecting a better solution, but It seems there's no
one. I'll do what you suggested.


On Dec 16, 1:16 pm, Streets Of Boston <[email protected]> wrote:
> That happens on Honeycomb as well.
>
> I had this happen when i tried to create/add a fragment while the
> onActivityResult was executing (which is just before an onResume is called).
> I got around this by deferring the creation/adding the fragment until the
> onResume is called: just set a boolean field in the code that would need to
> create this fragment and query this boolean in the onResume and actually
> create the fragment if this boolean is true.

-- 
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