Environment 1
Device: Xiaomi Redmi Note 3 Pro, Android (6.0.1); Samsung Galaxy S6, Android (6.0.1)
Build: Firefox Nightly 68.0a1(2019-05-25)

Steps to reproduce:

1. Install Firefox Nightly on device.
2. Open Firefox Nightly app.

Expected Result: The application opens with the welcome slides.

Actual Result: The application opens but the slides are nonexistent, no tapping is taken into consideration whether you want to activate the URL bar or tabs functionality.

NOTE 1: This is not reproducible all the time.
NOTE 2: This seem to be reproducible only on devices with android 6.0.

Please view the attached video. The video was made on Xiaomi Redmi Note 3 Pro

Hi,

An update for to the ticket, I managed to reproduce the issue with device Samsung Galaxy Note 9, Android 8.1.0 and build Firefox Beta 68.0b5.

Thanks,
Diana

Hi!
I can reproduce this issue on Beta 68.0b7 and Nightly 68.0a1 (2019-06-05) with the devices:

• Sony Xperia Z5 Premium (Android 7.1.1);
• OnePlus 5T (Android 9);
• Samsung Galaxy Note 8 (Android 9);
• Google Pixel (Android 9).

Note:

• The white screen can be dismissed by going to Android settings and Force Stop the app;
• This is reproducible 1 out of 3 attempts;
• Video: https://drive.google.com/file/d/1V4w6SL1iY5d_mbVcH5Ay5BixodHoSYQG/view

The priority flag is not set for this bug.
:st3fan, could you have a look please?

For more information, please visit auto_nag documentation.

Hi, the same issue is present on device Sony Xperia Z5(Android 7.0) with build Firefox Beta 68.0b9. I did not reproduce this outcome with Huawei MediaPad M3 Lite 10(Android 7.0) and nor with Samsung Galaxy S8+(Android 8.0.0) on neither of the builds.

Diana or Eliza, did you have a previous Firefox Nightly user profile on your device? Can you still reproduce the problems if you clear your Firefox Nightly user profile before you try to install? You can clear your user profile in Android's Settings > Storage > Other apps > Firefox Nightly > CLEAR DATA button.

Clearing the needinfo for Stefan because Devin has prioritized this bug.

Hi, in my case I did not have a previous profile when installing Firefox Nightly on neither of the devices mentioned in description, that is why the steps have the installation part, the same goes for Sony Xperia Z5 (Android 7.0). All the previous versions of Fennec have been uninstalled and afterwards the new versions installed.

I did tried today with clearing data but it did not have any effect, for Xiaomi Redmi Note 3(Android 6.0.1) on build Firefox Nightly 68.0a1(2019-06-13) and on Sony Xperia Z5 (Android 7.0) on build Firefox Beta 68.0b9.

The only workaround to use the specific build browsers is to close and open them again.
NOTE: For device Sony Xperia Z5 (Android 7.0) on build Firefox Beta 68.0b9 it seems that is not always reproducible.

I understand this is an ongoing issue but I'm having trouble reproducing it.
Diana,

• Can you please try the playstore builds and report back?
• Can you try without an Internet connection and see if the issue still reproduces?
• Does the issue still occur after clearing app data and restarting the app?
• Are the tab counter / menu buttons actionable?
• Could you please also attach a small logcat for that few seconds of the app starting but not responding?

Hi,
Environment
Device: Sony Xperia Z5(Android 7.0)

• The Firefox Beta 68.0b11 build from playstore works correctly but the one from path: http://archive.mozilla.org/pub/mobile/candidates/68.0b11-candidates/build1/android-api-16/multi/ does not
  With Nightly from playstore the issue is reproducible
• Without internet connection right after installation the issue does not reproduce
• After clearing data the issue is still present
• The tab counter/menu buttons are not actionable
• Logcat attached

Hi, I rechecked the issue on devices Xiaomi Redmi Note 3 Pro, Android (6.0.1); Samsung Galaxy S6, Android (6.0.1) on all builds - the issue is not reproducible anymore on neither ones, the only that seems affected by this issue is Sony Xperia Z5 from my findings.

Note: Retested on all devices on which the issue was encountered at some point in time.

Hi, attached you have the second logcat: Logcat2 which contains the ANR error generation.

Thanks Diana!
The reason found in logcat - Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago is the same as the one already part of bug 1556083.
Given that as per the video in the ticket description the UI was not responding to touches this does indeed seem to have been the cause from the start.

I'll close this as a dupe of bug 1556083 and continue investigating this ANR there. It's great that we have STR for that!