Closed Bug 1834586 Opened 2 years ago Closed 2 years ago

New Nightly won’t install

Categories

(Firefox for Android :: General, defect)

Firefox 119
ARM64
Android
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: negocjator7, Unassigned)

Details

(Whiteboard: [qa-triaged])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

Steps to reproduce:

When downloaded new version of Nightly from https://archive.mozilla.org/pub/fenix/nightly/2023/05/ (arm64-v8a flavor), installing it over an old one fails. Must de-install an old one in order to proceed. Also, if new Betas and Release versions are present, they won’t install either until current Nightly is de-installed. Device: Android 8 Huawei 10.1 inch tablet.

Actual results:

While attempting to install new Nightly the installer responded “The application has not been installed.”

Expected results:

The installing should be a success.

Today was a big update of all three versions: Release (113.2), Beta (114b8) and Nightly. And it was a success! Didn’t have to uninstall Nightly to update them all.

Status update: so far so good. Nightly, as well as Betas install smoothly.

Today was a first release of 116 Nightly, and the installer didn’t even attempt to install it over an existing one. The response was up front “The application has not been installed.” So I had to uninstall an old Nightly and after that installation went smoothly. A few hours later a brand new 114 Release and first Beta of 115 appeared and installation of both was a success.

The severity field is not set for this bug.
:jonalmeida, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jonalmeida942)

Seems like the bug appears when every major release of Fenix is out (like 115, 116 and so on). In order to install Release and Beta Fenixes on this Huawei device (a Samsung Android 12 phone installs for comparison without hitches), I have to uninstall Nightly first. Been informed by mail to state severity status, but couldn’t set that flag, sorry.

Severity: -- → S3

Today Nightly got even worse. There was only new release of Nightly, no new Beta nor Release. But installer couldn’t install new Nightly over a previous one. Had to uninstall Nightly again and then installer did the job.

So far so good again. For about two days new Nightlies install without problems over the old ones. I have seen that before, when new major releases "settled" and consecutive daily releases of particular "milestone" (like 115, 116 and so on) version were coming out. But after new milestone released, everything reverted to this situation again.

So installing a new Nightly over an old one usually fails. Sometimes it installs though, but that happens rather rarely.

So I found some kind of “hack”, which prevents from having to uninstall previous Nightly before installing a new one: don’t create any bookmarks in Nightly. This means also Sync feature must be turned off, because it sends Bookmarks to Nightly.

Everything seems to be working like a charm now. Nightly installs over previous one without problems. It doesn’t “block” updating Release or Beta, either. Also, updating Sync-ed Nightly also works, so my previous post about clearing bookmarks in Nightly in order to update it doesn’t apply, for now.

So the situation reverted to the place it was at the beginning. I have to uninstall previous Nightly to install a new one, be that Nightly, Beta or Release. But, it’s an adventure!

Version: Firefox 115 → Firefox 116

Hello.
After investigating the issue, I did not manage to reproduce the described behaviour.

I've covered the following scenarios:

  • Tried installing all 3 of the latest branches (Nightly, RC, Beta) by downloading the apks directly to the device, none of them seemed to fail on the installation process.
  • Installed an older build to try the upgrading user scenario by downloading the apk to the device. The new build was installed successfully over the old one.
  • Installed the latest Play-Store variant of the Nightly, updated it with the latest Nightly from the internet (task index was used as the official source, downloaded the .apk file on the device) and the process was smooth, the newer version was installed successfully. Also tried with the other 2 branches (Firefox Beta & Firefox RC) with the same success behaviour.
  • Installed some previous version of 2 branches from the Play-Store (Beta & RC), installed Nightly by the built-in package manager with the apk downloaded from the internet to the device, then installed the latest Nightly via ADB, everything seemed fine, installation was completed successfully, so it is not an issue related to having multiple Firefox branches on the devices.
  • Cancelled the installation process and restarted it, the new build was also installed, using both ADB and built-in package manager.
  • Tried with the versions you have specified (RC 115.0) to the next RC build (116.0), latest nightly from 2 months ago (116.0a1), upgrading it to 117.0a1 and also 118.0a1, using only ADB.
  • Covered a scenario of upgrading from Nightly 112.0 to Nightly 118.0a1 (112.0 was installed by using the built-in package manager, 118.0a1 was installed using ADB command), no issues encountered.
  • Installed previous version of 2 branches by using ADB, then installed the latest Nightly using the built-in package installer (downloaded the .apk from the internet and opened it on the device), installation was completed successfully.
  • Installed all 3 of the latest branches (Nightly, RC, Beta) using ADB, none of them failed on the installation process.

Devices used for testing: Huawei P50 Pro (Android 11), Huawei P40 Lite (Android 10), Samsung Galaxy Tab A6 (Android 5.1.1), Samsung Galaxy S22 Ultra (Android 13).

Could you please send us a screen recording of the issue? It would help in the problem identification process.
Additionally, we would need the specific model of the device of yours that you managed to reproduce the issue.
Did you also try to upgrade Firefox from the Play-Store? Does it have the same behaviour?

Thank you for submitting the issue.

Flags: needinfo?(negocjator7)
Whiteboard: [qa-triaged]

Sorry I didn’t report on the issue. After my last negative post here Nightly magically got well and the issue vanished. All was good again. I didn’t report it here as I did earlier because issue seemed to reappear randomly after some time of good behaviour. So for the time being all is well. Again.

Flags: needinfo?(negocjator7)

So while on my one Huawei MediaPad M5 lite tablet updating process went fine, on second identical device everything failed. Had again to uninstall Nightly in order to update Release’s and Beta’s from archive.mozilla.org/pub/fenix/ . Also have to uninstall current Nightly to update it with newer Nightly version.

So the update works again on the device I mentioned in previous post. The pattern I can see here is that the problem occurs every major upgrade of the program, and after several days of unsuccessful update approaches the problem vanishes. Until next big upgrade of Fenix.

Hardware: All → ARM64
Version: Firefox 116 → Firefox 118

Yesterday there was a triple update: all three branches of Fenix had new versions: 116.3 for Release, 117b8 for Beta and Nightly of course. On one Huawei device it failed, had to uninstall Nightly to succeed. But, on another Huawei tablet the update process went smoothly.

Today was a milestone update of Release to 117, second Beta of 118 and 119’s Daily. The installer couldn’t install new apk’s. Had to uninstall previous Nighty and then all three new apk’s were installed without a hitch.

Version: Firefox 118 → Firefox 119

After failure to install new Fenixes without uninstalling previous Nightly on one of my Huawei tablets, I tried the same feat on another identical device. It was triple “milestone” update: 117.0.1 Release, 6th Beta of 118 and a newest Nightly. And it was a success. I’m beginning to think it’s a device issue.

So it’s definitely a device issue. On one Huawei device the problem persists: have to uninstall previous Nightly to install new Release, Beta or Nightly. On another identical (although some minor system details look a little different) device problem doesn’t exist at all.

As stated in Comment #19, I will close this as invalid, as it is a device related issue.
Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Flags: needinfo?(jonalmeida942)
You need to log in before you can comment on or make changes to this bug.