Chee Kit

@alanjhughes it's unclear to me too, however the PR modifies `URL` in `Convertibles.swift` (see [here](https://github.com/alanjhughes/expo/blob/1af1b6211cceacf8639651fca3a11d8de63a803a/packages/expo-modules-core/ios/Swift/Arguments/Convertibles.swift)) which is an extension of `URL` in Foundation, so it definitely has something to do...

Did you clone the correct branch? Check `expo-modules-core-url-crash`

@alanjhughes I'll add that doing ```json "resolutions": { "expo-modules-core": "1.5.5" } ``` fixes it, so it should be a regression caused `1.5.6` instead, sorry for the mistake. It should be...

@tsapeta agree. I only posted the overrides 'solution' to bring attention to the fact that `1.5.6` introduced a regression.

Experiencing this as well

@douglowder I see the issue as well. You might have to launch the app several times, for me it starts bugging out after the second launch.

> Same. > > My quickest way to get this error is to launch a dev build with "JS Dev Mode" disabled. > > Also, this error was already in...

@Kudo this is the result: ``` yarn why v1.22.19 [1/4] 🤔 Why do we have the module "react-native-reanimated"...? [2/4] 🚚 Initialising dependency graph... [3/4] 🔍 Finding dependency... [4/4] 🚡 Calculating...

@Kudo still no dice. I have a feeling you'll see more reports of this once people start releasing builds with SDK 49 to the public. I realise that not many...

@Kudo it might have been `expo` after all, after bumping `expo` dependencies to the latest round of updates, the issue has resolved itself. Will close this next week if it...