This bug was filed from the Socorro interface and is report bp-60a9b7da-c7cd-4bda-995d-c50af2141226. ============================================================= android.content.res.Resources$NotFoundException: Resource ID #0x7f03008c type #0x1 is not valid at android.content.res.Resources.loadXmlResourceParser(Resources.java:3915) at android.content.res.Resources.getLayout(Resources.java:2161) at android.view.LayoutInflater.inflate(LayoutInflater.java:413) at android.view.LayoutInflater.inflate(LayoutInflater.java:366) at org.mozilla.gecko.toolbar.BrowserToolbar.<init>(BrowserToolbar.java:190) at org.mozilla.gecko.toolbar.BrowserToolbarTabletBase.<init>(BrowserToolbarTabletBase.java:44) at org.mozilla.gecko.toolbar.BrowserToolbarNewTablet.<init>(BrowserToolbarNewTablet.java:38) at org.mozilla.gecko.toolbar.BrowserToolbar.create(BrowserToolbar.java:165) at org.mozilla.gecko.BrowserApp.onCreateView(BrowserApp.java:265) at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:734) at android.view.LayoutInflater.rInflate(LayoutInflater.java:813) at android.view.LayoutInflater.rInflate(LayoutInflater.java:821) at android.view.LayoutInflater.rInflate(LayoutInflater.java:821) at android.view.LayoutInflater.rInflate(LayoutInflater.java:821) at android.view.LayoutInflater.inflate(LayoutInflater.java:511) at android.view.LayoutInflater.inflate(LayoutInflater.java:415) at android.view.LayoutInflater.inflate(LayoutInflater.java:366) at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:428) at android.app.Activity.setContentView(Activity.java:2267) at org.mozilla.gecko.GeckoApp.onCreate(GeckoApp.java:1276) at org.mozilla.gecko.BrowserApp.onCreate(BrowserApp.java:509) at android.app.Activity.performCreate(Activity.java:6283) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2642) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2756) at android.app.ActivityThread.access$900(ActivityThread.java:177) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1448) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:145) at android.app.ActivityThread.main(ActivityThread.java:5940) at java.lang.reflect.Method.invoke(Native Method) at java.lang.reflect.Method.invoke(Method.java:372) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1389) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1184)

Similar symptoms to Bug 1108564.

Lots of random devices in the reports including the Nexus 7.

Regression from bug 1105541? First report from 12-15

Martyn - Can you dig into this one? Brian has experience tracking these issues down. He can help.

There are 245 crashes since Dec 16: https://crash-stats.mozilla.com/report/list?product=FennecAndroid&range_unit=days&range_value=28&signature=android.content.res.Resources%24NotFoundException%3A+Resource+ID+%230x7f03008c+type+%230x1+is+not+valid+at+android.content.res.Resources.loadXmlResourceParser%28Resources.java%29#tab-reports That's roughly when split APKs went out. All crashes are on recent Android and are all Nightly builds. My hypothesis is that installing an API 9-10 build on an 11+ tablet will cause this crash. (Non-tablet will just get a degraded experience.) Importantly, Play Store builds should not be affected when splitapk makes it up to Beta and Release, because it's not possible to install the wrong APK via Play. Assuming my diagnosis is correct, I think there are two actions worth taking: * A cheap startup check that throws a notification which downloads the right build from FTP, finishing the activity and avoiding the crash. * Verifying that the update service is doing the right thing -- if these crashes aren't from new users installing the wrong APK, but from existing tablet users getting an update to the wrong APK, then sadness will ensure.

Verifying that installing a V9 apk on a tablet produces the same crash as seen here. antlam: Can we get some UX input as to best way forward?

Note that this should be a low-effort piece of work -- nothing fancy. This will only affect non-store users, and we expect a low proportion of impacted users -- I imagine many of these ended up browsing FTP directly (and incorrectly) while Bug 1108456 was still in effect. My proposal is: You're using the wrong $APPNAME for your device! Tap here to try to download the right version. See support.mozilla.org for more. We *could* try offering links, but then we'd have to try to avoid them opening it in Nightly.

Forked Bug 1119915. This bug can be reserved for not crashing!

Let's not.