@DTS Engineer Thanks for testing and confirming. :) This warning has been bugging me, so it’s helpful to know it’s a tooling issue. I just filed a bug report and the number is FB22064091. I’ll submit with the warning, and I’ll include the feedback number in my submission comments. I mainly wanted to make sure it won’t interfere with submission. Thanks again, this really eased my stress.

@DTS Engineer Sorry about the duplicate replies. The forum kept showing “Your post couldn’t be saved,” but it looks like each attempt actually posted afterward. I’m not seeing an option to delete them on my end, so please ignore it. :)

@DTS Engineer I’d prefer to submit without warnings if there’s a recommended fix. I’m using an asset catalog for bundled images and the app icon. Removing the asset catalog makes the warning go away, but is there a way to include a .xcassets asset catalog in a Swift Playgrounds app without triggering the duplicate build file warning? If the recommended solution is to avoid .xcassets and use SwiftPM resources instead, what’s the easiest way to handle the app icon in that setup? Thanks! :)