Skip to content

feat(app, sdks)!: update underlying SDKs w/related forward porting #7157

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

Merged
merged 8 commits into from
Jun 5, 2023

Conversation

mikehardy
Copy link
Collaborator

@mikehardy mikehardy commented Jun 4, 2023

Description

This PR contains a number of independent commits but all of them bring the underlying software up to date - review should be done commit-by-commit

This is a breaking change in that it requires higher minimum versions of transitive dependencies - specifically:

  • firebase-ios-sdk 10.8.0+ requires Xcode 13.3+ which transitively requires macOS 12+
  • firebase-ios-sdk 10.10.0+ requires Xcode 14.1+ which transitively requires macOS 12.5+

Each of these steps implies sets of older Apple hardware that are no longer officially supported, however if you are affected by this and your old hardware is still otherwise functional, you may enjoy https://dortania.github.io/OpenCore-Legacy-Patcher/

Related issues

Multiple issues resolved in the upstream firebase-ios-sdk / firebase-android-sdk repositories, and adopting their newer versions resolves the issues transitively for consumers of react-native-firebase

Release Summary

Multiple independent commits prepared for a rebase+merge, each one following conventional commit conventions

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
    • Yes
  • My change supports the following platforms;
    • Android
    • iOS
  • My change includes tests;
    • e2e tests added or updated in packages/\*\*/e2e
    • jest tests added or updated in packages/\*\*/__tests__
  • I have updated TypeScript types that are affected by my change.
  • This is a breaking change;
    • Yes
    • No

Test Plan


Think react-native-firebase is great? Please consider supporting the project with any of the below:

mikehardy added 4 commits June 3, 2023 16:55
This is speculative and unique to a dev environment situation I have
where the emulator is on a different machine and it is more convenient
for me to forward the ports required if they are stable instead of
ephemeral. I don't *think* this will affect anyone else negatively as
we are not running multiple detox instances on the same machine that
I know of, but this may be removed without discussion if it causes
harm to anyone anytime
the modular tests include a v8 compatibility test section, which
was otherwise duplicate of the main test file

move the modular test file into the main test file's place
@vercel
Copy link

vercel bot commented Jun 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
react-native-firebase ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 5, 2023 3:55am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
react-native-firebase-next ⬜️ Ignored (Inspect) Jun 5, 2023 3:55am

….5.0

BREAKING CHANGE: firebase-ios-sdk 10.8.0 and higher require Xcode 13.3+,
which transitively requires macOS 12.0+. You must update your CI build environments
to meet these minimums as well as your development environments - if you have older
hardware that still works but cannot be upgraded normally, you may like:
https://dortania.github.io/OpenCore-Legacy-Patcher/
@codecov
Copy link

codecov bot commented Jun 4, 2023

Codecov Report

Merging #7157 (1e82182) into main (a58ea4b) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #7157      +/-   ##
============================================
+ Coverage     54.00%   54.01%   +0.01%     
  Complexity      734      734              
============================================
  Files           230      230              
  Lines         11503    11501       -2     
  Branches       1854     1853       -1     
============================================
  Hits           6211     6211              
+ Misses         4949     4947       -2     
  Partials        343      343              

…moved

Note that forcing server retrieval of firestore named queries against loaded
firestore data bundles may fail on android with this SDK version. It appears
results will always come from the local cache.

BREAKING CHANGE: the "safetyNet" provider for App Check has been removed
from the underlying firebase-android-sdk and we have removed it here. You
should upgrade to the "playIntegrity" provider for App Check
BREAKING CHANGE: this version of the underlying firebase-ios-sdk has
a minimum Xcode requirement of 14.1 which transitively implies a macOS
minimum version of 12.5
@mikehardy mikehardy changed the title feat(app, sdks)!: update underlying SDKs w/related forward ports WIP feat(app, sdks)!: update underlying SDKs w/related forward porting Jun 5, 2023
@mikehardy mikehardy added the Workflow: Pending Merge Waiting on CI or similar label Jun 5, 2023
@mikehardy
Copy link
Collaborator Author

android just passed on the last commit - it's really slow so I will not wait for it again but the final commit I just pushed is iOS-only so that has no impact

Need to peel an issue off to investigate the source behavior for firebase named queries on collections cached locally from loaded bundles, that behavior has changed in android and ios SDKs since prior versions

- pod install can take as much as 16 minutes now
- compile + pod install on new SDKs can take more than 60 minutes combined
@mikehardy mikehardy removed the Workflow: Pending Merge Waiting on CI or similar label Jun 5, 2023
@mikehardy mikehardy merged commit bcc1a49 into main Jun 5, 2023
@mikehardy mikehardy deleted the @mikehardy/dependency-updates branch June 5, 2023 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant