Luis Padron

I think a use case for not crashing is potentially logging these issues somehow.

@chiragramani Do you have time to finish this PR up? If not, I could look at finishing any remaining work. Thank you!

@chiragramani I'm going to merge this once CI passes on the latest `master`

Tested end-to-end on our project and got the expected crash and checks when using the new features. Thanks @chiragramani!

The example linked uses `rules_ios` along with some flags that could effect things here. If this is still an issue and reproing open an issue in `rules_ios`

Should this just be changed so that `--test_env` accumulates and takes whatever value it was provided literally? i.e. ```sh bazel build //Foo --test_env=FOO=bar,baz --test_env=OTHER=Something ``` ```sh FOO="bar,baz" OTHER="Something" ```

Do we maybe need something similar to: https://github.com/MobileNativeFoundation/rules_xcodeproj/issues/2722

I tested using just `macos_framework` and it fails as well: Previews log == DATE: Friday, February 23, 2024 at 2:48:27 PM Eastern Standard Time 2024-02-23T19:48:27Z == PREVIEW UPDATE ERROR: LinkDylibError:...

The dylib doesn’t seem to exist in derived data. But if I copy it there manually then it works correctly

Ah gotcha! Interestingly though I can't repro in the integration examples, previews work there for the macOS app