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
{{ message }}
This repository was archived by the owner on Jan 14, 2025. It is now read-only.
I've noticed that my iOS app stops processing remote push notifications that have content-available-1 after 1 or 2 have been delivered. I think the problem is that I'm not following the rules about when to call the completion handler properly. Eventually, the OS suspends my app and stops delivering the notifications.
What I want to happen is on receipt of a remote push notification it should call my app. Then my app will do something and when it's done call back to the native code so that it can call the completion handler.
I've noticed that my iOS app stops processing remote push notifications that have
content-available-1after 1 or 2 have been delivered. I think the problem is that I'm not following the rules about when to call the completion handler properly. Eventually, the OS suspends my app and stops delivering the notifications.What I want to happen is on receipt of a remote push notification it should call my app. Then my app will do something and when it's done call back to the native code so that it can call the completion handler.
I think this behaviour is required and belongs in this project, but it's beyond my ability. I've found this project which does exactly what I've described but for background fetch operations: https://github.com/transistorsoft/react-native-background-fetch
Is there anyone around who understand iOS development enough to copy / implement this idea?