LiveCode Forums.

Thanks Randy!

That really helped me get a long way with it. yet another step has appeared that has me baffled yet again.

I have added myself as an internal tester, and a family member as an external tester. when i view the prerelease section i am presented with two messages. the first stating "To use TestFlight Beta Testing, build 1.5.4 must contain the correct beta entitlement. For more information, see the FAQ." going to the FAQ's provides the following details:

"What should I do if my prerelease build does not contain the correct beta entitlement?
To use the TestFlight app to test your prerelease build, it must be signed with an App Store Distribution Provisioning profile that includes the beta entitlement. New Distribution Provisioning profiles generated in the iOS Developer Center will automatically contain the beta entitlement.

If you have an existing Distribution Provisioning Profile that was generated before the launch of TestFlight Beta Testing, you must regenerate the profile."

As i've made this profile today, I am under the assumption that my provisioning profile is ok on in this regard.

The second prompts me to turn on TestFlight in order to begin testing. I flip the switch, and it turns green. Next, i'm asked to add a tester to begin.

I click to make sure that both the internal, and external testers are present (and they are), but a new message appears on the internal tester page prompting me to turn on TestFlight to begin testing. I jump back over to the build tab, and see that the switch has turned off, and i'm being prompt once more to turn on TestFlight.

is there as save button, or a step that i'm missing.

**Edit**

I've also noticed that there is a yellow triangle with an exclamation mark in it. My searches online have stated that this could be an issue with the provisioning profile missing the following key:

<key>beta-reports-active</key>

but i have located said key within my provisioning profile. i'm not sure if that helps in any way, but wanted to provide a bit more information as i came across it.

I've never used TestFlight... the steps I shared are basically what I follow to submit the final version.

Like Dave mentioned earlier, I also use AirLaunch for sharing beta versions of my apps.

Hi Randy!

Thanks for getting back to me on this. I've been looking more into AirLaunch, and think that is probably gonna be the way that i'm gonna go. I just wanted to follow up and thank everyone for all the help they've provided.

Regards,

Sean

I've got my app up and running in TestFlight, but still think i'll be using Airlaunch in the future.. for anyone who is looking to run an alpha or a beta in TestFlight through a mix of resources i've found a fix that seems to have been a fix for me.

here is a link to the page that helped me. hope it helps you.

http://lists.runrev.com/pipermail/use-l ... 10693.html

Indeed, this fix works. TestFlight permits distribution to up to 1000 users. An email address is all that's needed. AirLaunch is a slick implementation of ad hoc distribution. It is limited to 100 devices and requires a UDID for each device. For those who find their way here in search of a solution to the TestFlight beta entitlement error, here are step-by-step instructions:

1. Make a copy of LiveCode (optional, but you’ll be modding it so recommended).
2. Right click on the copy you just made and select Show Package Contents
3. Navigate to Contents→ Tools→ Runtime→ iOS where you’ll find one or more folders named Device-X_X. In each of those folders you’ll find a file called StoreEntitlements.xcent. That’s the file you need to modify, not the one called Entitlements.xcent
4. Open each StoreEntntlements.xcent file in your editor of choice (I used Text Wrangler) and change it from this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>application-identifier</key>
<string>${APP_IDENTIFIER}.${BUNDLE_IDENTIFIER}</string>
<key>get-task-allow</key>
<false/>
${REMOTE_NOTIFICATIONS}
</dict>
</plist>

To this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>beta-reports-active</key>
<true/>
<key>application-identifier</key>
<string>${APP_IDENTIFIER}.${BUNDLE_IDENTIFIER}</string>
<key>get-task-allow</key>
<false/>
${REMOTE_NOTIFICATIONS}
</dict>
</plist>

5. Save the changes to each StoreEntitlements.xcent file
6. Use the version of LiveCode you just modified to build the standalone you want to submit as a prerelease for distribution via TestFlight