You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know how this is even possible, I suspect @babel/preset-env but I'm creating this issue to reference to/from react-native's repo to get some help on figuring out exactly what's going on.
Using 1.0.4 react-native's Linking.getInitialURL() promise never resolves, somehow whatever changes were made since 1.0.1 block the core js-to-native bus from resolving promises in native land. This is such basic functionality and again I don't understand how it is even possible for a secondary package to create such a mess.
Hang tight, I'll update this thread with more info as I get it.
Anyone finding their way here, use [email protected] with react-native for now if you're having issues.
The text was updated successfully, but these errors were encountered:
Thank you for raising this! Would gladly merge the PR for that. The change, which might have affected this behavior is using core-js for polyfiling. Unfortunately, I don't have a good way to test in react-native environment. Sorry for the mess :/
I don't know how this is even possible, I suspect
@babel/preset-env
but I'm creating this issue to reference to/from react-native's repo to get some help on figuring out exactly what's going on.Using 1.0.4 react-native's
Linking.getInitialURL()
promise never resolves, somehow whatever changes were made since 1.0.1 block the core js-to-native bus from resolving promises in native land. This is such basic functionality and again I don't understand how it is even possible for a secondary package to create such a mess.Hang tight, I'll update this thread with more info as I get it.
Anyone finding their way here, use [email protected] with react-native for now if you're having issues.
The text was updated successfully, but these errors were encountered: