Kudo Chien
Kudo Chien
> If the app has installed a new update, will this new `reloadAppAsync()` method apply it? I anticipate two questions people will have are: why are there two reload methods...
> I think the names are clear but also think it would be helpful in the docs for each function to explain how it is different than the other function....
i was waiting for 0.74.1 for the changes from core and not using the reflection on android. since we may like to submit expo-go beforehand, i'm going to merge this...
this looks like something that we can add inside expo-build-properties, since it's CNG project only and not working for expo-go or bare project.
@bogdanbaghiu did you run the app through `npx run:android` or eas build or just expo-go? i encounter this error at first but then it's fine after re-run the app. then...
@bogdanbaghiu thanks for confirming that. it's interesting because the error happens only on expo-go but not `npx expo run:android` or `eas build`. i would take a further look later
it is possible that the issue was resolved by #27748 but we didn't backport the issue to expo-go. since we are prepare expo-go for sdk 51. could you try to...
does it work if we adding in this block? https://github.com/expo/expo/blob/705b518cc090d043862f1068a0660e350c758745/packages/expo-modules-core/ExpoModulesCore.podspec#L65-L73
trying to investigate more a little bit. it's again the import problem. the headers reside as the path `jsinspector_modern.framework/Headers/jsinspector-modern/InspectorInterfaces.h` which is not flattened. also in the code `#import `. that...
> The Swift pod `ExpoModulesCore` depends upon `React-jsinspector`, which does not define modules. oh this one should be better resolved from upstream.