[ios][android] Migrate names of module definition components

[tsapeta]

Why

Follow up on #17098 and #17153
The packages for SDK45 used the deprecated names for compatibility reasons, but now we can migrate them to use the new names of the components.

How

Migrated the definition components on iOS and Android with the following rule:

• function -> AsyncFunction, or Function if it had .runSynchronously()
• capitalized all other components

Also updated the expo-module-template

Test Plan

Tests are passing
Manually checked NCL and test-suite

[thsantac]

Hi,
Got this error during iOS build with eas :

Compiling expo-keep-awake Pods/ExpoKeepAwake » KeepAwakeModule.swift
❌ (node_modules/expo-keep-awake/ios/KeepAwakeModule.swift:9:5)
7 |
8 | public func definition() -> ModuleDefinition {

9 | Name("ExpoKeepAwake")
| ^ cannot find 'Name' in scope
10 |
11 | AsyncFunction("activate", activate)
12 | AsyncFunction("deactivate", deactivate)

Is there a workaround ? Do not use this module by the way.
Thanks.

[tsapeta]

@thsantac Can you check which version of expo-modules-core do you have installed in your project? It seems to be too old. You can check that with npm ls expo-modules-core or yarn why expo-modules-core.
Also, you shouldn't have this package installed directly in your package.json, so make sure it's not there.

[thsantac]

Thanks for your reply. I have fixed the issue removing the package from package.json and from the project files. thsantac$ npm ls expo-modules-core Youseeme@ /Applications/MAMP/htdocs/Youseeme ├── ***@***.*** └─┬ ***@***.*** └── ***@***.*** Cordialement. Bonne journée. Thierry Santacana - 0630927608 ***@***.***

…

Le 30 août 2022 à 09:24, Tomasz Sapeta ***@***.***> a écrit : @thsantac <https://github.com/thsantac> Can you check which version of expo-modules-core do you have installed in your project? It seems to be too old. You can check that with npm ls expo-modules-core or yarn why expo-modules-core. Also, you shouldn't have this package installed directly in your package.json, so make sure it's not there. — Reply to this email directly, view it on GitHub <#17193 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC6RVPK6UXRTLHKBNRK4XDV3WZMXANCNFSM5UH75WQA>. You are receiving this because you were mentioned.