(To the OP)
I may be missing something here, but why do you use a cached reference to
package B's context?
I believe you said that trying to grab the context after B has been
uninstalled fails, as expected - so why not use this as a test to see
whether A should be allowed to go ahead and use those assets? Why not try
and grab B's context afresh each time you want to access the files, and
avoid trying to do so if the grab fails?
If it's for performance reasons, you could at least try and re-grab it every
15 minutes - that wouldn't be such a bad hit.
Presumably if A is already using those assets while B is being uninstalled,
you wouldn't want the code to just die - package A should at least be
allowed to finish what it was doing; and if it is hogging those assets for a
long period of time... that sounds like an area that could do with a little
reconsideration as well.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
