Skip to content

feat: enable compatibility with new architecture #212

feat: enable compatibility with new architecture

feat: enable compatibility with new architecture #212

Triggered via pull request November 13, 2024 16:07
Status Failure
Total duration 3m 53s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 11 warnings
build-ios
react-native-ticketmaster-ignite-example#build:ios: command (/Users/runner/work/react-native-ticketmaster-ignite/react-native-ticketmaster-ignite/example) /private/var/folders/1y/56hdyx6x0_jb18k7b4ys9b6w0000gn/T/xfs-65fe11e7/yarn run build:ios exited (66)
build-ios
Process completed with exit code 66.
build-library
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint: example/src/navigators/BottomTabs.tsx#L45
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “BottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
lint: example/src/navigators/BottomTabs.tsx#L57
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “BottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
lint: example/src/navigators/BottomTabs.tsx#L70
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “BottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
lint: example/src/screens/MyEvents.tsx#L5
Inline style: { height: '95%' }
lint: src/TicketsSdkEmbeddedAndroid.tsx#L67
Inline style: { flex: 1 }
lint: src/TicketsSdkEmbeddedIos.tsx#L33
Inline style: { flex: 1 }
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-ios
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-android
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3, actions/setup-java@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/