Thank you for your reply. > "bug #1" may be related to this: > http://code.google.com/p/android/issues/detail?id=2373
I do not know. That post says: "This only happens when launching the app from Eclipse" My bug, on the other hand, is 100% reproducible by every user. Just launch the app from the installer, press home, launch it again and you have it. > I am assuming you are referring to stuff like this: > https://github.com/cleverua/android_startup_activity Yes. Thank you. Spent the whole Sunday googling, but missed that post. Now I will try to apply that approach in NotePad sample. > it does not occur in too many places -- > most people would encounter it after upgrading the app, as I > understand it. No. After the first installation as well. Other people also report it when the application is launched by other sources, such as a browser. Basically, a single instance of application is created when it is launched only by a single place, such as icon in Home screen (this is what Kumar was doing). But if an application is launched by multiple places (Home screen, Installer, Browser, etc), then multiple instances are launched. Since Installer has that big "Open" button, which most users click, the bug is almost impossible to avoid. > There might be a better approach, using > ACTION_PACKAGE_REPLACED, but I haven't tried thinking it through. If you will come up with something, please, tell me. Application launch is the very first thing in lifecycle and it has to be done properly. Thank you John -- 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
