fix: implement persistent auth session using expo-secure-store #5
Triggered via pull request
June 1, 2026 18:45
Midoriya-w
synchronize
#305
Status
Failure
Total duration
47s
Artifacts
–
ci.yml
on: pull_request_target
Annotations
6 errors and 3 warnings
|
mobile-ci
Process completed with exit code 1.
|
|
mobile-ci:
apps/mobile/src/screens/TeamsScreen.tsx#L3
'FlatList' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/TeamsScreen.tsx#L1
'useCallback' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/TeamDetailScreen.tsx#L7
'Icon' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/ScanScreen.tsx#L107
'err' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/EventsScreen.tsx#L1
'useCallback' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/HomeScreen.tsx#L254
Inline style: { opacity: 0 }
|
|
mobile-ci:
apps/mobile/src/navigation/MainTabs.tsx#L110
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 “TabNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
mobile-ci:
apps/mobile/src/navigation/MainTabs.tsx#L99
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 “TabNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|