The two probable causes are:

1. An internal error from react native: Currently there’s an issue open with regard to this error showing up. This occurs currently on version 0.76.5. It’s an autolinking bug introduced while ago when a new feature was being worked on.
2. The second is if by any means a dependency you installed is broken. My scenario came about when I was building a pure C++ turbo module for android and forgot or more or less didn’t know I was to link it to libboost_atomic.so in my CmakeLists.txt. I ported the code from a desktop app I worked on and never did need to link to that specifically. I linked to other things like boost thread and filesystem however. The error that showed the missing .so file showed up in Android Studio’s logcat just before this error showed up. The emulator screen tells you half truths most of the time. So trying probing your dependency list to see if any is faulty. Check your logcat output also.