[expo-modules-core] Ensure uuid.v4 and uuid.v5 imports available on old architecture

[andrejpavlovic]

Why

It seems that globalThis?.expo?.uuidv4 is undefined on iOS when this module is loaded. As a result, when trying to call uuid.v4 later in the code, it keeps throwing Native UUID version 4 generator implementation wasn't found in 'expo-modules-core' even though globalThis?.expo?.uuidv4 at that point is available.

I'm assuming in new architecture globalThis?.expo?.uuidv4 is set synchronously, so this would not be an issue. In old architecture however, it would be best to reference this value when executing v4 or v5 calls themselves.

How

Use direct reference to globalThis?.expo?.uuidv4 from inside uuidv4() functions to avoid referencing a stale value.

Test Plan

On iOS the error stops being thrown when calling uuid.v4 within a component.

import { uuid } from 'expo-modules-core'

export const MyComponent = () => {
  useEffect(() => {
    console.log(uuid.v4())
  }, [])
  return null
}

Checklist

• [*] I added a changelog.md entry and rebuilt the package sources according to this short guide
• [*] This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).
• [*] Conforms with the Documentation Writing Style Guide

[github-actions]

Subscribed to pull request

File Patterns	Mentions
packages/expo-modules-core/**	@Kudo, @lukmccall

Generated by CodeMention

[Kudo]

hi there! thanks for the fix. could you help to run the following command the build js files? that would help to resolve the check-packages ci error

$ cd packages/expo-modules-core
$ yarn prepare

[andrejpavlovic]

hi there! thanks for the fix. could you help to run the following command the build js files? that would help to resolve the check-packages ci error

@Kudo done!

[Kudo]

thanks again for having the fix!

[Thanaen]

Hello ! I also have this problem in version 51.0.39. Would it be possible to port this fix to version 51?