Nathan Ahn
Nathan Ahn
I believe it's an issue having to do with concurrency, and multiple calls to `addAssetID` sharing the same `audioReader`, `videoReader`, and `assetWriter`. I fixed this by moving those three variables...
Yep, you are correct! By default, your app clip uses the same JS bundle as your main app. I've done some experiments with different entry files but I've found in...
Support for the `*.clip.ts` extension has been added in `v0.5.0`! You can now have separate entrypoints (or any nested files) for the main app and the App Clip, so you...
@KrastanD Do you happen to have the command you were using when building locally? Running `expo run:ios --scheme --configuration Release` should specify which bundle should be built.
If anyone happens to run into this issue in the future, this same crash can also be caused by naming a monorepo `react-native`. Totally on me for poor naming conventions...
If anyone else stumbles upon this issue, I haven't found a solution to the original `getBundleIdentifier` problem. However, I did manage to differentiate between the app clip and main app...
Going to experiment, but I think there's a good chance this issue is related to [this commit](https://github.com/bndkt/react-native-app-clip/commit/7487d249abdf6f55316144ac53c10a34f21cae6b).
This issue only affects non-Expo modules. Expo modules are correctly handled with `use_expo_modules`'s `exclude` field, but non-Expo modules are going to require a custom implementation.
Fixed in #50.