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 <benr...@cogapp.com> wrote: > > 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 every week; > solving the problems one week didn't stop us having another load of problems > the next week. > > When doing development (as opposed to submission) my practise now when I get > a problem in LiveCode is to spend almost no time trying to fix it in LC; > instead jump immediately to a dummy app on Xcode, and make sure I can deploy > that first; mostly I find the same problem there, so can debug it with one > less step in the chain, and when I have that working, go back to LC. > > And yes, I long for a hand-holding guide, but I think the problems keep > changing. > > My 2p > > Ben > > On 23/03/2016 22:14, William Prothero wrote: >> 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. Hmmmm… what >> an obtuse system. >> Bill >>> On Mar 23, 2016, at 2:23 PM, William Prothero <waproth...@gmail.com> wrote: >>> >>> 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 >>> IDattached. 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 my iPhone, that’s good >>> enough. >>> >>> I’ll go back and carefully check your suggestions, though Scott. At >>> present, I need some lunch. Been staring at the screen too long. >>> >>> Best, >>> Bill >>> >>>> On Mar 23, 2016, at 2:09 PM, Scott Rossi <sc...@tactilemedia.com> wrote: >>>> >>>> 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.<yourdomain>.<yourappid> >>>> >>>> <yourappid> is the part that needs to match whatever you set up in the >>>> portal. >>>> >>>> Also make sure that you have the correct item selected in the Profile >>>> pulldown. >>>> >>>> Regards, >>>> >>>> Scott Rossi >>>> Creative Director >>>> Tactile Media, UX/UI Design >>>> >>>> >>>> >>>> >>>> On 3/23/16, 1:54 PM, "use-livecode on behalf of William Prothero" >>>> <use-livecode-boun...@lists.runrev.com on behalf of >>>> proth...@earthednet.org> wrote: >>>> >>>>> 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 iOS settings in Livecode? >>>>> It sounds like it is complaining about the code signing certificate. I >>>>> have checked, downloaded, tried, to no avail. >>>>> >>>>> Iąm stuck. Any comments or direction would be MUCH appreciated. One >>>>> problem for me is the jargon that Apple uses doesnąt match up well with >>>>> the Livecode jargon, so itąs very difficult to tell where to go to figure >>>>> out whatąs going on. Not to mention that the Apple documentation doesnąt >>>>> always match up with xcode screen. >>>>> >>>>> Bill >>>>> >>>>>> On Mar 23, 2016, at 12:44 PM, William Prothero >>>>>> <proth...@earthednet.org> wrote: >>>>>> >>>>>> 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 provisioning >>>>>> profile. (0xE8008016).˛ >>>>>> >>>>>> Iąm wondering if there is a way for Livecode to provide more diagnostic >>>>>> information about the validity of the provisioning profile. The message >>>>>> above from XCode doesnąt give much help. >>>>>> >>>>>> Best, >>>>>> Bill >>>>>> >>>>>>> On Mar 23, 2016, at 7:35 AM, Earthednet-wp <proth...@earthednet.org> >>>>>>> wrote: >>>>>>> >>>>>>> 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. I remember some postings a while back re the need to get a >>>>>>> new certificate. In the process, I mucked up my entire keychain and had >>>>>>> to recover it using the wonderful "Time Machine". >>>>>>> >>>>>>> Now I'm fiddling with the provisioning profile to make its setup match >>>>>>> with the standalone settings for iOS. One thing I see as I fiddle, is >>>>>>> multiple provisioning profile in the drop down menu on iOS settings. >>>>>>> Each new change and download on the Apple dev site creates a new one >>>>>>> and the name doesn't change unless I do in in the apple developer >>>>>>> website. Haven't figured out a way to delete old ones yet, but that >>>>>>> will come. >>>>>>> >>>>>>> I'm just giving these details of my thought so that if somebody >>>>>>> decides to write up this, with all it's messiness, they might see what >>>>>>> newbies go thru. I'm not a newby anymore, but I only work with iOS >>>>>>> occasionally and the process seems to always be painful. >>>>>>> >>>>>>> I'll take some notes and if they seem relevant, I'll post them >>>>>>> somewhere. >>>>>>> >>>>>>> Best, >>>>>>> Bill >>>>>>> >>>>>>> William Prothero >>>>>>> http://es.earthednet.org >>>>>>> >>>>>>>> On Mar 23, 2016, at 2:46 AM, Graham Samuel <livf...@mac.com> wrote: >>>>>>>> >>>>>>>> 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 course, thatąs >>>>>>>> just my view, and I am not young. Still, it seems to me that one of >>>>>>>> the biggest challenges for LiveCode is to make the whole process, from >>>>>>>> having the idea for the app all the way to successfully publishing it, >>>>>>>> a journey with no u-turns, dead ends, or deep frustration at lack of >>>>>>>> progress. >>>>>>>> >>>>>>>> Just my two eurocents >>>>>>>> >>>>>>>> Graham >>>>>>>> >>>>>>>>> On 23 Mar 2016, at 04:34, William Prothero <proth...@earthednet.org> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Never mindŠŠ Got it to work. >>>>>>>>> Bill >>>>>>>>> >>>>>>>>>> On Mar 22, 2016, at 8:17 PM, William Prothero >>>>>>>>>> <proth...@earthednet.org> 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 certificates, old >>>>>>>>>> provisioning profiles, etc. >>>>>>>>>> >>>>>>>>>> I wonder if there is a way to make this more robust and >>>>>>>>>> transparent. Like some app that will go through the settings, >>>>>>>>>> certificates, and provisioning profiles and give a diagnostic. Or >>>>>>>>>> perhaps, could the Livecode diagnostics give more information to >>>>>>>>>> help figure out whatąs going wrong? This seems like a real need to >>>>>>>>>> me. >>>>>>>>>> >>>>>>>>>> Maybe itąs too much to hope for. It takes me a day or two of >>>>>>>>>> hair-pulling to get this set up after being away from making iOS >>>>>>>>>> apps for awhile. >>>>>>>>>> >>>>>>>>>> Best, >>>>>>>>>> Bill >>>>>>>>>> >>>>>>>>>>> On Mar 22, 2016, at 7:29 PM, William Prothero >>>>>>>>>>> <proth...@earthednet.org> wrote: >>>>>>>>>>> >>>>>>>>>>> Iąm getting an error when I try to build an iOS standalone. It is: >>>>>>>>>>> łCould not find a valid identity to use with the selected iOS >>>>>>>>>>> profile.˛ >>>>>>>>>>> >>>>>>>>>>> Where should I look? Iąve downloaded a certificate and set the >>>>>>>>>>> bundle of the provisioning profile to >>>>>>>>>>> org.earthednet.wWaterDetective, and it shows up in the Profile >>>>>>>>>>> setting, and I set the internal App ID to >>>>>>>>>>> org.earthednet.wWaterDetective. >>>>>>>>>>> >>>>>>>>>>> Iąm in LC 8 DP 16, using Xcode 6.2.1. >>>>>>>>>>> >>>>>>>>>>> Very frustrating. It would be really wonderful if, sometime, there >>>>>>>>>>> was a list of possible complaints the standalone builder would >>>>>>>>>>> make, with possible solutions, or at least some diagnostic things >>>>>>>>>>> one could do. >>>>>>>>>>> >>>>>>>>>>> Any suggestions would be much appreciated. >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> Bill >>>>>>>>>>> >>>>>>>>>>> William Prothero, Ph.D. >>>>>>>>>>> University of California, Santa Barbara, Emeritus >>>>>>>>>>> proth...@earthednet.org > > > _______________________________________________ > 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
