Problem with Mobile Support

[matgarage]

Hello everyone

I have a problem with the iOS SDK integration.
I'm using Livecode 10 on Mac OS Sequoia 15.3.1 and Xcode 16.2.

When I try to set the iOS SDK by pointing to Xcode, I get an error message:

The chosen folder is not a valid iOs SDK.
Selected Xcode must have an iOS SDK among:
14.4
15.2
16.2
17.0

What can I do?
Thanks

[matgarage]

I continued my research on my own:
1 - It doesn't seem possible to install an older SDK on Xcode ( only the Device Simulator is available)
2 - The iOS SDK 17 version is available in Xcode 15, which is not compatible with Mac OS Sequoia.
3 - I find some hacks to install an unsupported version of the iOS SDK on Xcode, but the versions didn't correspond to my problem and I don't want to take any chances.

In short, I think I'm stuck.
Livecode 10 development will no longer evolve, I can only hope that the Create version and the subscription offer will be sexy enough to make me want to continue with it

[j9v6]

I'm running macOS Sequoia 15.3.1 with Xcode 16.2 and have been using LiveCode 10.0.1 (rc-3). With this combination I can build and deploy iOS apps locally (side-load) and also upload them to the AppStore using Transporter.

Interestingly yesterday Transporter starting informing me that the apps are built with a soon-to-be outdated SDK.

"SDK version issue. This app was built with the iOS 17.0 SDK. Starting April 24, 2025, all iOS and iPadOS apps must be built with the iOS 18 SDK or later, included in Xcode 16 or later, in order to be uploaded to App Store Connect or submitted for distribution. (90725)"

I don't think anythings changed with Xcode, so I'm assuming it's LiveCode using iOS 17.0 SDK when it builds?

[LCMark]

@matgarage: Update to 10.0.1-rc-3 and you will be fine - we changed the way iOS apps are built in 10.0.1 so that it no longer matters what version of Xcode / SDKs you have installed - you just need Xcode installed (as the standalone builder uses a couple of the command line tools only it contains).

@j9v6: Yes - the iOS engine is currently built against the iOS17 SDK - we'll update that to iOS18 in a release before the deadline.

[matgarage]

Thank you for these answers.
My goal is to use the test function on the device (iPhone 12 in my case) in Livecode.
I'm going to test it with the RC-3 version.
It's good news that iOS 18 integration is in the road map.

[j9v6]

@j9v6: Yes - the iOS engine is currently built against the iOS17 SDK - we'll update that to iOS18 in a release before the deadline.

Great, thank you

[trevix]

@j9v6: Yes - the iOS engine is currently built against the iOS17 SDK - we'll update that to iOS18 in a release before the deadline.

Today I tried to upload an update with transporter and I've got this message:

What should i do?

I am using OSX 14.7.4, Xcode 15.0, LC 10.0.1(RC3)
Thanks

Trevix

[scott_morrow]

Are you saying that Transporter refused to upload your app? My experience with those warnings has been that the app can still be submitted (up until the April 24 deadline). In most cases it doesn't mean that your app will stop working after the deadline, only that you will need to comply with the specified changes before it can be updated (after the deadline)... which Mark Waddingham indicates will happen.

[trevix]

You were right. I was able to use transporter to upload the standalone.
It was a longer then usual upload, for some reason, but it went well.
Thanks