Handle when serviceId is not present and store serviceId in keychain #28
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.
Handle when serviceId is not present and store serviceId in keychain
♻️ Current situation & Problem
Currently, there is an issue when running a reinstalled application where the firebase credentials where previously stored in the keychain that we don't have a reference to the previous serviceId as this is stored in localStorage.
This PR addresses this issue by (1) gracefully handling the error and (2) storing the server id in the keychain as well to have similar persistence as the firebase key.
⚙️ Release Notes
📚 Documentation
✅ Testing
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: