iOS Provisioning Profiles - Dev vs. Production

Gerry Orkin gerry.orkin at
Tue May 6 17:15:35 EDT 2014


Is this the first release of the app? I had a situation where updates to an existing version were fine but new installs hung for users. Turned out that I'd introduced a bug that only  affected users who didn't already have one of the files I copy from the binary to the device when the app is first launched. 

It must have passed Apple's testing because they tested it on the same device or simulator they'd used for the previous version. 


> On 7 May 2014, at 3:13 am, Dan Friedman <dan at> wrote:
> Greetings!
> If I build my iOS app with the Development Provisioning Profile, and install it on my phone, and it runs perfectly without error, is there any reason to believe or think that building the EXACT same app with the Production Provisioning Profile would have any type of problem when it's posted to the App Store by Apple?
> This is exactly what I did.  But when downloaded from the App Store, the app crashes.  Not just for me, but for everyone that installs the app.  How could the app have passed the App Review process but crash on EVERY install on EVERY device when downloaded from the App Store?
> I keep thinking that it might be the version of LC (6.6.1) or XCode (5.1.1) I am using... but wouldn't the development version fail as well?  Regardless of that, how could it pass App Review if the app crashes on launch?
> I have contacted Apple Developer Technical Support (using one of my 2 allotted support incidences), but they are just giving me the runaround.  All I get from them are form responses.  Check this, check that... all checks out.  They don't seem to want to examine the specifics of my case.   Some of what they want me to do I can't because the app was not compiled in XCode.
> If it helps, here is the relevant parts of a crash report:
> Exception Type:  EXC_CRASH (SIGABRT)
> Exception Codes: 0x00000000, 0x00000000
> Crashed Thread:  5
> Thread 5 Crashed:
> 0   libsystem_kernel.dylib            0x3197232c __pthread_kill + 8
> 1   libsystem_c.dylib                 0x3406f208 pthread_kill + 48
> 2   libsystem_c.dylib                 0x34068298 abort + 88
> 3   myApp                             0x001df580 0xad000 + 1254784
> 4   myApp                             0x0017ee4e 0xad000 + 859726
> 5   myApp                             0x0017ed20 0xad000 + 859424
> 6   libsystem_c.dylib                 0x3403072e _pthread_start + 314
> 7   libsystem_c.dylib                 0x340305e8 thread_start + 0
> Anyone have any words of wisdom on this?  Client is already at their wits end!
> -Dan
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list