Same. Sad to see this issues from 2023 with no response. What's the alternative? Any clue?

How is it possible to effectively debug network changes on a physical iPhone (which is recommended by Apple for a more accurate testing environment) if disabling the device's Wi-Fi while connected to Xcode via USB disrupts the debugging process? This presents a real challenge that needs to be addressed. UPDATE: Feedback created - FB13601388

I finally found what was missing and I'm a little embarrassed. I changed the "Show run destination" to "Always" and things started working. That's it. So simple but hard to understand based on the message.

In my case, the issue was because the Runpath Search Paths (LD_RUNPATH_SEARCH_PATHS) was empty. I cleared that build setting by mistake. I added @executable_path/Frameworks to the Runpath Search Paths, which was the right setting for my case, and I was able to submit the app to the App Store.

Same happened to me and the issue was because the Runpath Search Paths (LD_RUNPATH_SEARCH_PATHS) was empty. I cleared that build setting by mistake. I added @executable_path/Frameworks to the Runpath Search Paths, which was the right setting for my case, and the widget started working again.

Xcode 13.3 beta 1 has a fix for the crash.

Xcode 13.3 beta 1 has a fix for the crash.

I've the same question. I know it's not possible to remove the IAP but it's possible to put it unavailable using the "cleared for sale" flag. I want to know what happens when the subscription is "cleared for sale", what happens to the active subscriptions?