Firefox Beta 11.0 (XUL) is not displayed on the Android Market for Tablets

VERIFIED FIXED

Status

Release Engineering
General
VERIFIED FIXED
5 years ago
3 years ago

People

(Reporter: aaronmt, Assigned: mounir)

Tracking

other
ARM
Android

Firefox Tracking Flags

(firefox11 verified)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Firefox Beta 11.0 (XUL) is not displayed (compatable) with tablets on the Android Market, thus no update and no product shown.
(Reporter)

Updated

5 years ago
Summary: Firefox Beta 11.0 (XUL) is not displayed on the Android Market → Firefox Beta 11.0 (XUL) is not displayed on the Android Market for Tablets

Comment 1

5 years ago
We'll want to fix this for beta 4. No need to re-spin beta 3 though, since the update just isn't offered to tablet users currently (no errors, etc.). Also, XUL 11 will not be shipped to release (10.0.3 will), so no issue there.
(Reporter)

Comment 2

5 years ago
Looks to be the SMS permission causing an issue.

Phone users will see permissions:

Services that cost you money: 
Send SMS messages

Your messages: 
Receive SMS
(Reporter)

Updated

5 years ago
Blocks: 713377
(Assignee)

Comment 3

5 years ago
Created attachment 598373 [details] [diff] [review]
Remove SMS permissions
Assignee: nobody → mounir
Status: NEW → ASSIGNED
Attachment #598373 - Flags: review?(blassey.bugs)
Attachment #598373 - Flags: review?(blassey.bugs) → review+
(Assignee)

Comment 4

5 years ago
Comment on attachment 598373 [details] [diff] [review]
Remove SMS permissions

[Approval Request Comment]
User impact if declined: no Firefox Beta for tablets in the Android Market
Testing completed (on m-c, etc.): this permission is already disabled in m-c
Risk to taking this patch (and alternatives if risky): contents using WebSMS will break but we can safely assume that those contents do not exist because nor Aurora or Nightly have WebSMS enabled by default (Firefox neither)
Attachment #598373 - Flags: approval-mozilla-beta?
Attachment #598373 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

Comment 5

5 years ago
aki, please ping QA if we want this re-tested with a practice build first, on Android Market.

Comment 6

5 years ago
(In reply to Tony Chung [:tchung] from comment #5)
> aki, please ping QA if we want this re-tested with a practice build first,
> on Android Market.

I think we do want this re-tested with a practice build.
I'm currently waiting for that build; I can put it in the test Android Market account, and QA can re-test after that point.
(Assignee)

Comment 7

5 years ago
https://hg.mozilla.org/releases/mozilla-beta/rev/6df75f4d5ccc

Can the QA test the build generated by the build bots?
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Where is the build?

Comment 9

5 years ago
(In reply to Mounir Lamouri (:volkmar) (:mounir) from comment #7)
> https://hg.mozilla.org/releases/mozilla-beta/rev/6df75f4d5ccc
> 
> Can the QA test the build generated by the build bots?

No, they can't.
We need a build with a different app name to put on the market.
I pushed tip of beta to try with a package name change:
https://tbpl.mozilla.org/?tree=Try&rev=c4e8bdb49682
builds will be here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/blassey@mozilla.com-c4e8bdb49682
(Reporter)

Comment 11

5 years ago
Drop a comment here with the market package name or email me and I'll give it a test tonight/tomorrow.

Comment 12

5 years ago
(In reply to Brad Lassey [:blassey] from comment #10)
> I pushed tip of beta to try with a package name change:
> https://tbpl.mozilla.org/?tree=Try&rev=c4e8bdb49682
> builds will be here:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/blassey@mozilla.
> com-c4e8bdb49682

The package name of your apk (org.mozilla.firefox_beta) is the same as the package name of another developer's application. Choose a new package name.

Comment 13

5 years ago
Giving it another shot:

https://tbpl.mozilla.org/?tree=Try&rev=f6132bf40115
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/asasaki@mozilla.com-f6132bf40115
I expected try to build with nightly branding, not beta.

Just to be safe I also pushed another, with the package name of every branding changed to org.mozilla.fennec_sms_test:
https://tbpl.mozilla.org/?tree=Try&rev=1d475a4290de
(Assignee)

Comment 15

5 years ago
(In reply to Aki Sasaki [:aki] from comment #9)
> No, they can't.
> We need a build with a different app name to put on the market.

Sorry about that. And thank you Brad for providing a build.

Comment 16

5 years ago
I uploaded 'smstest' to the market.
It looks good, but I haven't tried installing it on a tablet yet.

Comment 17

5 years ago
(In reply to Brad Lassey [:blassey] from comment #14)
> I expected try to build with nightly branding, not beta.

Try builds with the in-tree mozconfig, e.g.
https://hg.mozilla.org/try/file/1d475a4290de/mobile/xul/config/mozconfigs/android/nightly

Since we're pushing from beta, that points to beta branding.
The Try talos/unit tests assume nightly branding, which is why this breaks.
Once bug 725703 is fixed that won't be the case anymore, but we might not have an early warning system that we merged branding incorrectly (e.g. beta will start building with aurora branding and tests will be green).
(Reporter)

Comment 18

5 years ago
verified fixed via Galaxy Tab 10.1, and a Galaxy Nexus using market package posted above
Status: RESOLVED → VERIFIED
i got firefox 11.0 XUL on both SGS2 and Galaxy Nexus.   I dont have any tablets on me at the moment.

Comment 20

5 years ago
Thanks!
When you're done testing, I should take this down.  Is there more testing planned?
Status: VERIFIED → RESOLVED
Last Resolved: 5 years ago5 years ago

Updated

5 years ago
Status: RESOLVED → VERIFIED

Comment 21

5 years ago
Verified on 
Tablets:
Asus Eee Transformers - Android 3.2
Asus Eee Transformers - Android 3.1
Galaxy Tab 10.1 - Android 3.1 
Phones:
Samsung Galaxy Nexus - android 4.0.2
Samsung Nexus S - Android 2.3.6
(Reporter)

Comment 22

5 years ago
@aki, remove it

Comment 23

5 years ago
Awesome, done.
(Reporter)

Updated

5 years ago
status-firefox11: --- → verified
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.