If you haven't received a response for a significant amount of time, try revoking your application and reapplying. Make sure your description of why you actually need to use the hardware is concise, honest, and compelling. I rushed my initial application and my pitch for why I needed it probably indicated as much. After not hearing anything for over a month, I followed my own advice by revoking and reapplying with a more thoughtful explanation for why I needed it. I was approved a few days later.

Sadly, setting DEAD_CODE_STRIPPING to NO does not resolve the issue for me. I'm having the issue with a dynamic library, so perhaps that setting doesn't help in that situation. I also tried setting PRESERVE_DEAD_CODE_INITS_AND_TERMS to YES. This didn't help either. UPDATE: It looks like linking against a dynamic lib from a swift package, the -dead_strip flag is added no matter what.

Same problem here with Xcode 12.5 & iOS 14.5.

The simplest way I've found to avoid this madness is to always switch to my main app's scheme and select "Any iOS Device" before staging/committing. If that results in a change for you, you'll have to commit that change, but that should be the last time you have to if as long as you always select "Any iOS Device" before staging/committing going forward.

@angarov Did you request the new entitlement? If so, did Apple approve your request promptly?

The problem continues with macOS 12.4.

Noticed the same thing just now

I filed a feedback, FB11280425, about this awful behavior on 8/16/22. Still no response from Apple and the problem persists in the latest Xcode 14.1/iOS 16.1 betas. Here's the sample project I created for it: https://github.com/gcox/SwiftUIBugs/tree/main/SwiftUI_ForEach_Behavior

This problem has been resolved in macOS 13. That said, it's concerning that whatever the underlying fix was has not been back-ported to macOS 12.x. I worry the fix was unintentional since it has been fixed since early in the macOS 13 beta cycle. If the fix was intentional, that means Apple has known about the problem for months without fixing the issue in macOS 12.x, which seems unlikely. I hope this doesn't get reintroduced.