Closed Bug 766636 Opened 13 years ago Closed 4 years ago

hide the in-app update UI on channels where we don't use it (or launch the play store to update)

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mluna, Unassigned)

References

Details

We should hide the Check for Updates button in Beta and Release channels if we aren't using it. When I tap it, it says there are no updates, even when there are updates available in the play store.
Sounds like a duplicate of bug 619801.
Bug 619801 did not actually fully ship, because it depended on a build change from bug 609705 that got backed out because it broke the feedback add-on. The feedback add-on isn't an issue any more, though we also need to make sure that the correct channel is send in the blocklist ping for metrics. As long as that works, we should be able to use that technique for this bug: Add --disable-updater to the release mozconfigs, and wrap the UI in #ifdefs.
Summary: hide the in-app update UI on channels where we don't use it → hide the in-app update UI on channels where we don't use it (or launch the play store to update)
We still do this. Some folks still get confused.
Version: Firefox 14 → Trunk
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.