https://bugzilla.novell.com/show_bug.cgi?id=645603
https://bugzilla.novell.com/show_bug.cgi?id=645603#c1 Mike Kestner <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|[email protected] |[email protected] Severity|Major |Critical --- Comment #1 from Mike Kestner <[email protected]> 2010-10-13 22:51:06 UTC --- Your sample contains an incorrectly written AndroidManifest for using a custom application class. When I update it to a correct format: <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android"; package="test_CustomAppClass.test_CustomAppClass" android:versionCode="1" android:versionName="1.0"> <application android:name="test_CustomAppClass.CustomApplication" android:label="Test_CustomAppClass"> </application> <uses-sdk android:minSdkVersion="4" /> </manifest> I get a crash on startup, since we are only initializing the runtime for Activity instances thus far. So Jon, it looks like we need to initialize in Application subclass java stubs too, as they can be instantiated and onCreate executed prior to the creation of the first activity. We might even be able to use this as an improvement to our initialization mechanism, always create an Application subclass in java regardless of whether the user creates one, and then use it to do the runtime initialization instead of duplicating it on all the activity, service, etc... subclasses. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
