Fix an error getting the providerId that could cause getCurrentUser to fail on android #706
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.
PR Type
What kind of change does this PR introduce?
PR Checklist
Please check your PR fulfills the following requirements:
Bugfixes:
New features/enhancements:
What is the purpose of this PR?
This is to fix #662 Where getCurrentUser could fail on android
Does this PR introduce a breaking change?
What testing has been done on the changes in the PR?
Tested by including my fork of the plugin in our app, and getting the current user. Not just in dev but also in production.
What testing has been done on existing functionality?
The auth code has been throughly tested from tzappia's branch, but not based on your current dev build, with the other PRs recently merged. I will so some testing on it with those merged.
edit: Tested done on this branch, using the auth emulator and a pixel 6. I did not encounter any issues during testing.
Other information