Closed Bug 1630834 Opened 5 years ago Closed 4 years ago

A subscription with a different application server key already exists

Categories

(Firefox for Android Graveyard :: General, defect, P3)

Firefox 68
Unspecified
Android

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jrconlin, Unassigned)

Details

See: https://github.com/jrconlin/WebPushDataTestPage/issues/26

A User reports:

I tried the demo page on a mobile phone using Android Firefox 68.7

When I click subscription info, I get an error:
"A subscription with a different application server key already exists"

I've never visited the demo page before.

BTW, this is the same error I get on my site as well.

I think the problem is on Android Firefox side. I tried to track down the problem:
https://searchfox.org/mozilla-central/rev/97cb0a90bd053de87cd1ab7646d5565809166bb1/dom/push/Push.jsm#291
https://searchfox.org/mozilla-central/rev/97cb0a90bd053de87cd1ab7646d5565809166bb1/dom/push/PushService.jsm#1200
https://searchfox.org/mozilla-central/rev/97cb0a90bd053de87cd1ab7646d5565809166bb1/dom/push/PushRecord.jsm#262
https://searchfox.org/mozilla-central/source/dom/push/PushService.jsm#1166
https://searchfox.org/mozilla-central/source/dom/push/PushDB.jsm#273

I think this particular mobile brand isn't saving anything on the pushDB, but I haven't no idea how to continue.

Seems android without play store seems to have this problem.

Yeah, that's definitely the problem. FCM doesn't work on devices that do not have Google Play installed. (FWIW, Google shifted A LOT of functions into that app, including their message service which we use as a bridge. As I noted in the original issue, the push message is still encrypted when it goes over the FCM bridge, but we use that because otherwise we'd drain the battery on your device pretty fast.)

Still, the error you're seeing is probably the wrong one to display. What should happen is that firefox tries to call the GCM/FCM registration function, which would fail because Google Play isn't there. The return message should instead indicate that the service is unavailable for this device and not give an incorrect reason.

Sorry about that.

Priority: -- → P3

I made this a P3, but I doubt we will address this in Fennec as we are in the process of moving towards Fenix.

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.