fix: async save/create/update/replace use async/await deep save #418
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.
New Pull Request Checklist
Issue Description
Xcode 14 throws purple warnings for
hang risk
at runtime due to asynchronoussave/create/update/replace
needing to deep saveParseObject
's synchronously. It's okay for synchronous calls to have this warning as developers are choosing to hold the thread (because of the synchronous call), but this should not occur for async calls.Related issue: #n/a
Approach
ParseError
even though the server is wrong. This happens when the error thrown from the Parse Server only containserror
ormessage
, but does not contain acode
.TODOs before merging