Open Bug 1402527 Opened 2 years ago Updated 2 years ago
Install of the .apk fails on Kindle
¡Hola! Trying to install the .apk I get some "analysis error", please see the screen capture attached. The last Nightly that updated is 54.0a1 (2017-02-07) Built from https://hg.mozilla.org/mozilla-central/rev/af8a2573d0f1e9cc6f2ba0ab67d7a702a197f177 ¡Gracias! Alex
Have you by any chance moved Firefox onto an external SD card? For the date you've given, bug 1322029 seems the most likely to cause installation problems like that.
¡Hola Jan! This is on a 1st or 2nd generation Kindle that doesn't even have an SD slot. ¡Gracias! Alex
I don't know we support Kindle:) May I know how can I help with this?
(In reply to Nevin Chen [:nechen] from comment #3) > I don't know we support Kindle:) Not specifically, but as long as it runs a supported version of Android I guess... We certainly have one or two Kindle-specific workarounds in our codebase (https://dxr.mozilla.org/mozilla-central/search?q=path%3Amobile+kindle+-path%3Atest&redirect=false), but other than that I'm not sure what to say, either
Alex, can you get a logcat from the device?
Hardware: Other → ARM
¡Hola Richard! I could give it a try if you tell me how to do so exactly. ¡Gracias! Alex
Flags: needinfo?(alex_mayorga) → needinfo?(rnewman)
Set up your Kindle for debugging: https://developer.amazon.com/docs/fire-tablets/ft-set-up-your-kindle-fire-tablet-for-testing.html then either see if you can do this: https://www.utest.com/articles/android-logs-on-the-go-how-to-obtain-them-using-the-bug-report-shortcut or use `adb logcat` after installing Android Studio: https://developer.android.com/studio/command-line/logcat.html
(In reply to Richard Newman [:rnewman] from comment #8) > or use `adb logcat` after installing Android Studio: > > https://developer.android.com/studio/command-line/logcat.html Or just download the Platform Tools, so you don't have to download and install the whole of Android Studio: https://developer.android.com/studio/releases/platform-tools.html
You need to log in before you can comment on or make changes to this bug.