@swift-ci create

Comment by Patrick Beard (JIRA)

I experienced this bug the other day and solved it a different way. I was trying to add individual .png files to my executable target, using:

resources: [.copy("foo.png"), .copy("bar.png")]

When building with SPM, the Bundle.module accessor would get generated, but loading the Package.swift into Xcode 13, the accessor would not get generated. I fixed it by moving all of the image files into a subdirectory called "Resources" and switching to this form:

resources: [.process("Resources")])

Same problem (Xcode 13A1030d, default toolchain), except none of the suggested solutions worked (didn't try xcodeproj, though). Luckily, the generated file resource_bundle_accessor.swift is accessible, I copied the whole thing into a (hopefully) tmp file and renamed module into _module.

FYI I have not a .target, but rather an .executableTarget in my Package.swift and this problem manifests only in Xcode, running swift run from terminal works perfectly.

UPD: this solution didn't work in Linux (Docker, image 5.5), however, doing nothing (just use Bundle.module without anything) worked. I find myself mildly frustrated.

Comment by Nicole Stone (JIRA)

Running into this same issue on Xcode 13.2.1. Calling `swift package generate-xcodeproj` did not fix the issue for me. But doing what @kirilltitov describes by just copying the generated file into a temp file did work for me.