If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Empty notification received on Firefox Beta

NEW
Unassigned

Status

()

Firefox for iOS
Firefox Accounts
3 months ago
a month ago

People

(Reporter: st3fan, Unassigned)

Tracking

unspecified
Other
iOS

Firefox Tracking Flags

(fxios10.0)

Details

(Whiteboard: [MobileCore][AutoPush][8.2])

(Reporter)

Description

3 months ago
The very first notification I received was empty. No title, no contents. Screenshot attached.

It is unclear if this was a fxaccount:* notification or if this was the result of me sending myself a tab from Desktop.
(Reporter)

Comment 1

3 months ago
Firefox Beta 4218 via Internal TestFlight
(Reporter)

Updated

3 months ago
Severity: normal → blocker
(Reporter)

Updated

3 months ago
tracking-fxios: --- → 8.0+

Comment 2

3 months ago
Quick drive-by, but...IIRC FxA will send a push notification with no payload when you verify your account or confirm a signin, might be a good candidate to look at for debugging this.
(Reporter)

Comment 3

3 months ago
Why no payload? Is there no way to identify this notification?

Are you saying we can we assume that a zero length message is the sign in confirmation?

We cannot ignore this message, and I don't think we have a good string for it. Should this be the "Tap to begin" notification maybe?
Flags: needinfo?(rfkelly)

Comment 4

3 months ago
> Are you saying we can we assume that a zero length message is the sign in confirmation?

Yes.  For historical reasons (we added this one before payloads were properly supported end-to-end) the "you are now verified" event is signaled by a push notification with empty body.  It will mean either "your email address was successfully verified" or "your login session was successfully confirmed", depending on whether you did a signup or a signin.  But in either case what it means is basically "you're now ready to start syncing".

I expect we could disable this message on the server though, in the same way we intend to disable the other unsupported messages.
Flags: needinfo?(rfkelly)

Comment 5

3 months ago
On desktop, this event surfaces as a "sync will begin momentarily" notification.
(Reporter)

Comment 6

3 months ago
I think it is a good idea to disable this one on the server for now. We can address it when we have strings for this notification.

Is it possible to give this notification a proper payload so that we can see the difference between signup or signin?

Cc to :vladikoff to request a Github issue for this
Flags: needinfo?(vlad)
(Reporter)

Comment 7

3 months ago
Moving this to 8.1
tracking-fxios: 8.0+ → 8.1+
(In reply to Stefan Arentz [:st3fan] from comment #7)
> Moving this to 8.1

Can we remove `Importance:	P1	blocker` from this? (If this was moved for later release)

> Is it possible to give this notification a proper payload so that we can see the difference between signup or signin?


We can try! I filed an issue here: https://github.com/mozilla/fxa-auth-server/issues/1976
Flags: needinfo?(vlad)
(Reporter)

Updated

3 months ago
Severity: blocker → normal
Priority: P1 → --
I receiving an empty notification intermittently when following this steps:

1. Same FxA signed in on: - Nightly 56.0a1 (2017-07-09) 
                          - iPad Mini (10.3.1)
                          - iPhone 6 Plus (10.3.2)
2. Send a few tabs from desktop to iPad
3. Send a few tabs from desktop to iPhone
4. Select a tab on desktop and "Send to All Devices"

Result: Once in a while, when sending to all devices, I'm getting an extra empty push notification on iPad.

This doesn't seem to happen on iPhone.
(Reporter)

Comment 10

2 months ago
The above is with Beta 4467
Taking this to investigate.
Assignee: nobody → jdarcangelo
Status: NEW → ASSIGNED

Updated

2 months ago
See Also: → bug 1380295
Duplicate of this bug: 1380295
(Reporter)

Updated

2 months ago
Whiteboard: [MobileCore][AutoPush] → [MobileCore][AutoPush][8.2]
(Reporter)

Comment 13

2 months ago
Moving this to 9.0. Also, this bug needs to turn into one that is more concrete/actionable.
tracking-fxios: 8.1+ → 9.0
Assignee: jdarcangelo → nobody
Status: ASSIGNED → NEW
tracking-fxios: 9.0 → 10.0
You need to log in before you can comment on or make changes to this bug.