This may help, may not. I found that I couldn't debug something I was developing on my physical device. After tearing my hair out I deleted the app from my phone and when it tried to re-deployed I got the same error. I then realized that the APS Environment value in my entitlements was set to production rather than development. I changed it, deleted the app on the phone and re-deployed without error. Might not be the same issue, but this helped me.
rhodesie23
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 found that the option "Enable device-specific builds" was ticked in the Build properties of the release configuration in Visual Studio Mac. Unticked and then submitted, all good... HATE this error!!
I found that the option "Enable device-specific builds" was ticked in the Build properties of the release configuration in Visual Studio Mac. Unticked and then submitted, all good... HATE this error!!
I found that the option "Enable device-specific builds" was ticked in the Build properties of the release configuration in Visual Studio Mac. Unticked and then submitted, all good... HATE this error!!
Did anyone find a solution for this? I have the same issue for iOS 17. It was very sudden. I did a submission one day, then literally the next day I got this error when trying to go for review. I had not changed the icons. These haven't changed for YEARS. There are no alpha channels in these images. I have re-built the asset catalog, added 1024 images with different names, messed with the pinfo list and references in there... I have tried EVERYTHING I can think of / find online and I still get the same errors. I have pushed though 20 different builds with different solutions, NOTHING works?!
I have sent an email to support and NOT heard anything back. This is absolutely critical to get this update out to my customers, and I have another project which will probably have the same error which has real-world impacts for some big customers and I have this kind of nonsense stopping my submission.
I need a solution! PLEASE!
Mate did you get this working?? I need an answer to this too!