I also can't solve this, it really make me sad. Sigh..... But I finally make a compromise, USE MAC-Catalyst -_- I| ⬇️ Apple Doc: Mac_catalyst_Documentation - https://developer.apple.com/tutorials/mac-catalyst/turning-on-mac-catalyst

I confirm such facts: with  free provisioning profile (my persernal free apple-id,not developer), I can't run iOS-app on Mac-m1 by Xcode; 2.I got the developer team id from my colleague, I successfully run iOS-App on same Mac by Xcode. So , I guess ,for now ,apple did it on purpose. Just pay for the developer id , my friend.

My solution: modify the "Signing & Capabilities" --> "Team id", "Bundle Identifier" I got 2 team id, one is my personal(free account),another is my company's team developer id(not free account), I'm part of group. I crash at second account(and I checked the systemLog by Console,no useful information), so I change to the first one(free one), and it worked now. I don't know why. Ps: And, I'm confused, because at 4 month ago, apple don't allow free account run Mac-M1-iOS-App, I found it can run right now. (Today: 2021-11-03) My device : Mac-mini-M1 My macOS : 12.0.1 Xcode : 13.0

I am the person who ask this question, today it just fixed (about 5 seconds to launch Application), after I upgrade to Xcode13.0, emmmmmm, have nothing to say, for my view, it's just a BUG of Xcode12. Ps: when I use Xcode12, I doubt that whether my cmake-projects have loop-target-link,so I check and make sure there's not loop-link. Dyld3 takes so long time ,it's just the bug of Xcode12.

Ahhhh, why does Apple forum's reply comment board not support Markdown syntax. The mess of layout.... I just wanna enter new line....