Closed Bug 914415 Opened 11 years ago Closed 11 years ago

Persona window never opens on Android from web app

Categories

(Core Graveyard :: Identity, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: kumar, Assigned: wesj)

References

Details

Attachments

(2 files)

Attached image device-2013-09-09-184555.png (deleted) —
To reproduce: - Install Firefox Nightly on an Android device - Install this add-on to activate payments prefs: http://mzl.la/19BZQCx, from https://addons.mozilla.org/en-US/firefox/addon/dev-marketplace/ (source: https://github.com/wesj/devMarketplace) - Install the in-app payment tester from http://apploa.de/3b25a (manifest: http://inapp-pay-test.paas.allizom.org/manifest.webapp) - Open the tester app from the Android home screen - Tap Pay - When prompted to sign-in, tap the sign-in button Expected: A Persona window should open and let you sign in. Actual: No Persona window opens. You only see the spinner from the webpay server and there isn't anything useful in the logcat that I can see. Note that the add-on above activates Persona debug settings.
Attached file android-app-signin-logcat.txt (deleted) —
Jed, it looks like we're trying to open a trusted UI from a trusted UI -- is native Persona even at work here? I believe navigator.mozPay() has a custom implementation on Android. Wes could provide details.
This might be a dupe of bug 826325
/cc :seanmonstar, who has has deeper knowledge about persona on android
:kumar and no, there is no native Persona navigator.id for Firefox on Android. Opening a Persona issue for this. Let's discuss more here: https://github.com/mozilla/browserid/issues/3882
We thought maybe this was related to CSP errors but I disabled CSP on WebPay and the error still happened (without any CSP errors in logcat). We can rule that out.
Blocks: 909896
Assignee: nobody → wjohnston
Hmm. The STR work fine for me on nightly. Persona window opens. I can log in. Going through the pin verification now (although I never got the expected SMS...). Can you give me any details about the type of device you're testing on?
I was testing on HTC Dream (TMob G2) running an ancient Android, version 2.3.4. That's the only device I have laying around. Sounds like we can maybe mark it as wontfix? Let me know if you need more logging than what's attached.
I just verified that this is not happening with Ice Cream Sandwich on a Samsung Galaxy II. If someone wants to close this (or change priority) then go for it.
There were still payment issues on ICS but I filed bug 924693 to track them
According to http://developer.android.com/about/dashboards/index.html, over 50% of devices are on ICS and above. Should we be worrying about compatability before that? We should be matching whatever compatibility Firefox has in my opinion.
Flags: needinfo?(elancaster)
Yeah, we do worry about those devices. I've got some around and will try to test this when I can. But I'm surprised it only fails on some devices.
+1. Officially we support Android v2.2 and up.
Wesj Is there a latest status on this? Update?
Flags: needinfo?(elancaster) → needinfo?(wjohnston)
The persona windows show up and work on my phones. Can QA verify?
Flags: needinfo?(wjohnston) → needinfo?(aaron.train)
Do you mean you tried it with Android 2.3? That's the only version I've seen it in so far.
Yeah, I tried on an Android 2.3 Motorola Droid X.
Thanks. I trust your 2.3 test more than mine because I was testing on a locked T-Mob phone with a non-standard Android build anyway. QA can weigh in if they like but I'm fine with a worksforme until someone else hits it.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Flags: needinfo?(aaron.train)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: