Created attachment 8891412 [details] ScreenshotsNightly.png Devices used: - ZTE Grand X In - Android 4.0.4 - x86 architecture - HTC Sensations 4G - Android 4.0.3 Steps: - download latest build from http://ftp.mozilla.org/pub/mobile/nightly/ - try to install it Expected Results: - as your device is no longer compatible you should get an error stating that Actual Results: - you get a parse errror Can we improve the parse error though? I think it is generic from Android OS when trying to install any not compatible build but for x86 devices for example when we try to install the regular build we do get a small notification/ toast message saying is not the correct build.
Created attachment 8891413 [details] Screenshot_wrong_build.png x86 error example of toast notification
I think the "Parse Error" is generic from Android framework and will not occur to real google play user because they cannot install the 56 APK from the beginning. The screenshot actually proved that not compatible APK won't install on ICS devices as expected. And about the x86 error toast notification,
And about the x86 error toast notification, it's kinda weird because the toast is triggered in runtime, which means the apk installed and shouldn't happen. :ioana Is the ZTE device installed the correct apk(fennec-56.0a1.multi.android-i386.apk)?
> :ioana > Is the ZTE device installed the correct > apk(fennec-56.0a1.multi.android-i386.apk)? That was my point - I've downloaded the regular API 15 APK not the i386 one and when I tried to install it I got the toast telling me that it is the wrong build. Thast's why I entered this bug to see if we can get one like that to inform the user the build is not compatible anymore instead of the black parse error which doesn't tell my to the user.
(In reply to Max Liu [:maliu] from comment #2) > The screenshot actually proved that not compatible APK won't > install on ICS devices as expected. Yes, That was used in signing of the feature as fixed.