fix: Don't fill with empty images, fix expo Android build #85
ci.yml
on: pull_request
lint
21s
test
21s
build-library
18s
build-android
3m 5s
build-ios
7m 58s
Annotations
2 errors and 25 warnings
build-ios
fatal error: module 'RCTDeprecation' in AST file '/Users/runner/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/2VET1BCI500YL/RCTDeprecation-FA4CDKU9EFLS.pcm' (imported by AST file '/Users/runner/Library/Developer/Xcode/DerivedData/ReactNativeBottomTabsExample-gpermdiojumotfanieuoetwkxvbl/Build/Intermediates.noindex/PrecompiledHeaders/ReactTestApp-Bridging-Header-swift_3T61TZPOK4J9-clang_2VET1BCI500YL.pch') is not defined in any loaded module map file; maybe you need to load '/Users/runner/work/react-native-bottom-tabs/react-native-bottom-tabs/example/node_modules/.generated/ios/../../../ios/Pods/Headers/Public/RCTDeprecation/RCTDeprecation.modulemap'?
|
build-ios
fatal error: module 'RCTDeprecation' in AST file '/Users/runner/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/3UAURZXSV7IJ8/RCTDeprecation-FA4CDKU9EFLS.pcm' (imported by AST file '/Users/runner/Library/Developer/Xcode/DerivedData/ReactNativeBottomTabsExample-gpermdiojumotfanieuoetwkxvbl/Build/Intermediates.noindex/PrecompiledHeaders/ReactTestApp-Bridging-Header-swift_1TI8WSHSXVYCT-clang_3UAURZXSV7IJ8.pch') is not defined in any loaded module map file; maybe you need to load '/Users/runner/work/react-native-bottom-tabs/react-native-bottom-tabs/example/node_modules/.generated/ios/../../../ios/Pods/Headers/Public/RCTDeprecation/RCTDeprecation.modulemap'?
|
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/App.tsx#L86
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 “Navigation” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
lint:
example/src/Examples/MaterialBottomTabs.tsx#L11
Inline style: { width: 20, height: 23 }
|
lint:
example/src/Examples/MaterialBottomTabs.tsx#L21
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 “MaterialBottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
lint:
example/src/Examples/MaterialBottomTabs.tsx#L32
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 “MaterialBottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
lint:
example/src/Examples/MaterialBottomTabs.tsx#L41
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 “MaterialBottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
lint:
example/src/Examples/MaterialBottomTabs.tsx#L52
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 “MaterialBottomTabs” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
lint:
example/src/Screens/Article.tsx#L26
Inline style: { color: '#000' }
|
lint:
example/src/Screens/Article.tsx#L34
Inline style: { color: '#000' }
|
lint:
example/src/Screens/Article.tsx#L54
Inline style: { backgroundColor: '#fff' }
|
lint:
example/src/Screens/Article.tsx#L64
Inline style: { color: '#000' }
|
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-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/
|
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-ios
Run script build phase '[CP-User] [RN]Check rncore' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'React-FabricComponents' from project 'Pods')
|
build-ios:
ios/PageSelectedEvent.swift#L30
coercion of implicitly unwrappable value of type 'String?' to 'Any' does not unwrap optional
|
build-ios:
ios/PageSelectedEvent.swift#L30
coercion of implicitly unwrappable value of type 'String?' to 'Any' does not unwrap optional
|
build-ios:
example/node_modules/react-native-screens/ios/utils/UIView+RNSUtility.mm#L41
undeclared selector 'touchHandler' [-Wundeclared-selector]
|
build-ios:
example/node_modules/react-native-screens/ios/utils/UIView+RNSUtility.mm#L46
undeclared selector 'touchHandler' [-Wundeclared-selector]
|
build-ios:
example/node_modules/react-native-screens/ios/RNSScreenWindowTraits.mm#L168
'keyWindow' is deprecated: first deprecated in iOS 13.0 - Should not be used for applications that support multiple scenes as it returns a key window across all connected scenes [-Wdeprecated-declarations]
|
build-ios:
example/node_modules/react-native-screens/ios/RNSScreenWindowTraits.mm#L208
'statusBarOrientation' is deprecated: first deprecated in iOS 13.0 - Use the interfaceOrientation property of the window scene instead. [-Wdeprecated-declarations]
|
build-ios:
example/node_modules/react-native-screens/ios/RNSScreenStackHeaderConfig.mm#L97
method possibly missing a [super reactSuperview] call [-Wobjc-missing-super-calls]
|
build-ios:
example/node_modules/react-native-screens/ios/RNSScreenStackHeaderConfig.mm#L102
method possibly missing a [super reactSubviews] call [-Wobjc-missing-super-calls]
|
build-ios:
example/node_modules/react-native-screens/ios/RNSScreenStackHeaderConfig.mm#L722
method possibly missing a [super insertReactSubview:atIndex:] call [-Wobjc-missing-super-calls]
|