We don't understand this issue well. Current theorys are a 3rd party store that only provides an ARM binary. Some sort of forum post that is popular or some sort of direct link on the internet to download Firefox. I have seen a different crash that is an emulator that allows users to run Android apps on desktops [1]. Since it is a a crash on startup it is simple for a user to crash many times inflating the crash rate.
[1] http://www.bluestacks.com/comparison-chart.html Kevin On Thu, Dec 31, 2015 at 8:48 AM, Margaret Leibovic <[email protected]> wrote: > On Wed, Dec 30, 2015 at 10:52 PM, Kevin Brosnan <[email protected]> > wrote: > >> >> The second issue that is skewing the crash data is that the number 2 >> crash is the ABI mismatch [5]. Running Firefox for Android for ARM devices >> on x86 or vice versa. We have some code changes in v45 to try to alert >> users that they need to use a different build. They are rudimentary but at >> least give some feedback other than crashing [6]. >> > > Do we understand how beta users are even encountering this issue? Is > Google Play giving them the wrong version? Is there any way for us to know > the source of the builds running into this problem? > > Uplifting bug 1119915 would reduce the crash rate, but I'm worried about > how users are even getting these incorrect builds in the first place. Also, > if we wanted to uplift that, we'd need to uplift a string. > > Margaret >
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
