compiler setting. It is more of a runtime
>> thing. So if you set the deployment target to 13.0 it will not launch on
>> macOS 12, for
>
> Oh, I see. That explains a lot.
>
>> example. The SDK is what determines what API are (not) available. So if you
>> were buildi
Isn’t it as simple as setting the minimum build version to 10.12?
> On Mar 18, 2022, at 9:47 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> I am trying to build my app for macOS 10.12 (Sierra).
>
> First of all, is it correct that I need to build it for "My Mac" , not do a
> niversal build
nch on
> macOS 12, for
Oh, I see. That explains a lot.
> example. The SDK is what determines what API are (not) available. So if you
> were building against the 10.12 SDK you would have gotten a compiler error.
Sorry for asking (again?): how would I do that?
How do I install old SDK's on
> On Mar 20, 2022, at 11:41 AM, Quincey Morris
> wrote:
>
> (Resending because I forgot to cc the list)
>
> On Mar 20, 2022, at 08:09, Gabriel Zachmann via Cocoa-dev
> wrote:
>>
>> Apparently, this caused it:
>>
>> Symbol not found: _AVAudioSessionInterruptionNotification
>>
>> Yes, I am
(Resending because I forgot to cc the list)
On Mar 20, 2022, at 08:09, Gabriel Zachmann via Cocoa-dev
mailto:cocoa-dev@lists.apple.com>> wrote:
>
> Apparently, this caused it:
>
> Symbol not found: _AVAudioSessionInterruptionNotification
>
> Yes, I am using that function, and yes, it seems to
ll not launch on macOS
12, for example. The SDK is what determines what API are (not) available. So
if you were building against the 10.12 SDK you would have gotten a compiler
error.
> How can I prevent things like that happening in the future?
Use the correct SDK for the OS builds y
I have now the crash report.
Apparently, this caused it:
Symbol not found: _AVAudioSessionInterruptionNotification
Yes, I am using that function, and yes, it seems to be available only on macOS
11 and higher.
My question now is: why did Xcode not warn me about that function, even though
On 3/18/22 1:03 PM, Gabriel Zachmann via Cocoa-dev wrote:
Make sure you have the 10.12 SDK installed in your Xcode. To find out
what
Actually, it seems I wouldn't need older SDK's any more, see, for instance:
https://developer.apple.com/forums/thread/82518
And some people even
>>> Make sure you have the 10.12 SDK installed in your Xcode. To find out
>>> what
Actually, it seems I wouldn't need older SDK's any more, see, for instance:
https://developer.apple.com/forums/thread/82518
And some people even say it could be harmful to have multiple SDK's with Xcode
> On Mar 18, 2022, at 1:11 PM, Gabriel Zachmann wrote:
>
>>> I am trying to build my app for macOS 10.12 (Sierra).
>>>
>>> First of all, is it correct that I need to build it for "My Mac" , not do a
>>> niversal build (Any Mac)?
>> If you are only building to debug it then My Mac is
>> I am trying to build my app for macOS 10.12 (Sierra).
>>
>> First of all, is it correct that I need to build it for "My Mac" , not do a
>> niversal build (Any Mac)?
> If you are only building to debug it then My Mac is fine. But if you
> are building to send out to customers then you
> On Mar 18, 2022, at 8:47 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> I am trying to build my app for macOS 10.12 (Sierra).
>
> First of all, is it correct that I need to build it for "My Mac" , not do a
> niversal build (Any Mac)?
If you are only building to debug it then My
I am trying to build my app for macOS 10.12 (Sierra).
First of all, is it correct that I need to build it for "My Mac" , not do a
niversal build (Any Mac)?
Second, I have been switching the scheme to build for "My Mac", but when I
archive it to notarize it and export it, I still get a
PS:
I have, of course, switched the Deployment Target to 10.12,
but I am working on macOS 12.1 and Xcode 13.3.
(Sorry for not mentioning earlier)
smime.p7s
Description: S/MIME cryptographic signature
___
Cocoa-dev mailing list
14 matches
Mail list logo
