FileCache throws NullReferenceException #3105
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.
FileCache.InitializeTypeAsync(Stream...) should not return null. It should return
Task.FromResult<StorageFile>(null)
. Otherwise, CacheBase attempts to dereference the Task to call ConfigureAwait(false) which results in a NullReferenceException.Fixes #3104
PR Type
What kind of change does this PR introduce?
What is the current behavior?
If the Uri has not already been cached, calling the following throws a NullReferenceException
What is the new behavior?
No NullReferenceException is thrown.
PR Checklist
Please check if your PR fulfills the following requirements:
Other information
I also updated the what the InitializeTypeAsync(StorageFile...) return to be consistent with the other InitializeTypeAsync(Stream...) return. In the end, Task.FromResult is the more appropriate thing to return when your asynchronous method does not await.