Page 1 of 1

iOS Standalone Not Working

Posted: Wed May 28, 2014 10:11 pm
by Gage
Hello all!

I am currently trying to enable iOS testing, and I have been reading around, noting that it's really a headache. That said, I think I mostly have everything figured out, however, something is still not in order, and I am hoping someone can point something out in my blindspot.

I already have Development and Distribution Certificates, as well as a wildcard App ID for testing purposes.

I have a Provisioning Profile for Distribution, but do not yet have one for Development. I know I need to get the UDIDs of all devices I plan to use to create Provisioning Profiles for app development. (*This may be where my problem lies, but my test device is in the mail, so I have no way of creating the Provisioning Profile for Development, since it requires that devices' UDID*).

In any case, when I try to Save as Standalone (after tinkering with the Standalone Application Settings), I get the following error message from LiveCode.
"could not find a valid identity to use for the selected profile"

I use LiveCode Commercial 7.0.0 (dp-5) and my Apple ID Account was created in Xcode 5.1.1 .

Anyone know what I am missing? Do I simply need a device in hand to be able to create a Provisioning Profile at all, thereby enabling myself to create the Standalone without error?

I will happily provide any other necessary information that I haven't included here.

Thanks in advance!!

Phil E.

Re: iOS Standalone Not Working

Posted: Wed May 28, 2014 10:31 pm
by sefrojones
Since You're using 7.0(dp5) it could be a bug. Unless you need the bleeding edge in the app you're creating, I'd recommend trying to create your standalone in a more stable version of LiveCode.

--Sefro

Re: iOS Standalone Not Working

Posted: Wed May 28, 2014 10:37 pm
by Gage
Thanks for the reply! So, I didn't update to the version until I saw in the version description from LiveCode that it was a stable version... as in it directly stated that it is a stable version. That said, what makes you suspect it is not a stable version?

Best,
Phil E.

Re: iOS Standalone Not Working

Posted: Wed May 28, 2014 10:42 pm
by sefrojones
From the livecode site:
DP – developer preview (feature incomplete likely to be unstable)

RC – release candidate ( feature complete, likely to be quite stable but is not considered the final stable release)

GM – gold master ( feature complete stable release)

Hope this helps!

--Sefro

Edit: This was in a blog post on the livecode site. Perhaps it might be a good idea to ask RunRev if they could put these descriptions at the top of the download page to clear up any confusion.

Edit2: This is my desktop
desktop.png

Re: iOS Standalone Not Working

Posted: Wed May 28, 2014 11:08 pm
by Gage
Yes, that helps greatly! I always wondered what those initials stood for...

So, you recommend I use the most recent version of LiveCode that is a GM.

Your desktop cracks me up: camel + too many versions of LC!! Great style.

Thanks for your help!

All the best,
Phil E.

Re: iOS Standalone Not Working

Posted: Wed May 28, 2014 11:15 pm
by Gage
Feedback: unfortunately, that did not have any effect on my issue. Same problem as before. Hmm...

Anyone?

Re: iOS Standalone Not Working

Posted: Thu May 29, 2014 12:13 am
by Simon
Hi Phil,
Do you have your iOS Certificate (Production) installed?
I think you have to use that one.

If you look all the others contain "Devices" (number of UDID's) and you don't want that. But then your app is only usable once it gets into the app store. Not really much purpose to this experiment.

But yes, once you get your device and UDID then you select the provisioning profile from the standalone settings.

Simon

Re: iOS Standalone Not Working

Posted: Thu May 29, 2014 5:02 pm
by Gage
Hi Simon, thanks for your response!

I did not have a Production Certificate installed, actually. I now have one, but it was not available for selection when I created the Provisioning Profile (I used a Development Certificate instead of the Production Certificate).

As for my original problem, it did go away when I got a device, used the UDID, and created the Provisioning Profile for it.

Now, to figure out how to make AirLaunch or mergTestApp work...

Cheers!
Phil E.