Open
Bug 1338550
Opened 8 years ago
Updated 2 years ago
Move to using iOS10 version of Local Notifications
Categories
(Firefox for iOS :: General, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
fxios | + | --- |
People
(Reporter: fluffyemily, Unassigned)
Details
(Whiteboard: [MobileCore] [Debt])
On master, if you login to your Firefox account, when you are returned to the Settings panel, an alert is displayed asking if you would like to receive notifications. On the swift-3-migration branch no alert is displayed
Reporter | ||
Updated•8 years ago
|
Assignee: nobody → etoop
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•8 years ago
|
||
This turned out not to be a problem. It was remembering an acceptance of the notifications screen from an earlier build. However, We are currently using a version of the notifications code that was deprecated in iOS10. We need to move to using the new code
Assignee: etoop → nobody
Status: ASSIGNED → NEW
Iteration: 1.15 → ---
Summary: [swift-3-regression] User is not asked for notification permission after account login → Move to using iOS10 version of Local and Remote Notifications
Whiteboard: [MobileCore] [Debt]
Reporter | ||
Updated•8 years ago
|
tracking-fxios:
--- → ?
Updated•8 years ago
|
Priority: -- → P3
Comment 3•7 years ago
|
||
No; when this bug was filed we didn't use Remote Notifications. However, we are still using LocalNotifications when the app is in the foreground. We should perhaps consider either deleting this code, or moderninsing it. Will change the title of this bug to just Local notifications.
Flags: needinfo?(jhugman)
Updated•7 years ago
|
Summary: Move to using iOS10 version of Local and Remote Notifications → Move to using iOS10 version of Local Notifications
This was fixed with PR #3421 (https://github.com/mozilla-mobile/firefox-ios/pull/3421), specifically commit 9c13f9b (https://github.com/mozilla-mobile/firefox-ios/pull/3421/commits/9c13f9bcef5cdac28d06f3d3c9a83d85006eb40f).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•