Still the same issue with XCode 12.5, why is this marked as solved??
pupasani
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I don't know why the above is marked as a solution. Just because the media team is aware of it doesn't mean the problem is solved. This issue still exists 9 months later!
I don't know why the above is marked as a solution. Just because the media team is aware of it doesn't mean the problem is solved. This issue still exists 9 months later!
This has been acknowledged as a known issue by the Media Team in July 2020, more than 9 months ago (see link below)! No idea why this is still not fixed. Just because its only happening on the simulator doesn't mean this is not a serious issue. I don't have devices lying around with all previous iOS versions. Apple please take this seriously!
https://developer.apple.com/forums/thread/652852
Glad to get confirmation this is a know issue. Have been seeing this issue since Big Sur came out. Any fixes for this yet? I don't have devices lying around to test with older iOS versions, not mention Apple doesn't allow downgrades!
I cannot believe the Media Team has not been able to solve this for more than 9 months after acknowledging the issue. What has happened to Apple's development process?? Apple please take this seriously!!