feat: new architecture (turbo modules, fabric components) and unify return data from accounts sdk methods #579
Triggered via pull request
February 23, 2026 14:55
DanielOS7-TM
Status
Cancelled
Total duration
2m 29s
Artifacts
–
ci.yml
on: pull_request
lint
1m 4s
react-native-test
1m 11s
kotlin-test
2m 22s
build-library
1m 1s
build-android
2m 22s
build-ios
2m 23s
Annotations
7 errors and 10 warnings
|
kotlin-test
The run was canceled by @DanielOS7-TM.
|
|
kotlin-test
The operation was canceled.
|
|
build-android
The run was canceled by @DanielOS7-TM.
|
|
build-android
The operation was canceled.
|
|
build-ios
The run was canceled by @DanielOS7-TM.
|
|
CI
The run was canceled by @DanielOS7-TM.
|
|
build-ios
The operation was canceled.
|
|
lint:
src/IgniteProvider.tsx#L554
'primaryColor' is already declared in the upper scope on line 163 column 5
|
|
lint:
src/IgniteProvider.tsx#L553
'clientName' is already declared in the upper scope on line 162 column 5
|
|
lint:
src/IgniteProvider.tsx#L552
'apiKey' is already declared in the upper scope on line 161 column 5
|
|
lint:
example/src/navigators/Root.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 “Root” 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#L72
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#L60
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#L50
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#L47
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:
__tests__/IgniteProvider.test.tsx#L823
Disabled test suite
|
|
lint:
__tests__/IgniteProvider.test.tsx#L499
Disabled test suite
|