Xcode 15 Beta 4 Symbol Not Found Error

[lilidotshi]

Hi, we are running version 0.18.3, and launching the simulator on startup results in the following crash:

dyld[46534]: Symbol not found: _OBJC_CLASS_$_NSError
  Referenced from: <FDBC70ED-7153-3948-9082-A67AC8871822> /Users/lilishi/Library/Developer/CoreSimulator/Devices/E5962E48-526F-4F7A-9E3E-895C3BDB642F/data/Containers/Bundle/Application/A41D84BB-44F3-44DD-9086-DDB773C46C48/OurApp.app/OurApp
  Expected in:     <B52037D9-EA5E-3731-861B-495152967F91> /Users/lilishi/Library/Developer/CoreSimulator/Devices/E5962E48-526F-4F7A-9E3E-895C3BDB642F/data/Containers/Bundle/Application/A41D84BB-44F3-44DD-9086-DDB773C46C48/OurApp.app/Frameworks/react_native_blob_util.framework/react_native_blob_util

Going back to Xcode 14 works no problem, but installing and running from the new beta has this issue. Any help is advised! Thanks so much.

[RonRadtke]

Hard to tell what the problem is especially since i don't have xcode 15 running.
But it could be that you changed e.g. the depolyment ios version but did not fully recompile all sources.
Or e.g. pods must be reinstalled completely.
Sorry I can't teally help much here

[DavidBemerguy]

Same here, in my own project, which has lots of modules. Didn't find a fix so far

[lilidotshi]

Same issue on Xcode Beta 6. Deployment target has not changed, pod was reinstalled completely.

[lilidotshi]

Can confirm this is isolated to react-native-blob, removing from the list, and the app compiles ok.

[RonRadtke]

@lilidotshi @DavidBemerguy
My MacBook refuses to run xcode 14 or 15, so I need someone to debug and create a PR fixing this issue.

[lilidotshi]

@RonRadtke I think i found it, I'll submit a PR in just a bit.

[lilidotshi]

@RonRadtke #288

[lilidotshi]

@RonRadtke any thoughts on approving the PR I submitted? @DavidBemerguy if you're blocked on this and really want to use the beta, you can go ahead and edit the to match what i have in my PR in your node_modules folder in react native

[RonRadtke]

@lilidotshi Thank you for your PR! Awesome that you could help here.
In general I don't see any problems merging it - I'm a little confused about the problem though, and a little worried we might run into soem crashes due to not caught errors now... But will likely have to face that then.

But if you have an idea why that single change was needed, would be awesome to get to know - I can't seem to see the reason for the issue in xcode 15 with that

[lilidotshi]

To be honest, I have no idea. My current running theory is that the underlying Foundation framework that they bundle with the project in Xcode 15 changed, and where previously the @Try @catch block was able to handle non-exceptions, it no longer does. I opened up a forum post on the dev website: https://developer.apple.com/forums/thread/735610

[RonRadtke]

Thank you.
Based on what I can read it should never have been NSError... NSError is nothing that can be thrown and thus not be caught.
But likely that is one of the ancient code fragments in the lib.

I'll merge it tomorrow