More just feeling out the community/wondering if anyone has seen this
than concerned about our issue, our fix works and has yet to fail.
I may file a bug -- but why at this point, whither goest thou, oh
Honeycomb? ;)
Actually, I am just too busy to write a simple case and try to
reproduce this atm
Situation:
Activity One sends a non-null String via Intent and
startActivityForResult() (won't execute/send if it's null -- we
verified this)
Activity two starts and calls an internal AsyncTask which uses
`Activity.this.getIntent().getExtras().getString(<key>)` as a
parameter for an object
This fails intermittently (sometimes yes, sometimes no)
Insert these three lines of code above the Object instantiation :
Intent i = Activity.this.getIntent();
Bundle b = i.getExtras();
String filename = b.getString(<key>);
And it has yet to receive null.
I decided to place those three lines of code in onCreate and use a
String field instead of accessing the Activity's Intent within
doInBackground and have yet to encounter the issue since doing so.
Anyone encountered this particular situation?
Peace,
Dan
--
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
