Repository navigation
docs(📚): say what the background hold costs and how to stop producing - #611
Merged
Merged
Conversation
A held promise settles only once the app is back, what is submitted in the background stays in memory and then runs all at once, and turning the toggle off loses the device. Show a render loop that stops submitting.
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
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.
Docs only. Makes the iOS and tvOS "Background and foreground" section more useful for the behavior that ships today.
onSubmittedWorkDone()ormapAsync()promise settles only once the app is back, so background code awaiting one waits until then. This replaces "Nothing changes for your code".AppStaterender loop example.gpu-device-extensions).Not covered: whether held work can get a backgrounded app killed, which has not been measured on a device.
Not run: the docs build.