tfcornerstone

@mrousavy The following is causing issues in `runAsync`, it resolves when you get rid of `visionCameraProcessorPlugin.call`. It seems `visionCameraProcessorPlugin.call` works perfectly fine in default context, but not as expected in...

Related: https://github.com/margelo/react-native-worklets-core/pull/196/commits/552186a62b688c8e125e01fac51850a28086106a#diff-5626d984fb6c601e169493e0cdcd6f411cda50ad0672031afc78883b8289f60cR29 ...

> I'm trying to reproduce this issue on tests without success. Maybe this issue only happens with vision-camera installed. I'll keep testing here. I believe the example app for the...

Related: https://github.com/margelo/react-native-worklets-core/pull/196/commits/552186a62b688c8e125e01fac51850a28086106a#diff-5626d984fb6c601e169493e0cdcd6f411cda50ad0672031afc78883b8289f60cR29

There were complaints of it working on non releases. This seems to be the only code references that distinguishes the release on the plugin. Possibly the bug is composed around...

Does eas update generate runtime versions again, it doesn't have a `--profile` options, assuming the environment variable diff can cause issues? Potentially related https://github.com/expo/eas-cli/issues/2484