Are Xcode warnings like this safe to submit (won’t disqualify)?

Question

Created 1d

Replies 5

Boosts 0

Participants 2

I’m building a Swift Playgrounds app (.swiftpm) in Xcode 26.2 and I consistently see this warning, even on brand-new Swift Playgrounds apps created from the default template:

“Skipping duplicate build file in Compile Sources build phase: /Users/.../<ProjectName>.swiftpm/Media.xcassets”

Everything builds and runs normally and all images/assets appear correctly, so it seems like it’s just an annoying warning.

I’ve checked for duplicates and don’t see the asset catalog listed twice, but the warning still appears whenever I add an asset catalog to any playground project in Xcode.

Is this warning safe to ignore for submission, and it won’t affect Swift Student Challenge eligibility?

Answered by DTS Engineer in 877507022

Oh, hey, look at that!

I had assumed that, if you set the app icon via the General tab of the playground editor, it would do the right thing. However, as soon as I switch it from Placeholder to Custom it adds the asset catalogue and I get that warning. That’s… suboptimal.

Given that, I don’t think there’s much you can do about this. You have the choice of that warning or giving up on your pretty icon, and that’s no choice.

I had a bit of a rummage and I couldn’t find any existing bug report about this warning. Given that, I encourage you to file your own. Please post your bug number, just for the record. And you can then also include the bug number in the comments when you submit.

but it looks like each attempt actually posted afterward.

Yeah, that’s a known issue with the forums platform (r. 165521402)-:

I’m not seeing an option to delete them on my end

Yep. That’s another known issue. You can learn more about it here.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

1d

Submitting your app with a warning is better than not submitting it at all. But obviously it’s better to not have warnings.

AFAIK this warning is generated by you adding an Asset Catalog (.xcassets) to your playground. What happens if you remove that?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1

Answer 2

islandrose OP

1d

@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! :)

0

Answer 3

islandrose OP

1d

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

0

Answer 4

DTS Engineer OP

Apple

10h

Recommended

Oh, hey, look at that!

I had assumed that, if you set the app icon via the General tab of the playground editor, it would do the right thing. However, as soon as I switch it from Placeholder to Custom it adds the asset catalogue and I get that warning. That’s… suboptimal.

Given that, I don’t think there’s much you can do about this. You have the choice of that warning or giving up on your pretty icon, and that’s no choice.

I had a bit of a rummage and I couldn’t find any existing bug report about this warning. Given that, I encourage you to file your own. Please post your bug number, just for the record. And you can then also include the bug number in the comments when you submit.

but it looks like each attempt actually posted afterward.

Yeah, that’s a known issue with the forums platform (r. 165521402)-:

I’m not seeing an option to delete them on my end

Yep. That’s another known issue. You can learn more about it here.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1

Answer 5

islandrose OP

9h

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

0