@arcangel06 - can you post the filenames you used for one of your icons?
developer555
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
Strange, it's no longer happening for me.
Yes, still happening here as well.
Thank you, @DavidOgdenStiers - this worked! Finally no more extra emails for every build submitted.
Where did you put this?
I added the NSHTTPURLResponse to my earlier feedback in case that's helpful (FB11577100).
Yes, it is an old-style WatchKit app + WatchKit extension app, but I'm not sure when I stopped seeing crashes in Organizer - it may have stopped several Xcode versions ago, but I only just recently needed to look at my watch crash logs in more detail. When I click "show all versions" in Organizer, I'm able to get some watchOS crashes from older versions of the app showing up in Organizer - they're all for devices still running watchOS 6.3.
I filed this as FB11862196. Thank you.
Post the feedback number here once you do and I'll reference it in mine as well. (Also, might want to remove the "accepted answer" from this post since this bug hasn't been resolved.)
I submitted as FB13137561.
I believe I found a solution - if you migrate your watch app to a single target (combining the watch app with the watch extension), then invalidateConfigurationRecommendations starts working again.
To migrate, I had to bump the minimum SDK to watchOS 7, then there's an option in the recommended project settings to perform the migration. (FYI: I had a lot of issues after performing the migration, it took a few hours to get the project building again.)
I don't believe so - Apple has said that the single-target watch apps are only backwards compatible back to watchOS 7.
@simonfromhelix would you be able to share what specific steps you told users to take in order to fix this issue? Unfortunately I wasn't aware of this issue before releasing my update, and now obviously it's too late. In my testing, just switching to another complication then back again fixed the issue, but I have at least one user now who wasn't able to get things working again by doing that.
What's the FB number for your bug report? Ours is FB13100671.
Is this with watchOS 10.0.1?
Confirmed on my end as well just now.