You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During EF 26 there were a few reports of announcement notifications deep-linking to the "Expired announcement" view, even though they'd literally just been advertised. It was confirmed some of these devices had low-power mode enabled so would not have pre-emptively loaded content via the app delegate's application(_:didReceiveRemoteNotification:fetchCompletionHandler:) delegate callback.
To make this more reliable for EF 27, we should tweak the way announcements are presented so that:
If the announcement is cached locally, show it (already done)
If the announcement cannot be found, perform a fetch
If the announcement exists post-fetch, show it
If the announcement does not exist post-fetch, show the "expired" message
If the fetch fails, show a non-modal error with a retry fetch button
We should also investigate whether shifting the acquisition of content in a notification extension would help improve reliability of background fetches
The text was updated successfully, but these errors were encountered:
According to user reports (and own experience), this issue seems to now be happening independently of whether or not the device in question is in low-power mode. When receiving a notification for an announcement, tapping on it to open the app without having opened the app manually to trigger a data refresh will result in the user being informed about the announcement already having expired.
Steps to verify issue:
Tap notification for announcement shortly after it arrives.
App will show that the announcement has already expired or been deleted.
Return to News view of app and pull down to refresh.
Announcement will appear in list and can be opened in detail view.
Steps to verify it actually works when data has been refreshed:
Receive notification about new announcement.
Open app directly instead of tapping notification and trigger data refresh.
Announcement should appear in News view.
Leave app (e.g. to Home screen) and tap announcement notification.
App correctly opens to announcement detail view.
Thanks for Wilk (Telegram), Faye (Ticket) and others for reporting this.
During EF 26 there were a few reports of announcement notifications deep-linking to the "Expired announcement" view, even though they'd literally just been advertised. It was confirmed some of these devices had low-power mode enabled so would not have pre-emptively loaded content via the app delegate's
application(_:didReceiveRemoteNotification:fetchCompletionHandler:)
delegate callback.To make this more reliable for EF 27, we should tweak the way announcements are presented so that:
We should also investigate whether shifting the acquisition of content in a notification extension would help improve reliability of background fetches
The text was updated successfully, but these errors were encountered: