-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(app): ios sdk 10.27.0 / android sdk 33.1.0 #7820
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
5e116cd
to
ebb9add
Compare
As sometimes happens, android simply had a slow runner so it timed out. Didn't make it to the point where it's having trouble for me locally. Re-running. |
Well, that's a failure I've never seen before.
re-running to see if persistent or flake |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7820 +/- ##
=======================================
Coverage 69.90% 69.90%
=======================================
Files 150 150
Lines 5985 5985
Branches 1258 1258
=======================================
Hits 4183 4183
Misses 1713 1713
Partials 89 89 |
Would be great to have at least the iOS package updated asap since it most likely is the culprit of this issue we are facing: See: |
Yep - just needed to get it through testing - looks okay enough to go, will merge and release, hope it helps you @1337LutZ |
@1337LutZ released - also note that for things like this that are urgent for you, the "escape hatch" of being able to specify an override the firebase-ios-sdk version is always available --> https://rnfirebase.io/#ios |
@mikehardy Awesome and thanks! |
In the end this didn't fix our issue, however the 10.26.0 SDK added some better logging for these kinds of issues and that is what in the end helped us. Thanks again! |
Pretty standard update, however the android tests are failing for me locally, so I expect an e2e android test failure here, in the database test suite
If that occurs obviously will need to investigate for root cause, and even if it does not occur then I will need to determine what the environmental difference is such that it fails for me locally but not in CI
We'll see...