Closed Bug 1135362 Opened 9 years ago Closed 9 years ago

Use fxpay for Android payments

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P1)

2014-Q3
x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: andy+bugzilla, Unassigned)

References

Details

The effort to get mozPay working on Android is still ongoing and something that should probably keep up. However:
* once it does land it will have to go through the train
* it won't land this quarter
* we recommend developers use fxpay anyway for in-app payments
* you have to use fxpay for desktop in-app payments

I really don't see much of a downside to turning on fxpay for Android and working around the current issues. Then when the mozPay fixes land and the whole flow works on Android, we can turn it off in fxpay and use the native flow.

The upshot is, we have Android out and people using it sooner and we can wait till mozPay is all fine. 

See bug 1134466, bug 1123849, bug 1130057, bug 1097928 etc which have to work their way through the train.
Depends on: 1134296
I'll add that there's no technical reason we need mozPay on Android. There's no Trusted UI and there's nothing else that should prevent us from doing payments with standard web technology.
So thinking about this it's probably a case of tweaking this line to exclude android: https://github.com/mozilla/fxpay/blob/c37e40a57eece66daee2edcea653d566596a5a5b/lib/fxpay/pay.js#L16

And anything popup related that looks at capabilities.navPay e.g. https://github.com/mozilla/fxpay/blob/c37e40a57eece66daee2edcea653d566596a5a5b/lib/fxpay/pay.js#L16 so you get the popups on android.
Priority: -- → P1
Assignee: nobody → kumar.mcmillan
This also assumes that bug 1135261 isn't going to occur on Android as well. I tried installing http://webapprt-win.paas.allizom.org/ as an app to check on my Android and it just crashes on starting up the webapp on my Android, so not sure yet :(
Depends on: 1135261
Oops, took a nightly update and its working again. It fails to open a popup on Android runtime at all and the "window reference was falsey".
Looks like we're going to set this aside for now
Assignee: kumar.mcmillan → nobody
We can re-open this if we file its worthwhile doing.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
No longer depends on: 1135261
You need to log in before you can comment on or make changes to this bug.