Closed Bug 1373203 Opened 8 years ago Closed 8 years ago

Remove delivered push notifications if there are no tabs received

Categories

(Firefox for iOS :: Firefox Accounts, enhancement, P2)

Other
iOS
enhancement

Tracking

()

RESOLVED FIXED
Iteration:
1.25
Tracking Status
fxios 8.0+ ---

People

(Reporter: jhugman, Assigned: jhugman)

References

Details

(Whiteboard: [MobileCore][Autopush])

Attachments

(1 file)

When a push notification is received with a sync:collections_changed event, and there are no tabs, only non-sensical message is possible. (current behaviour: Firefox Sync / Tap to begin). In this case, we should try and recycle an existing notification, and then delete it so we make a best effort to make the current notification useful. See also Bug 1373201. In the case of other FxA push events, we should file other bugs. https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/SupportingNotificationsinYourApp.html#//apple_ref/doc/uid/TP40008194-CH4-SW1
Blocks: 1373111
Iteration: --- → 1.24
Whiteboard: [MobileCore][Autopush]
Priority: -- → P2
Assignee: nobody → jhugman
Status: NEW → ASSIGNED
Iteration: 1.24 → 1.25
Attachment #8883417 - Flags: review?(jdarcangelo) → review+
Merged into master.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [MobileCore][Autopush] → [MobileCore][Autopush][needsuplift]
Whiteboard: [MobileCore][Autopush][needsuplift] → [MobileCore][Autopush]
This patch has some odd side effects. I removed a device from my account, and as a result, notifications are being sent around. We don't know how to handle those, so I think this patch kicks in and shows the last tab notification again. It is better than "Tap to begin" but still not ideal. (I understand the fxaccount:device_disconnected message will not be sent anymore, but I assume this can also happen for other notifications)
> I understand the fxaccount:device_disconnected message will not be sent anymore IIUC we had a rollback on the FxA server during the train-90 deployment, which would have also rolled back the code that disabled sending of these notifications to iOS devices. I wonder if you saw some temporary weirdness due to the notifications briefly being sent again?
Keep in mind that Desktop also sends a sync:collections_changed event when syncing the clients collection for the first time.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: