When I rotated the screen on the emulator (^F11) to test an app's layout I got a surprise. A different app I am working on crashed. This other app had never been launched since booting the emulator but it does have a service that starts on boot_completed, and which was sitting there quietly in the background doing nothing.
The reason for the crash, from the log, is that it couldn't find the layout resource for one of the app's launchable activities that does have a UI. That isn't surprising since I haven't yet provided a landscape layout for for that UI activity. But I had not launched it. Then when I went looking for the service component, I found that it had quit as well. Is this normal behavior? Why did the onCreate of the UI activity get called when it had never been launched? And, does this sort of crash always take out everything running in the same process, including services? Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
