-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug] Firefox nightly has moved and New Nightly link points to org.mozilla.fennec_aurora #12207
Comments
We are in the middle of the process of simplifying Firefox versions in the Play store. This information is correct. We have yet to get the Nightly build updated on the Firefox Preview <org.mozilla.fenix>. It will be updated soon. |
@kbrosnan I have this message on both Fenix Nighly <org.mozilla.fenix.nighly> and Fennec Nighly <org.mozilla.fennec_aurora>. Both messages redirect to Fennec Nighly <org.mozilla.fennec_aurora> play store page. |
Actually there is a bug here @sblatz we either need to hardcode fenix/app/src/main/java/org/mozilla/fenix/components/tips/providers/MigrationTipProvider.kt Line 96 in 0a9afbe
|
So both fennec nightly and fenix nightly are gone... |
Will Firefox Preview <org.mozilla.fenix> branding on Play Store be updated to Nightly branding? Curently, they are still using old Preview branding. Or will nightly versions now use Preview branding instead? Update: Is is now also rebranded on Play Store as Nightly. But could you update Play Store descriptions of old Nightlies to let users apps are moved and what should they use instead? Maybe also delist them from Play Store searchs if this is possible? Also, it seems that description of new Nightly is not translated to some languages, while old Nightly description is. And some bug with description of new Nightly: Link to "Download the release version of Firefox." contains |
Given some of the confusion around this change, can we see if it would be possible to migrate top sites when using Sync to make the transition as seamless as possible? I just did this transition myself and it was disappointing to see that I lost my top sites in the move. See #7936 Even a basic version that did top sites sync on mobile only would be nice to have. |
For verification, making the org.mozilla.fennec_aurora and org.mozilla.fenix.nightly builds (per #9208 #9208 (comment) ) and testing that the link takes you to the "new" Firefox Nightly (which is org.mozilla.fenix, and used to be Firefox Preview, but has now been rebranded to "Firefox Nightly"). (My mistake in the earlier bug for not specifying that the link should open org.mozilla.fenix!) |
Developers -- generally most of the time, I'm with you but when you make it this much confusing -- I have to ask you -- do you really want to lose your userbase by doing this?! Have you ever seen the discussions that go on /r/firefox or /r/Android ?! I always try to help the users there and redirect them to use the appropriate Firefox versions and to make Fenix even better by making them request features and file bug reports -- but now even I don't know what's going on here now! I never said anything until now, I was with you -- and still am, but I'll say this one thing to you... THIS. IS. REALLY. CONFUSING. TO. USERS! CAN. YOU. PLEASE.... STOP. IT?! Please I request you to at least document this somewhere in a way that'll at least make it clear to general users which version to use or recommend. Those recent merged commits -- I don't understand them! I know fenix is currently in a transition period but this is not how you handle it. At least don't push those versions to the Play Store untill you are done! Please see the Mozilla's Play Store page -- How many versions do you even want to have?! CC @vesta0 |
While I'm not a developer, I think this change is good for the long run. They are dropping from 5 versions to 3 just like pre-fenix. The appropriate Firefox version for the general public has always been the Firefox browser. This is the first result when you search for "Firefox" in the Play Store. Currently, this is the Fennec browser. Fenix is not ready for stable and it'll replace Fennec when it's ready. If you want to use the Fenix, install Firefox Beta. Don't use Nightly and soon to be removed versions and you are good to go. |
Have you seen the Play Store page of Mozilla right now?! And I know the situation will become much better after the transition happens but what I'm saying is this is not the way to handle. If you read Reddit then you'll realise the general users' pain! There must be other ways to handle it!
I'm not sure what version are "soon to be removed" and versions what are permanent anymore! And why do you think Firefox Beta/Firebox Preview is not an appropriate version for general users? Even Fenix developers team agrees that it a production/quite stable ( I can't remember where and when I read it but someone from Mozilla said this and I agree with them). |
Yeah, It's a mess. I think Mozilla shouldn't have 5 different versions of the same app in the first place. We practically never used fennec_aurora for a long time and after Fenix merged to the beta, there is no need for Preview anymore. And yeah, I read people asking which version to use every couple of days on reddit. This is finally ending now.
The old Firefox Nightly (fennec_aurora) and Firefox Preview Nightly are the versions getting removed. There are reasons why Fenix is not pushed to the stable. UI is still changing, (We just got a new tab design for example) and extension support is garbage. Fennec can run any extension desktop Firefox can. Fenix can't because extension support is not complete. I expect they can push Fenix to stable when both developers and user base is generally happy with the UI and the full extension support is implemented. |
There were some technical reasons along with keeping the apps with the largest active userbases why the 3 builds were chosen. The people in r/firefox made some incorrect assumptions about what builds were going to survive. The active full featured browsers are:
|
We checked the links to the new Nightly channel and now they are working as expected. So I'll close this. Thanks! |
Steps to reproduce
Start nightly 200702. See Screenshot. Press on the button.
Expected behavior
Get some useful Indication of what is happening and be told how to get the proper nightly.
Actual behavior
Get redirected to regular non nightly preview.
Device information
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: