1

Can we somehow compile a project that has custom configuration names that are different than Debug/Release? Currently, we get module not found error if let's say we want to build a project with build configuration named Alpha etc.

11 Likes
2

Unfortunately, no. This is currently a know issue in Xcode. We're tracking this internally.

3

This is a huge issue for us as well. We can't use SPM in Xcode until this is working.

6 Likes
4

We are using custom multiple configs in our project and really need SPM to support it.

5

Seems like there is a workaround until it will be fixed:

1 Like
6

However, that particular workaround doesn't seem to work for archives with non supported configuration names. Which for me is a problem since my daily test(er) builds rely on this.

1 Like
7

It seems that it works when you put the script in Build phases before Compile sources.
Take a look at my answer xcode11 - Getting 'no such module' error when importing a Swift Package Manager dependency - Stack Overflow

1 Like
8

Thanks @nonameplum! This seems to work for me indeed.

9

You can find a fix here for this issue Swift Package Hack. Read this post if you have “No such… | by Álvaro Royo | Medium

1 Like
10

Any updates on this issue?

6 Likes
11

One year later, this is still an issue. Any progress? Is there a chance you could share the Xcode issue tracker for this?

2 Likes
13

This is still occurring @NeoNacho do you know if there is a fix for this?

14

It's a pity that there is no progress here. It's very important for my company's project.

1 Like
15

bump this!

1 Like
16

Hi @Aciid Do we have any update on this? I am getting this issue in Xcode 14.2 aswell.

17

Still an issue in Xcode 14.3.

18

Using a custom configuration name with Debug or Release prefix seems to work fine (contrary to using a fully custom name), at least in Xcode 15.1.

Configuration name examples:

  • DebugTesting (duplicated from Debug)
  • ReleaseStaging (duplicated from Release)
1 Like