Issue encountered with running Compose/iOS falling balls example :thread: :point_right:

# compose-ios

[darkmoon_uk]

Issue encountered with running Compose/iOS falling balls example 🧵 👉

[darkmoon_uk]

• On running iosDeployIPhone8Debug

External tool execution failed:
* Command: [/usr/bin/xcrun, simctl, boot, 332C50AD-35CF-4880-8138-57AAD41D042B]
* Working dir: []
* Exit code: 2
* Standard output log: /Users/chris/Projects/Other/compose-jb/experimental/examples/falling-balls-mpp/build/compose/logs/iosSimulatorBootIPhone8/xcrun-2022-07-24-11-53-20-out.txt
* Error log: /Users/chris/Projects/Other/compose-jb/experimental/examples/falling-balls-mpp/build/compose/logs/iosSimulatorBootIPhone8/xcrun-2022-07-24-11-53-20-err.txt

...where xcrun-2022-07-24-11-53-20-err.txt contains:

An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Unable to boot device because we cannot determine the runtime bundle.
No such file or directory

This returns very quickly and nothing is built (only logs inside build).
However if I invoke:
iosSimulatorBuildIPhone8Debug
...which generates the Xcode project, and then open/run the project from Xcode, it works!
...this suggests something is broken in the way current Compose/iOS plugins are invoking Xcode tooling 🤔 I'm using Xcode Version 13.4.1 (13F100)

[darkmoon_uk]

❓ Prepared to raise a YouTrack for this; but can anyone else confirm it first? This is a small way we can help Compose/iOS to reduce the noise for [JB]

[darkmoon_uk]

ℹ️ iosDeployDeviceRelease does work fine; once a team and unique bundle ID are set... so this issue seems related to Simulator; maybe the destination specifiers?

[Dima Avdeev]

Thanks, I will investigate!

[Dima Avdeev]

One of possible solution is to remove all simulators and try again:

sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService
rm -rf ~/Library/*/CoreSimulator