Tpi 285 upgrade react - #60
Conversation
… code and swift code
…use node 24 and setup correct version of ruby
| @@ -0,0 +1,5 @@ | |||
| // Global JSX namespace shim for @types/react@19 compatibility. | |||
| // React 19 moved JSX to React.JSX; this restores the global JSX.Element alias. | |||
| declare namespace JSX { | |||
There was a problem hiding this comment.
If we're setting up JSX as a global alias, is the import in some other specific files in this PR necessary?
There was a problem hiding this comment.
Will look if they other imports are unnecessary now, cheers
fix: populate Gemfile.lock checksums after cocoapods upgrade update readme and e2e script to better select device update tests, and dependencies plus ci fix for ios update gemfile lock to point away from vulnerable activesupport versions and update ios-unit ci update to macoc-15 for unit create simulator for ios ci tests update podfile min target and build.gradle to not fail on emtpy tests remove duplicate ios simulators fix native unit tests update e2e tests make sure to install ios simulator update e2e github action to try and optimise the flow add concurrency cancel in progress to unit and dependency fix prepack order in android e2e added property check and restored challenge test to android fix gradle
f1916b0 to
c513585
Compare
| @@ -0,0 +1,4 @@ | |||
| export enum Colors { | |||
There was a problem hiding this comment.
can we import the other one created? or not possible?
There was a problem hiding this comment.
yeah can probably just have one actually.
| {paths: [process.argv[1]]}, | ||
| )', __dir__]).strip | ||
|
|
||
| MIN_IOS_VERSION='16.0' |
There was a problem hiding this comment.
would've preferred to refer to this variable (wherever it is) and set that in one spot vs hard-coding here.
If we need to bump it up in the future, might be hard to know to do it here too
There was a problem hiding this comment.
centralised it on package.json
…and fixing some types in tests podfile.lock update fix import for min ios version for example podfile
e158dff to
05e5aed
Compare
| jobs: | ||
| android-e2e: | ||
| runs-on: ubuntu-latest | ||
| timeout-minutes: 120 # <-- was unbounded (default 360 = your "hours") |
There was a problem hiding this comment.
nitpick, do we need the comments here?
| ./gradlew assembleRelease --no-daemon | ||
| env: | ||
| GITHUB_PACKAGES_USER: ${{ github.actor }} | ||
| GITHUB_PACKAGES_TOKEN: ${{ secrets.PACKAGE_READ_PAT }} |
There was a problem hiding this comment.
quick question, where does this token come from? does it ever expire? do we need to document something in the readme for the future
There was a problem hiding this comment.
App platform set this for us I believe. I got them to update as it was expired when I started working on it. Might just put a note in the TYRO_README
| /> | ||
| </SafeAreaView> | ||
| <SafeAreaProvider> | ||
| <SafeAreaView style={{ flex: 1, backgroundColor: 'transparent' }}> |
There was a problem hiding this comment.
nitpick, i know we introduced the enums for other colours, is this one not used widely enough?
There was a problem hiding this comment.
Will add this one to the Colors enum, and then move the enum out of tests and update imports
| visible: "SUCCESS" | ||
| timeout: 150000 | ||
| timeout: 300000 | ||
| # With the SDK upgrade we have lost the ability to detect the password field, |
There was a problem hiding this comment.
any reason why all of these are a comment?
There was a problem hiding this comment.
left as a reasoning for future improvement to restore this UI test to its full flow, but can probably just remove it fully
| rootProject.name = 'TyroPayApiReactNative' | ||
| apply from: file("../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesSettingsGradle(settings) | ||
| include ':lib' | ||
| includeBuild('../node_modules/@react-native/gradle-plugin') |
There was a problem hiding this comment.
is this a duplication of the pluginManagement block?
There was a problem hiding this comment.
We do need both here. without the root level includeBuild gradle would try and fetch it from maven repositories and the build will fail.
I just tried to remove it which caused the build to fail locally
| apply plugin: "com.android.application" | ||
| apply plugin: "org.jetbrains.kotlin.android" | ||
| apply plugin: "com.facebook.react" | ||
| apply plugin: "kotlin-android" |
There was a problem hiding this comment.
Should we remove apply plugin: "kotlin-android" since we have the org.jetbrains.kotlin.android?
There was a problem hiding this comment.
Yep it seems we can remove this
…d another color enum and accepted a security flag for a dev only dependency as no easy work around available update tyro read me, remove unused e2e test code and restore example gradle plugin
873ba23 to
a5f705e
Compare
PR
Upgrade SDK to be compatible with RN v0.86.0 <-> RNv0.78.0
Upgrade Example app to be using RN v0.86.0 as our main target
Testing
Android
iOS