Reference: https://github.com/swiftlang/swift-build/blob/f49864e7aac2143bafb7c4dc37635bdf52aab8da/Sources/SWBTaskExecution/TaskActions/FileCopyTaskAction.swift#L125

Just my layman guess. powersync-sqlite-core is a static xcframework. The contents of the framework is copied in to the app to /FitWoody-Watch.app/Frameworks/powersync-sqlite-core.framework/ But, my interpretation of the swift-build source, is that the framework must have a binary. So it creates a stub binary with name powersync-sqlite-core mobile.installd on iOS26 simulators seems to reject that file.

I believe I am seeing the same issue as you @asiergmorato . I have reported it as FB18656704

We have been informed through Japan developer relations that the issue was fixed in iOS18.3.2. Also the Update release notes mentions (sorry, this is from the Japanese release notes): 一部のストリーミング コンテンツを再生できなくなることがある問題に対応しています。 Translated: Addresses an issue that could prevent playback of some streaming content.

The mail accidentally used an invalid address. There's information in another thread what to do: https://forums.developer.apple.com/forums/thread/763163?answerId=810365022#810365022

"Repeated Build & Run targeting iOS 16.1 and later simulator runtimes may sometimes result in a hung launch. (101990080)" Not sure where that 16.1 comes from. For us it happens on older versions than 16.1 too...

The suggestion from Apple in the FB is to use audiovisualBackgroundPlaybackPolicy = .continuesIfPossible.

Reported FB12038560

My experience is the same. It reproduces when running Xcode in Rosetta mode. Sadly I have to run Xcode in Rosetta mode because of a slow 3rd party... (Hi Google).