Open jevakallio opened 7 years ago
Two related issues in react-native repo:
Worryingly, the first issue mentions this happens in production builds as well, just less frequently.
Turning off component animations alleviates the issue: When no animate
value is provided to Victory components, the app is more stable. I am able to still induce a crash by rapidly changing chart properties.
In a laymen language, this happens when a code confuses the debugging engine with what values to fetch. I suggest to reconsider the logic and check the structuring of the code.
Hi @hnrindani have you reproduced this issue recently, or was the comment unrelated? I believe this issue should be closed, since the underlying issue in react-native-svg
has been fixed and I have not seen these issues on Android for a long time.
The application crashes in Android GenyMotion simulator in a few situations, such as entering the VictoryArea example screen or changing the VictoryScatter symbol type.
These issues do not affect release builds, but make development and debugging very difficult.
Stacktrace from logcat: