Anton Plebanovich

The issue is localized in those lines: ```shell DEVELOPER_DIR="$(xcode-select -p)" # Verify that DEVELOPER_DIR points to an Xcode installation, rather than the Xcode command-line tools. if [ -x "$DEVELOPER_DIR/usr/bin/xcodebuild" ];...

@abhishekthanvi8 There are three possible solutions at the moment: - Fork `realm-swift`, apply suggested changes and use fork repo instead of the main - Manually fix the `RLMPlatform.h` file after...

I have the same issue. Though my dependency graph might be more complex the problem is the same. I also tried to use `Archive` but it did not help.

This answer was helpful https://stackoverflow.com/a/73844861/4124265 I had to manually sign all frameworks in the `PackageFrameworks` directory to be able to run the executable successfully. This looks like an Xcode issue...

I had to add post-build action as a workaround fix with this script: ``` # Resigning as a workaround for https://github.com/realm/realm-swift/issues/8575 # Framework resign for framework_path in "${BUILT_PRODUCTS_DIR}/PackageFrameworks/"*/; do framework_dir=$(basename...

Well, they switched to library `type: .dynamic` in the SPM which was not used previously. This mode might be buggy from the Apple side but in any case, it has...

In my case, `libarclite_iphoneos.a` was missing. I have a dependency in my pod spec on a framework that will likely not be updated. Workaround solution: https://stackoverflow.com/a/75920796/4124265

> This is not good solution, since using any cloud based CI will require doing it for every build. Also copying some files from external repo can be malicious. I...