Which apps are affected, out of curiosity?

Well that's encouraging at least! @JacobJohnston how long ago did you release the App Store build - long enough that you would have heard something by now if someone was affected?

Yes, it started with the TestFlight build I submitted on May 8th. The previous build I submitted on April 17th worked fine. As far as I (and git) can tell, I didn't make any project changes that would have affected this, and didn't change Xcode versions or anything like that.

I’m assuming you’re using automatically-managed provisioning profiles. Have you tried turning that off then back on yet? I’m unable to reproduce this on any of my devices so it’s making it much harder for me to see if I’ve found a fix.

We did see those Watch AppConduit lines, but no iPhone AppConduit or app database out of sync lines.

Confirmed on my end as well just now.

Is this with watchOS 10.0.1?

What's the FB number for your bug report? Ours is FB13100671.

@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.

I don't believe so - Apple has said that the single-target watch apps are only backwards compatible back to watchOS 7.

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 submitted as FB13137561.

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.)

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.

I added the NSHTTPURLResponse to my earlier feedback in case that's helpful (FB11577100).