Migrate to Expo-Modules for Expo SDK 43 and newer about isomorphic-webcrypto

[olivierpascal]

+1

[marcato15]

+1

[charlestbell]

+1

[charlestbell]

I found a temporary workaround, which is to use Expo's classic build service, instead of their newer EAS build service. Unfortunately, the classic build service is deprecated and goes offline in about 160 days. So I'm reaching out to them and see if they can get EAS build to work like classic in this regard, or hold off on deprecating classic.

[charlestbell]

Update: The EAS guys gave a kind of "not my problem" response.
I also reached out to the guys in charge of microsoft's @azure/cosmos package and they're investigating finding a replacement for this package.

[TimoGlastra]

For yarn I found the following resolutions 'hack' to be working:

{
  // ... other package.json options ...
  "resolutions": {
    "@unimodules/react-native-adapter": "./node_modules/expo"
  }
}

[TimoGlastra]

I think this should be fixable by removing the dependency on the unimodules and instead updating to the expo modules. Not sure why it is needed to depend on the unimodules in the first place, couldn't we directly depend on expo-random?

@kevlened would you accept a PR for this change?

[czy0729]

@TimoGlastra
i solve the problem right now.
I've been trying to fix this for 50 hours, any solution that can be found is invalid.
at last i just remove @unimodules/core and @unimodules/react-native-adapter in package.json which tell you to migrating expo under 44 to expo modules at first https://github.com/expo/fyi/blob/master/expo-modules-migration.md#migrating-to-expo-modules.
then the build pass oh god.