Re: Invalid mac/ios standalone engine file

2021-12-31 Thread Jim At Consensus via use-livecode
Andreas/Panos, So glad you asked/answered. I’ve been putting off the Monterey update as I was afraid I wouldn’t be able to successfully build and deploy. Sounds safe to do as at least 1 person has had success. Happy New Year. ~j Sent from Jim's iPhone XR Please excuse brevity, typos and errors

Re: Invalid mac/ios standalone engine file

2021-12-31 Thread panagiotis m via use-livecode
Hello Andreas, You're welcome. RE "ITMS-90683: Missing Purpose String in Info.plist”, since it is a warning, it can be ignored for now. *Or should I always fill in the App Tracking Transparency field in the standalone settings, even if not relevant?* Nope, you should fill in this field only

Re: Invalid mac/ios standalone engine file

2021-12-31 Thread Andreas Bergendal via use-livecode
Hi Panos, I had set the minimum deployment target to 15.0 or later. Changing it to 9.0 or later solved the problem! The new standalone was successfully deployed to device, as well as submitted for review on AppStore. I got this warning feedback (on top of the traditional "ITMS-90078: Missing

Re: Invalid mac/ios standalone engine file

2021-12-31 Thread panagiotis m via use-livecode
ything works fine in the Simulator (iOS15.2), but when I try to build > the standalone for upload, I get the error message: > ”There was an error while saving the standalone application > invalid mac/ios standalone engine file” > > It still actually builds the app, but I’m afraid

Invalid mac/ios standalone engine file

2021-12-31 Thread Andreas Bergendal via use-livecode
fine in the Simulator (iOS15.2), but when I try to build the standalone for upload, I get the error message: ”There was an error while saving the standalone application invalid mac/ios standalone engine file” It still actually builds the app, but I’m afraid of uploading it to AppStore after such