[notifications][Android] Remove vernsioned `ExpoBadge Manager`
[notifications][Android] Fix BadgeManager not found in vendored code
[android] Fix compilation issues on main (#24311)
[expo-updates][android] Bare update manifest non-nullability parity (#23166)
[go] update stripe-react-native to 0.27.2 (#22917)# Why update vendoring modules for sdk 49 # How - `et uvm -m @stripe/stripe-react-native -c 'v0.27.2'` - backport native stripe version t
[go] update stripe-react-native to 0.27.2 (#22917)# Why update vendoring modules for sdk 49 # How - `et uvm -m @stripe/stripe-react-native -c 'v0.27.2'` - backport native stripe version to old sdks' podspec and build.gradle - transform manually - [android] remove `GooglePayButtonManager.kt`, `GooglePayButtonView.kt` - [android] remove `GooglePayButtonManager()` and `AddToWalletButtonManager()` in `StripeSdkPackage.kt` - [android] revert `import host.exp.expoview.R` change in `CardFormView.kt` - [ios] remove `stripe-react-native/ios/Tests/**/*` test files # Test Plan 1. clone and setup [stripe example app](https://github.com/stripe/stripe-react-native#run-the-example-app) 2. in `example/` - `yarn add file:/path/to/expo/packages/expo` - yarn add for `[email protected]`, `[email protected]` and other unsynced packages - and other necessary changes. i'd shared my patch file here: https://gist.github.com/Kudo/1d976feb403c325828b61b301bea3276 3. install unversioned expo go to simulator/emulator 4. modify the stripe cloned repo's maestro e2e test cases - cd `e2e-tests` - modify the ***.yml** file you want to test and replace `- launchApp` to ```yml - stopApp - openLink: exp://127.0.0.1:19000 ``` - replace the 127.0.0.1:19000 to the local dev-server address 5. run maestro test, e.g. `maestro --device {device_id} test -e APP_ID=host.exp.Exponent cardfield-basic.yml` 6. i only went through these test cases - cardfield-basic.yml - paymentsheet-basic.yml - paymentsheet-customFlow.yml
show more ...
[expo-updates][expo-go] Support new SDK version field in new manifests (#22356)
[expo-updates] Add support for extra params (#21837)
[expo-updates][android] Re-add support for v1 of the protocol (#21256)# Why This PR re-applies support for v1 of the expo-updates protocol and fixes versioned code compilation and adds a featur
[expo-updates][android] Re-add support for v1 of the protocol (#21256)# Why This PR re-applies support for v1 of the expo-updates protocol and fixes versioned code compilation and adds a feature to avoid a logical breaking change for old SDK versions. # How This does 3 things (in 3 commits): 1. Reverts https://github.com/expo/expo/pull/21226, which itself was a revert of the initial feature implementation PRs: https://github.com/expo/expo/pull/20275 and https://github.com/expo/expo/pull/21007. These are unchanged. 2. Fixes compilation of versioned code. 3. Adds a compatibility mode flag for Expo Go. ## How the compatibility mode flag works Expo Updates protocol v1 is a superset of v0. The diff is that v1 supports directives and also allows empty requests. We want to request v1 of the protocol in all cases, but for Expo Go, we can't do anything with rollbacks or no-ops (the current new features); put another way, Expo Go requires a manifest (which happens to be v0 of the protocol). Therefore, when loading in Expo Go, we require a manifest and ignore directives. Here's what the error will look like in Expo Go if a rollback is fetched: <img width="250" alt="Screenshot 2023-02-16 at 11 58 30 AM" src="https://user-images.githubusercontent.com/189568/219480436-d87616dc-ed70-45ed-8831-18d7f18aa6fb.png"> # Test Plan Run new tests for compatibility mode. Test manually to capture screenshot. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[android] fix expo go build errors (#21117)# Why fix expo go build error where kotlin 1.8 is incompatible with 1.6: https://github.com/expo/expo/actions/runs/4120016867/jobs/7114321156 # How
[android] fix expo go build errors (#21117)# Why fix expo go build error where kotlin 1.8 is incompatible with 1.6: https://github.com/expo/expo/actions/runs/4120016867/jobs/7114321156 # How - the underlying module of stripe 0.23.1 ships kotlin 1.8 which is prebuilt as aar/jar on maven central. we have no way to downgrade its kotlin version but only to upgrade kotlin in whole android expo go. - stripe 0.23.1 has a build error error and fixed at https://github.com/stripe/stripe-react-native/pull/1289. upgrade the vendoring module to 0.23.3. # Test Plan versioned android expo go + ncl launch test # Checklist - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[stripe] Upgrade stripe to 0.23.1 (#20964)
[android] backport fix for sdk47 to versioned code (#20062)# Why backport fix for sdk47 to versioned code # How - backport #19920 - backport #20037 - backport #20063
[Android] Backport #19723 and #19725 to sdk-47 (#19760)# Why Backports #19723 and #19725 to sdk-47 versioned code.
[android] add versioned code for sdk 47 (#19676)# Why add android versioned code for sdk 47 # How `et add-sdk -p android -s 47.0.0` # Test Plan android versioned expo go + NCL