This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
iOSSimulatorFlush for known iOS Simulator issue with invalid_token #66
Conversation
This file contains 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
|
Awesome, thanks for this very useful addition! |
|
I had switched variable names midstream and thought I had synced them before this PR. I was wrong 😦. #67 has fix for the readme so it is iOSEmulatorFlush (emulator, not simulator). @EddyVerbruggen , thanks for adding the typings and for this plugin! |
|
👍 |
EddyVerbruggen
added a commit
that referenced
this pull request
Apr 18, 2017
iOSSimulatorFlush for known iOS Simulator issue with invalid_token
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When using the angular-firebase branch of the NativeScript/sample-Groceries repo, I switched the config's
apiURLto my own firebase project and received the invalid_token issue with my iOS Simulator, which was very similar to your documented Known Issues in the readme. Adding an option toinitnamediOSSimulatorFlushto try to callauth().signOutresolves the issue with the simulator holding onto an invalid_token.