javascript – Expo App crashes in manufacturing Construct on TestFlight

I’ve a React-Native Expo iOS app that labored simply advantageous till now. After I run the construct with expo run:ios it really works completely on the simulator however after I construct it for manufacturing it instantly crashes after I open it.

I get the next error log in my xcode console.

Invariant Violation: Did not name into JavaScript module methodology RCTDeviceEventEmitter.emit(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 0): .
          A frequent reason behind the error is that the appliance entry file path is wrong. This may additionally occur when the JS bundle is corrupt or there may be an early initialization error when loading React Native., js engine: hermes

Unhandled JS Exception: Invariant Violation: Did not name into JavaScript module methodology AppRegistry.runApplication(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 0): .
          A frequent reason behind the error is that the appliance entry file path is wrong. This may additionally occur when the JS bundle is corrupt or there may be an early initialization error when loading React Native., js engine: hermes

*** Terminating app because of uncaught exception 'RCTFatalException: Unhandled JS Exception: Invariant Violation: Did not name into JavaScript module methodology AppRegistry.runApplication(). Module has not been registered as callable. Bridgeless Mode: false. Registered callable JavaScript modules (n = 0): .
          A frequent reason behind the error is that the appliance entry file path is wrong. This may additionally occur when the JS bundle is corrupt or there may be an early initialization error when loading React Native., js engine: hermes', motive: 'Unhandled JS Exception: Invariant Violation: Did not name into JavaScript module methodology AppRegistry.runApplication(). Module has not been registered as callable. Bridgeless ..., stack:
invariant@1965:25
__callFunction@28223:21
nameless@28036:30
__guard@28162:14
callFunctionReturnFlushedQueue@28035:20
'
*** First throw name stack:
(0x1833425fc 0x1808bd244 0x1026faeec 0x10239b15c 0x10239b984 0x183344e34 0x183343e7c 0x1833a7a38 0x10272fc90 0x102731da4 0x1027319f8<…>

I attempted actually every part already from updating all my attainable dependencies, prompting each attainable AI software for options and so forth. Nothing helped thus far. My entry file path and so on. can be appropriate as I checked it like 10000x instances.

Now right here comes the tough most complicated half:
I cloned my repo once more and went again to the final profitable commit. I up to date the model numbers to the present one, construct it and deploy it on TestFlight -> The construct works and I can use the app. After I copy the very same listing of the working codebase and paste it into my precise repository on the most recent commit and construct it once more (NOT A SINGLE LINE OF CODE CHANGED) it crashes. So I dont actually understand how this will occur that it really works on the outdated commit however crashes on my new commit.

I already tried to take away my entire repository from my laptop and clone it some place else once more as a result of I assumed it might has one thing to do with caching but it surely additionally doesnt work.

I attempted all of the options discovered on GitHub points or StackOverflow, however none of them labored.

This, This, This and so forth.

Additional Info:

I additionally thought is has one thing to do with react-native-reanimated or react-native-gesture-handler versioning however 1. they didnt change since my final profitable construct, 2. the put in variations are suitable with my react-native model (0.74.5) expo ([email protected]).

I ran expo-doctor 1,000,000 instances.

I attempted to construct it with out my customized entry level (index.js) utilizing the default one supplied by expo.

I exploit @react-native-firebase and up to date these dependencies to essentially the most suitable variations.

The xcode logs earlier than the crash do not give any beneficial info or errors in any respect.

Clearly I cleaned the xcode builds and cached knowledge with xcode, ran expo prebuild --clean & pod set up and so on.