Open ShezHsky opened 2 years ago
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:
Steps to verify it actually works when data has been refreshed:
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