Fix Storage usage of invalid pointers. #1574
Merged
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.
Description
As reported in #1570, if
StorageReference::GetFile()
is called from a non-UI thread, theconst char* path
passed in is not preserved and could have been deleted by the calling code once theFIRStorage
native call occurs in the main thread later.Fix this by creating the URL from the local file path outside outside of the thread dispatch block. (Similar to what
PutFile()
already does.)Testing
Integration tests in this PR.
Type of Change
Place an
x
the applicable box:Notes
Release Notes
section ofrelease_build_files/readme.md
.