Re: Invalid mac/ios standalone engine file
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 > On Dec 31, 2021, at 8:25 AM, panagiotis m via use-livecode > wrote: > > 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 if your app tracks user activity > among other apps/websites. > > Have a happy new year :) > > Cheers, > Panos > -- > > > > >> On Fri, 31 Dec 2021 at 18:11, Andreas Bergendal via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >> 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 Push Notification Entitlement”): >> "ITMS-90683: Missing Purpose String in Info.plist” >> >> As the app does not "access sensitive user data” I hope that warning too >> can safely be ignored. >> Or should I always fill in the App Tracking Transparency field in the >> standalone settings, even if not relevant? >> >> Anyway, many thanks for you swift and helpful reply Panos - I wish an >> especially Happy New Year to you! >> >> /Andreas >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode >> > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Invalid mac/ios standalone engine file
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 if your app tracks user activity among other apps/websites. Have a happy new year :) Cheers, Panos -- On Fri, 31 Dec 2021 at 18:11, Andreas Bergendal via use-livecode < use-livecode@lists.runrev.com> wrote: > 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 Push Notification Entitlement”): > "ITMS-90683: Missing Purpose String in Info.plist” > > As the app does not "access sensitive user data” I hope that warning too > can safely be ignored. > Or should I always fill in the App Tracking Transparency field in the > standalone settings, even if not relevant? > > Anyway, many thanks for you swift and helpful reply Panos - I wish an > especially Happy New Year to you! > > /Andreas > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Invalid mac/ios standalone engine file
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 Push Notification Entitlement”): "ITMS-90683: Missing Purpose String in Info.plist” As the app does not "access sensitive user data” I hope that warning too can safely be ignored. Or should I always fill in the App Tracking Transparency field in the standalone settings, even if not relevant? Anyway, many thanks for you swift and helpful reply Panos - I wish an especially Happy New Year to you! /Andreas ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Invalid mac/ios standalone engine file
Hello Andreas, What is the minimum deployment target in the iOS standalone settings? I suggest setting it to "9.0 or later". Kind regards, Panos -- On Fri, 31 Dec 2021 at 16:03, Andreas Bergendal via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi all, > > So, following the release of LC 9.6.6 rc1, I took the plunge and upgraded > my Mac to Monterey (12.1) and Xcode to 13.2.1. > > I now want to build an iOS15 version of my app and upload to AppStore, to > prevent the crashing that has occurred for users with the iOS14 version. > > Everything 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 of uploading it to > AppStore after such an error message. > > I have so far done the following: > - Using macOS Monterey 12.1 > - Using Xcode 13.2.1 > - Selected Xcode 13.2.1 in the Command Line Tools section in Xcode > - Reinstalled the Command Line Tools just in case (following hint in the > Forum) > - Using LiveCode 9.6.6 rc1 (Pro) > - Selected the correct path in LC to Xcode 13.2.1, green-lighted > - Turned the Mac off, and on again... > > With a development provisioning profile everything works fine when > deploying to the Simulator. > With a development provisioning profile the error message appears and it > doesn’t deploy to my physical device (iPhone X, iOS 15.2). > With a distribution provisioning profile the error message appears when > building a standalone. > > All certificates and provisioning profiles are valid. > > Why, oh why, does it not work? > > Hoping for a solution before the New Year! :) > Wishing you all a Happy New Coding Year 2022! > /Andreas > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Invalid mac/ios standalone engine file
Hi all, So, following the release of LC 9.6.6 rc1, I took the plunge and upgraded my Mac to Monterey (12.1) and Xcode to 13.2.1. I now want to build an iOS15 version of my app and upload to AppStore, to prevent the crashing that has occurred for users with the iOS14 version. Everything 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 of uploading it to AppStore after such an error message. I have so far done the following: - Using macOS Monterey 12.1 - Using Xcode 13.2.1 - Selected Xcode 13.2.1 in the Command Line Tools section in Xcode - Reinstalled the Command Line Tools just in case (following hint in the Forum) - Using LiveCode 9.6.6 rc1 (Pro) - Selected the correct path in LC to Xcode 13.2.1, green-lighted - Turned the Mac off, and on again... With a development provisioning profile everything works fine when deploying to the Simulator. With a development provisioning profile the error message appears and it doesn’t deploy to my physical device (iPhone X, iOS 15.2). With a distribution provisioning profile the error message appears when building a standalone. All certificates and provisioning profiles are valid. Why, oh why, does it not work? Hoping for a solution before the New Year! :) Wishing you all a Happy New Coding Year 2022! /Andreas ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
