I'm encountering the same warning. Xcode Version 16.1 (16B40) - RC. My project settings are Swift 6 and SWIFT_STRICT_CONCURRENCY=Complete or Targeted. The only configuration that seems to avoid this warning is SWIFT_STRICT_CONCURRENCY=Minimal.

Anyone have any luck on this? I believe I'm seeing the same issue on iOS 18.0 (release) using both Xcode 16.0 and Xcode 16.1beta3.

Thanks @DTS Engineer for your reply. Unfortunately doing it that way results in no smooth animation -- the expansion simply "pops" rather than smoothly expanding. Also in my actual app, I have other animations I'm trying to trigger (e.g. fadein/out effects depending on the expansion state) that I believe this would negate? I suppose I could have a separate state for that. But it still allow the list row to smoothly expand/collapse like the default DisclosureGroupStyle. Is there no way to achieve behavior that is similar to the default? I'd consider a VStack, but then I lose the ability handle move/delete operations easily.

I'm experiencing this as well. Aug 8, 2024 For reference, seen on simulator running iOS 18.0 beta with Xcode 16 beta 4. Curiously ProductView(id:) works fine.

Xcode 15.4 now says "The selected package cannot be a direct ancestor of the project.". Seems like this is intentional. But personally this feels like a huge oversight as this is kind of a necessary workflow when working on and testing libraries.

You may also need to add the Hardened Runtime: Apple Events capability

This has been a major deficiency in many source document tools I've used. It'd be great if DocC can fill the gap!

For anyone else finding this question, there's also the swift package purge-clean and swift package reset commands.

I ran into the same error after updating to Xcode 13.3, however I never haver had a relevant "Document Types" or "Exported Type Identifiers" for my UIDocument. I found I was able to get around the problem by overriding "fileType" and "savingFileType". I'm not sure what is making use of these values as the document filename appears to be the same.

I know this doesn't directly solve your problem, the phone case you are using can also severely impact heat dissipation from the phone. Just something to keep in mind.

Thanks for this info. Even 5 years later, it was helpful! It would be nice if the documentation for supportedInterfaceOrientations and related methods included this info.