Closed francois-pasquier closed 7 months ago
Can you provide a minimally reproducible repo? maybe fork from the starter kit so we can look into if it's a ViroCore problem or a ViroReact problem.
So this was due to using @react-navigation/native-stack
This is not happening with @react-navigation/stack
I guess the issue still stands though. What do you think?
I could provide a repro but basically using the native stack and accessing a screen often ends up with the crash.
hmm. We definitely want to warn people about this, so I think it is worth mentioning in the documentation somewhere. There must be some conflict under the hood. @doranteseduardo, what do you think?
Requirements:
Please go through this checklist before opening a new issue
Environment
Please provide the following information about your environment:
Description
I am getting a crash after going back and forth to the screen containing the Viro scene:
I tried with version 2.22.0: it's the same.
Repro
This seems to be triggered when I am not leaving enough time for the viro scene to set up properly.
Is there anything than can be done on the library level to prevent these errors with null pointer dereference?