[MOBILE-5309] Update the headless task time out and make sure it ends#694
Merged
[MOBILE-5309] Update the headless task time out and make sure it ends#694
Conversation
jyaganeh
approved these changes
Nov 15, 2025
rlepinski
pushed a commit
that referenced
this pull request
Nov 15, 2025
rlepinski
added a commit
that referenced
this pull request
Nov 15, 2025
* update the headless task time out and make sure it ends (#694) * Release 24.8.1 * Changelog --------- Co-authored-by: Ulrich Giberné <ulrich.giberne@airship.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The global state issue is now fixed with the new time out.
The headless task is triggered correctly with a high priority push as it wakes up the app. It doesn't work with normal priority because service can't be launched from background anymore.
The listeners needs to be set from the index.js to work on app killed state though. Otherwise it won't be handled as it won't have the same context as the headless task.