Hello, I'm trying to find a workaround for the following bug:
http://code.google.com/p/android/issues/detail?id=5277 Short summary: installing an application from a .apk file and then running it with the 'Run' button in the Package Installer will cause the application to run subtly wrong, which can cause attempts to run the application to create multiple copies of the activity instead of resuming an existing instance. This is a very serious problem for us: our application is being distributed off-Market, so our users will see this workflow frequently. Can anyone suggest anything we can do to avoid the problem? Even something as crude as a way of suppressing the 'Run' button in the Package Installer would be fine. I've been trying to find out exactly what's going wrong, but not having much luck. The only difference I've seen is that the Home Screen starts my app with this: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=<myapplication> bnds=[98,227][172,327] } ...and the Package Installer starts it with this: Intent { act=android.intent.action.MAIN flg=0x10000000 cmp=<myapplication> } 0x200000 is FLAG_ACTIVITY_RESET_TASK_IF_NEEDED; 0x10000000 is FLAG_ACTIVITY_NEW_TASK. Any ideas? -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ life←{ ↑1 ⍵∨.^3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵ } │ --- Conway's Game Of Life, in one line of APL
signature.asc
Description: OpenPGP digital signature
