Post

Replies

Boosts

Views

Activity

Reply to Silent Push background launch rejected with "pushDisallowed" and "AMNP" on TestFlight build
Thank you for your detailed explanation. I have one additional question regarding your suggestion to use a Notification Service Extension (NSE). My understanding is that a Notification Service Extension executes in its own process and is separate from the main application. Therefore, while the extension itself can perform limited processing, it cannot directly execute the main application's code or wake the main application to perform arbitrary background tasks. In my use case, I need to execute processing implemented in the main application, such as obtaining the device's current location in response to a server request. Is there any supported mechanism that allows the main application itself to be launched or resumed in the background in response to a remote request? If not, would it be correct to understand that this type of server-triggered processing should instead be implemented entirely within the Notification Service Extension (to the extent supported by the available APIs), or that iOS intentionally does not provide a mechanism to guarantee execution of the main application in this scenario? Thank you again for your assistance.
3w
Reply to Silent Push background launch rejected with "pushDisallowed" and "AMNP" on TestFlight build
Thank you for your detailed explanation. I have one additional question regarding your suggestion to use a Notification Service Extension (NSE). My understanding is that a Notification Service Extension executes in its own process and is separate from the main application. Therefore, while the extension itself can perform limited processing, it cannot directly execute the main application's code or wake the main application to perform arbitrary background tasks. In my use case, I need to execute processing implemented in the main application, such as obtaining the device's current location in response to a server request. Is there any supported mechanism that allows the main application itself to be launched or resumed in the background in response to a remote request? If not, would it be correct to understand that this type of server-triggered processing should instead be implemented entirely within the Notification Service Extension (to the extent supported by the available APIs), or that iOS intentionally does not provide a mechanism to guarantee execution of the main application in this scenario? Thank you again for your assistance.
Replies
Boosts
Views
Activity
3w