Ward Willats wrote: > So....I HOPE NO ONE EVER CHANGES THE ENTRY ACTIVITY OF THEIR PROGRAM > WHEN THEY ISSUE AN UPDATE OR THEIR USERS ARE GOING TO HAVE TO ERASE > THEIR PHONES.
I don't think it's quite that simple. I am able to somewhat reproduce this problem. I say "somewhat" because: 1. It only happens when I switch the LAUNCHER intent filter from Activity B back to Activity A (where A was the original activity with the intent filter) 2. It only fails once. I get the acore force-close dialog, and the desktop restarts, and then my app works fine, starting up Activity A Could you post your whole manifest, and point out the two activities you were switching between? -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
