Mac app code signing for beginners
iowahengst at mac.com
Sun Apr 29 11:24:08 EDT 2018
Sounds like you’re loading your apps to your iPhone and iPad via the Xcode Devices and Simulators window… apps loaded in that way will cease to work when your provisioning profile expires. As far as I know (and have experienced), that is the “normal” way it works.
However, those same apps if approved by Apple and made available in the App Store will not cease to work when the profile you used to make the app expires.
> On Apr 29, 2018, at 9:51 AM, prothero--- via use-livecode <use-livecode at lists.runrev.com> wrote:
> I write a couple of apps for myself, that run on Apple iPhone and iPad. I have to buy certificates from the Apple Developer site. They stop working after a year. However, some of the apps I get on the Apple store haven’t been updated for more than a year, yet they still work. I wonder if it has something to do with the way I provision them, as developer apps.
> Building standalone, provisioning them, etc is always a painful process for me. I think one of the problems is the infrequency that I need to do this, the ever changing way it needs to be done, and the interactions between Xcode, the Apple developer web site, and the keychain. Finding and deleting old certificates seems to be some of the problem for me. They seem to be stored in multiple places and it isn’t obvious which place is accessed by LC when building.
> Eventually I get it working, but I’m still not sure why always. It seems that there could be more docs on this, but I know it must be an enormous challenge to keep up with this. Perhaps the alerts that come from LC could be more explanative? Or maybe there are simply too many complications.
> Currently, I create the certificates and provisioning profiles on the developer site, download them to my downloads folder, double click on them and hope they get into Xcode correctly. Certificates load into the keychain. This seems to work for me. When I update from old certificates, I need to delete the old ones. Finding where these are stored (multiple places) seems to change, but eventually I find them.
> Various postings of procedures by folks here have been extremely helpful.
> So, I hope my rambling explanation of my experience with some of my challenges with getting my apps on my own devices is informative to those who might be working with the docs.
> William Prothero
>> On Apr 29, 2018, at 3:35 AM, Graham Samuel via use-livecode <use-livecode at lists.runrev.com> wrote:
>> Sorry Mark, I’ve just switched countries and I haven’t got all the info to hand, but I think the length of validation depends on the certifcate(s) one buys - you can get them for different lengths of time. From memory, mine are three-year certificates, but you can get shorter and longer ones.
>>> On 28 Apr 2018, at 15:21, Mark Smith via use-livecode <use-livecode at lists.runrev.com> wrote:
>>> graham, do your apps expire and need resigning after a year?
>>> Sent from: http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode