Might be related to the other issue I posted In that issue, we were passing a non-ISO date string to the Javascript new Date(). It works for some of the devices (Javascript runtime) but didn't work for all of them. And we make this call at a global level so it's causing the entire ReactNative app to crash. new Date("2023-01-01") // Invalid for SOME devices (Javascript runtime) new Date("2023-01-01T00:00:00.000Z") // Valid for all devices

Might be related to the other issue I posted In that issue, we were passing a non-ISO date string to the Javascript new Date(). It works for some of the devices (Javascript runtime) but didn't work for all of them. And we make this call at a global level so it's causing the entire ReactNative app to crash. new Date("2023-01-01") // Invalid for SOME devices (Javascript runtime) new Date("2023-01-01T00:00:00.000Z") // Valid for all devices

After several hours of debugging, I found out that it was because we were passing a non-ISO date string to the Javascript new Date() object. It works for some of the devices (Javascript runtime) but didn't work for all of them. And we make this call at a global level so it's causing the entire ReactNative app to crash. new Date("2023-01-01") // Invalid for SOME devices (Javascript runtime) new Date("2023-01-01T00:00:00.000Z") // ISO date string valid for all devices

@Claude31 Yes, we're using the react native netinfo package to fetch the connection status when the App launch. And also used the expo-network package to get the IP address. Is it possible that the regional issue is caused by this? And how can we reproduce it since we've tried VPN to Ireland and it works.

After discussing with Apple, they found that it only crashes in Cork, Ireland. But works well in the U.S. and Taiwan. I've posted another question about it, please let me know if anyone has any idea about it, thanks! https://developer.apple.com/forums/thread/722829