Re: iOS deployment question

Ben: This sounds reasonable. Then I don’t have to translate the terms from Xcode terminology to Livecode terminology. Best, Bill > On Mar 29, 2016, at 1:31 AM, Ben Rubinstein wrote: > > FWIW, this really isn't a LiveCode issue. Back when we were doing a lot of > iOS app

Re: iOS deployment question

On Mar 29, 2016, at 8:26 AM, Dave Kilroy wrote: > > Glad you got things sorted William > > For those who find they are accumulating more and more old copies of > provisioning profiles on their local drive (which can lead to error > messages) and can't find a way of

Re: iOS deployment question

Glad you got things sorted William For those who find they are accumulating more and more old copies of provisioning profiles on their local drive (which can lead to error messages) and can't find a way of deleting them - they are located here: "/Users//Library/MobileDevice/Provisioning

Re: iOS deployment question

FWIW, this really isn't a LiveCode issue. Back when we were doing a lot of iOS app development, submission - which should have been a matter of pressing a few buttons - invariably took many hours of hair tearing - and this in spite of the fact that we were making new submissions virtually

Re: iOS deployment question

Scott: Yes, I’ve experienced this. I do think there could be some kind of “advice” document, blog, or something that puts some of the Apple jargon into livecode understandable terms, though. From the XCode error message, I thought the problem was the certificate (wild goose chase) but it was

Re: iOS deployment question

Maybe this Chrome extension below is usefull when dealing with provisioning files. App IDs are "the herpes of iPhone provisioning". Once you've created one, you're ... http://simonwhitaker.github.io/app-id-sanity/ Cheers, Erik On Wednesday, 23 March 2016, Scott Rossi

Re: iOS deployment question

Speaking as someone who took a stab at this (http://tactilemedia.com/download/How_to_publish_on_iOS_83013.pdf), it's a major amount of work that almost needs to be a part time job. Not only does Apple change details of the process and add features to the system, but it updates/rearranges the

Re: iOS deployment question

Last post on this subject: I also got it working by changing my provisioning profile to include both iPad and iPhone. Previously I had only checked the iPhone option. But, I guess I must have entered a device description for my iPad too. H… what an obtuse system. Bill > On Mar 23, 2016, at

Re: iOS deployment question

Last post on this subject: I also got it working by changing my provisioning profile to include both iPad and iPhone. Previously I had only checked the iPhone option. But, I guess I must have entered a device description for my iPad too. H… what an obtuse system. Bill > On Mar 23, 2016, at

Re: iOS deployment question

Folks: Ok, what I got working was a profile that was named “iOS Team Provisioning Profile”. There was a wildcard version, and a version with my app ID attached. Both worked. The specific profiles I created for the app itself gave the error. Since this is an app that I will only use myself, on

Re: iOS deployment question

This might be a naming issue. In standalone settings, make sure that the last item in the entry for Internal App ID matches the app name you set up in your provisioning profile in Apple's developer portal. The Internal App ID should look like this: com.. is the part that needs to match

Re: iOS deployment question

Panos: Thanks for the idea. Nope, beta version isn’t checked. I’m using a Development profile. Todd: Yes, there is a major need for more information and help getting mobile apps through the process. It’s really ugly for newbies. It’s made even more difficult because Apple keeps making changes

Re: iOS deployment question

Folks: I’m stuck. I keep getting the error message: "The entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your provisioning profile. (0xE8008016)." Folks: So: Is this a problem with the certificate, or with the options I select on the

Re: iOS deployment question

Hi Bill, Just a thought: Could it be the case that you have checked the "Beta version" checkbox in the standalone application settings for iOS, but you sign the app using a Development profile? I think the "Beta version" checkbox has to be used *only* with a Distribution profile. Regards, Panos

Re: iOS deployment question

Hello Bill, Please please if you have any info on the steps of how to submit to the OSX Store. We are facing the same problems. I can find almost ZERO info on what needs to be done to submit the app. Thanks, Todd > On Mar 22, 2016, at 7:29 PM, William Prothero earthednet.org> > wrote: > >

Re: iOS deployment question

I’m wondering if there is a way to smooth out this error for the user. When I try to load my app onto my iPhone for testing, I get the following message from XCode: T"he entitlements specified in your application’s Code Signing Entitlements file do not match those specified in your

Re: iOS deployment question

Graham, I can take some notes. What I did to fix it was to delete all my developer certificates from my keychain and re-activate them. That was after I realized that the reference to "identity" actually meant that it couldn't find a valid certificate. Now it seems obvious, but didn't at first.

Re: iOS deployment question

Care to write it up, William? AFAICS, coding in LiveCode is a trouble-free activity compared to deployment on iOS (or indeed on LiveCode Server, Android etc). Arcane rules, certificates, permissions… even the vocabulary seems to have been re-invented to confuse the honest programmer. Of

Re: iOS deployment question

Never mind…… Got it to work. Bill > On Mar 22, 2016, at 8:17 PM, William Prothero wrote: > > I can see, after Googling around a bit, that getting the certificates signed > and set up correctly is quite complicated, with lots of ways of going wrong. > With out-dated

Re: iOS deployment question

I can see, after Googling around a bit, that getting the certificates signed and set up correctly is quite complicated, with lots of ways of going wrong. With out-dated certificates, old provisioning profiles, etc. I wonder if there is a way to make this more robust and transparent. Like some