Xcode 13.2.1 by now, it's still buggy...
Something like property wrappers with quotes (@Environment() and something like that), or the most used DispatchQueue won't highlight properly...
It's really confusing as if Apple developers and testers never used Xcode for at least once and upload new versions without any check...
Post
Replies
Boosts
Views
Activity
For anyone is using Xcode 13.2 and above, and still getting this error:
Remove any API using Swift Concurrency and re-archive your build.
If you're not using any Swift Concurrency API, however, using Alamofire, you should know that Alimofire's newest release (5.5.0) has added Swift Concurrency support. That's the reason why you're getting this error. Downgrade Alamofire to 5.4.4 and reset package caches, then re-archive. This would hopefully solve this issue.
For any further information, this issue seems fixed in latest Xcode 13.3 Beta (never tried though). You might wanna wait for next stable release of Xcode to use Alamofire 5.5.0.
Just in case someone is using Alamofire 5.5.0, please downgrade to 5.4.4 as 5.5.0 added Swift Concurrency support. Then reset package caches and re-archive.
Found the solution!
I'm using Xcode 13.3.1, follow the instructions below:
Go to your-target -> Edit Scheme (next to the picker of your devices).
Then go to Run -> Arguments.
Inside Environment Variables, add Name OS_ACTIVITY_MODE and Value disable.
Close the window and rebuild your target!
Hopefully can help!