My application started having this problem after I updated the launcher activity with a different root package. Here's the sequence:
1) Install application on the phone with [com.package] as the path to my launcher activity. 2) Changed the path to be [com.package2] and updated the AndroidManifest.xml 3) Now some Hero phones are encountering the the bug you have described above with the icon. Somehow the old package path is being cached and you will get an exception when rebooting the phone Let me know if you did something similar where you installed your application on your phone and then changed it during later developments. On Oct 28, 4:21 pm, gdonald <gdon...@gmail.com> wrote: > On Oct 27, 9:35 am, "Mark Murphy" <mmur...@commonsware.com> wrote: > > > 1. Is this test phone a Sprint Hero (US), or a different Hero? > > Mine is a US Hero. > > > 2. What firmware are you running? The build number on my devices is: > > > 1.22.651.1 146733 CL62456 release-keys > > Mine has: 1.29.651.1 CL69164 release-keys > > > 3. Is the app that is giving you this behavior available for me to test to > > see if I get the same behavior? > > I'm waiting until I get this issue worked out before placing it in the > marketplace. First impressions, etc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
