ANDROID - New Architecture crash on refresh #33665
Labels
Impact: Crash
Platform: Android
Android applications.
Priority: High
Resolution: Answered
When the issue is resolved with a simple answer
Tech: React Native Core
Issue related to the Core of React Native
Type: New Architecture
Issues and PRs related to new architecture (Fabric/Turbo Modules)
Description
When running on the architecture, refresh does not work on android and causes crash
I have added the part of the logcat crash log from below(there are a lot of errors that happen as a result of the refresh)
Looks like the source of the error is from
/Users/yotamishak/aaa/temp/projectName/node_modules/react-native/ReactAndroid/../ReactCommon/react/renderer/mounting/ShadowTreeRegistry.cpp:17: function ~ShadowTreeRegistry: assertion failed (registry_.empty() && "Deallocation of non-empty `ShadowTreeRegistry`.")
....there's more where that came from
Also, when building I saw the following warnings
Version
0.68.1
Output of
npx react-native info
System:
OS: macOS 12.1
CPU: (8) arm64 Apple M1
Memory: 117.97 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.18.2 - ~/.nvm/versions/node/v14.18.2/bin/node
Yarn: 1.22.11 - ~/node_modules/.bin/yarn
npm: 8.3.0 - ~/.nvm/versions/node/v14.18.2/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 28, 29, 30, 31
Build Tools: 26.0.2, 28.0.3, 29.0.2, 30.0.2, 30.0.3, 31.0.0
System Images: android-30 | Google Play ARM 64 v8a, android-31 | Google APIs ARM 64 v8a, android-Tiramisu | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8309675
Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild
Languages:
Java: 11.0.14.1 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.68.1 => 0.68.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: