After adding provisional profiles with theis entitlements in AppWrapper for an app to be delivered to the Apple Store, double-clicking on the app created by AppWrapper, or installing the pakage on my machine I get this message: The app appName cannot be opened.
In order for the app to open, I have to remove from AppWrapper the provisional profiles’ entitlements. So I have a question: is it normal for such an app not to open on my own machine?
In fact, although testing the pakage in Transport I do not get any warning, I still am in doubt whether to deliver it, fearing the Apple Store reviewer (and users) may not be able to open it.
BTW: the only one reason I started adding provisional profiles, was to get rid of the warning issued by Transporter (the app cannot be used for test-flight etc.). In fact, I do not intend for my desktop apps to be tested in test-flight. So the question: is it worthy for me to go through all this maneuvering when I cannot anymore use such app even on my own machine?
The only reason to add a provisioning profile is if you’re actually going to be distributing the app through the App Store. Entitlements are added to the app as part of the code-signing process and the app must be notarized in either case as well.
I do indeed. But I’d be glad to know if such app, when ready to be delivered, can or cannot be opened on my own machine, since at present I get the “The application “myappName” cannot be opened” message. I wanted just to be sure that such warning was not due to my negligence. Thanks.
IIRC, I believe it has to go through the App Store and downloaded to your computer just like anyone else would. That’s why TestFlight is so handy, even if it’s just for yourself.
You are doing the whole digital receipt thing correct?