Mysterious build warning with .xib file


Graham Cox
 

Can anyone explain this? I’m getting the following warning in my build:


But when I look at the file info for that .xib file:


And the deployment target in the target as a whole:


Am I missing something? I’m building for 10.11 at the earliest, and that seems to be what is set throughout. So why the “Unsupported configuration”?


—Graham



Carl Hoefs
 

That has happened to me when I've forgotten to change the OS targets for (1) all the xibs and (2) the project itself. But it sounds like you've got all that covered...

-Carl


On Nov 5, 2019, at 5:03 PM, Graham Cox <graham@...> wrote:

Can anyone explain this? I’m getting the following warning in my build:

<Screen Shot 2019-11-06 at 10.58.27 am.png>

But when I look at the file info for that .xib file:

<Screen Shot 2019-11-06 at 10.58.12 am.png>

And the deployment target in the target as a whole:

<Screen Shot 2019-11-06 at 10.58.54 am.png>

Am I missing something? I’m building for 10.11 at the earliest, and that seems to be what is set throughout. So why the “Unsupported configuration”?


—Graham




Quincey Morris
 

On Nov 5, 2019, at 16:03 , Graham Cox <graham@...> wrote:

Am I missing something? I’m building for 10.11 at the earliest, and that seems to be what is set throughout. So why the “Unsupported configuration”?

I see similar results. It looks like a bug.

If I set “Builds for” to “Deployment Target”, it shows the wrong deployment target (10.13 instead of 10.11), or if I choose a popup setting later than 10.13 there’s no error. It’s not clear whether it’s actually using 10.13, or using 10.11 and lying about it. Note that the build log shows “--minimum-deployment-target 10.11”.



Graham Cox
 

Hmmm, oh well, I guess I’ll just live with it. Bigger fish to fry and all that.

Thanks!

—Graham



On 6 Nov 2019, at 1:05 pm, Quincey Morris <quinceymorris@...> wrote:

On Nov 5, 2019, at 16:03 , Graham Cox <graham@...> wrote:

Am I missing something? I’m building for 10.11 at the earliest, and that seems to be what is set throughout. So why the “Unsupported configuration”?

I see similar results. It looks like a bug.

If I set “Builds for” to “Deployment Target”, it shows the wrong deployment target (10.13 instead of 10.11), or if I choose a popup setting later than 10.13 there’s no error. It’s not clear whether it’s actually using 10.13, or using 10.11 and lying about it. Note that the build log shows “--minimum-deployment-target 10.11”.


Quincey Morris
 

On Nov 5, 2019, at 20:30 , Graham Cox <graham@...> wrote:

Hmmm, oh well, I guess I’ll just live with it. Bigger fish to fry and all that.

I played with this a bit more. It turns out that the bug is “transient”, in the sense that if you quit Xcode and relaunch, it picks up the correct deployment target.