Make sure currentUser is available upon startup #51
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.
Make sure currentUser is available upon startup
♻️ Current situation & Problem
We experience problems, where the Firebase
currentUser
was not directly available upon startup and therefore required busy-waiting approaches to make sure a firebase user is available on startup actions (e.g., see StanfordBDHG/PediatricAppleWatchStudy#83 (comment)).Firebase v11.6.0 fixes this issue with firebase/firebase-ios-sdk#14141, making sure that the
currentUser
is available immediately. We raise the minimum required Firebase version to the latest one and updated our code comments.⚙️ Release Notes
📚 Documentation
Updated inline docs.
✅ Testing
Added UI test to verify that user account is available inside
configure()
if user is logged in.📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: