Sad truth about iOS apps
Erik Beugelaar
e.beugelaar at me.com
Sat May 16 04:38:16 EDT 2020
First you can upgrade your 'old' MacBook Pro (before mid 2012), in your case High Sierra, to Mojave with macOS Mojave Patcher Tool. See http://dosdude1.com/software.html
Then you upgrade to Catalina with the macOS Catalina Patcher and you will be up to date.
Detailed instruction are on the website. You only loose the support of the extra gpu card in your MacBook Pro but if you are not playing games or other heavy graphical stuff you will not notice any difference.
Erik
-----Original Message-----
From: use-livecode <use-livecode-bounces at lists.runrev.com> On Behalf Of Graham Samuel via use-livecode
Sent: vrijdag 15 mei 2020 23:34
To: How to use LiveCode <use-livecode at lists.runrev.com>
Cc: Graham Samuel <livfoss at mac.com>
Subject: Re: Sad truth about iOS apps
Very sincere thanks to all who replied - I will explore all your solutions and insights.
If I get that far (to make an acceptable version of my app bundle) I will also have to solve a number of errors that the Loader reported. For instance:
> The Key UIUUserInterfaceStyle … in the Payload/Myapp.appinfo.plist is invalid
Difficult, as I don’t know what that means.
I can cope with the requirement for different PNG files of certain precise sizes not mentioned in the LC Standalone Settings, e.g.
> The bundle does not contain an app icon for iPad of exactly '76x76' pixels, in .png format for iOS versions >= 7.0. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file.
but the references to where they should be placed mean nothing to me. Here’s another one:
> ERROR ITMS-90023: "Missing required icon file. The bundle does not contain an app icon for iPad of exactly '152x152' pixels, in .png format for iOS versions >= 7.0. To support older operating systems, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file.
I had hoped that LC would look after the positioning of all this stuff for me - I believe I supplied all the PNGs that the LC Settings asked for, but of course I will check.
The Xcode documentation of course assumes that one’s app is a project within the XCode universe,which AFAIK doesn’t apply to LC projects, so it’s not much help, at least not to me.
Is there a way out of this confusion?
Graham
> On 15 May 2020, at 18:02, I wrote:
> As many of you will know, I have been struggling to create an iPhone app - very unfamiliar territory for me. It’s been an education. Without help from this list and the mother ship I would have been dead in the water long ago. Finally I can see the (beta version of) the app running on my iPhones - yipee! The next step is to get it out there via TestFlight so that a few friends can mess with it.
>
> I just went through all the hoops with the Apple App Store to reach the magic TestFlight stage, using the XCode Application Loader. Things looked good until this:
>
>> ERROR ITMS-90725: "SDK Version Issue. This app was built with the iOS 12.1 SDK. New apps for iPhone or iPad must be built with the iOS 13 SDK or later.”
>
> My iMac can only run High Sierra, and High Sierra can only run XCode 10.1, and AFAIK that version of XCode only runs SDK 12.1. I think that means I get a new Mac or give up.
>
> Please tell me if I’m wrong.
>
> Graham
>
> PS I would really like a new Mac, but the budget is the problem!
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
More information about the use-livecode
mailing list