We are using dependency injection in such a way that we want to use the process we are running in to determine which modules we inject when constructing our android.app.Application. Unfortunately, ActivityManager.getRunningAppProcesses() is not a reliable source of information. Normally, we try to iterate over that list and match it up with the value of android.os.Process.myPid(), but in the wild, we've gotten quite a few error reports (even on newer phones running JellyBean) that there is no match in the list. It's unclear whether this is a race condition or just a lot of people running some rogue version of Android, but given the volume of the reports, we doubt it is the latter.
Normally, you know which process you are in by virtue of which Activity or Service is running. Unfortunately, this does not work in our case because we need to know this when our Application is being constructed, which happens before the Activity or Service is created. Are there any known workarounds to this issue? Thank you, Michael -- 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
