RE: semi-OT: TestFlight.com beta testing closing
Chris, I just got back to this and it work like a charm. Nice not to do the whole ad-hoc thing. Just wanted to thank you for this!!! Did you put in a QCC request to have RR put the key into the StoreEntitlements.xcent file? It is not in 6.7.3. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 1:53 PM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Ralph, I think I got it to work. I created an app build using an App Store distribution profile, not Ad Hoc, as Colin suggested. I also added the following to my StoreEntitlements file: keybeta-reports-active/key true/ This should go right before the closing /dict tag, if you’re just using a text editor. I would recommend creating a copy of that file before modifying it, just in case. After creating a build and uploading it, I no longer see the beta entitlement warning, and I can turn on beta testing for that build. Pretty cool. :) So it seems as though RunRev simply need to add this to the entitlements file in a future release of LiveCode. That should fix the issue for everyone going forward. On Jan 27, 2015, at 9:51 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: I'm trying to use the new TestFlight. I created a new distribution profile. This is supposed to include the Beta entitlement. I refreshed Xcode and the new profile appeared and was on the LC provisioning profile list. I selected it and created a standalone. Uploaded via the application loader. On iTunes connect I see the dreaded To use TestFlight Beta Testing, build 1.326.1 must contain the correct beta entitlement. For more information, see the FAQ. The FAQ states 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. Do I also have to add the Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements key to StoreEntitlements.xcent or Entitlements.xcent or both? Is there a cookbook for this? MacBook Pro OSX 10.9.5 Xcode 6.1.1 LC 6.7.1 Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 11:08 AM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Mike, Yes, I found HockeyApp yesterday as well. Looks very similar to TestFlight. We’ll probably end up giving that a go for now. Thanks, Chris On Jan 26, 2015, at 3:09 PM, Mike Kerner mikeker...@roadrunner.com wrote: There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-re p orts-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Ralph, Yes, it worked for me as well. I haven’t filed a request yet. I thought I had. I’ll go ahead and do that today. On Feb 27, 2015, at 10:05 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: Chris, I just got back to this and it work like a charm. Nice not to do the whole ad-hoc thing. Just wanted to thank you for this!!! Did you put in a QCC request to have RR put the key into the StoreEntitlements.xcent file? It is not in 6.7.3. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 1:53 PM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Ralph, I think I got it to work. I created an app build using an App Store distribution profile, not Ad Hoc, as Colin suggested. I also added the following to my StoreEntitlements file: keybeta-reports-active/key true/ This should go right before the closing /dict tag, if you’re just using a text editor. I would recommend creating a copy of that file before modifying it, just in case. After creating a build and uploading it, I no longer see the beta entitlement warning, and I can turn on beta testing for that build. Pretty cool. :) So it seems as though RunRev simply need to add this to the entitlements file in a future release of LiveCode. That should fix the issue for everyone going forward. On Jan 27, 2015, at 9:51 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: I'm trying to use the new TestFlight. I created a new distribution profile. This is supposed to include the Beta entitlement. I refreshed Xcode and the new profile appeared and was on the LC provisioning profile list. I selected it and created a standalone. Uploaded via the application loader. On iTunes connect I see the dreaded To use TestFlight Beta Testing, build 1.326.1 must contain the correct beta entitlement. For more information, see the FAQ. The FAQ states 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. Do I also have to add the Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements key to StoreEntitlements.xcent or Entitlements.xcent or both? Is there a cookbook for this? MacBook Pro OSX 10.9.5 Xcode 6.1.1 LC 6.7.1 Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 11:08 AM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Mike, Yes, I found HockeyApp yesterday as well. Looks very similar to TestFlight. We’ll probably end up giving that a go for now. Thanks, Chris On Jan 26, 2015, at 3:09 PM, Mike Kerner mikeker...@roadrunner.com wrote: There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-re p orts-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Hi Ralph, I just added an enhancement request: http://quality.runrev.com/show_bug.cgi?id=14706 http://quality.runrev.com/show_bug.cgi?id=14706 Hopefully we'll see it in the next version of LC. :-) On Feb 27, 2015, at 10:05 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: Chris, I just got back to this and it work like a charm. Nice not to do the whole ad-hoc thing. Just wanted to thank you for this!!! Did you put in a QCC request to have RR put the key into the StoreEntitlements.xcent file? It is not in 6.7.3. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 1:53 PM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Ralph, I think I got it to work. I created an app build using an App Store distribution profile, not Ad Hoc, as Colin suggested. I also added the following to my StoreEntitlements file: keybeta-reports-active/key true/ This should go right before the closing /dict tag, if you’re just using a text editor. I would recommend creating a copy of that file before modifying it, just in case. After creating a build and uploading it, I no longer see the beta entitlement warning, and I can turn on beta testing for that build. Pretty cool. :) So it seems as though RunRev simply need to add this to the entitlements file in a future release of LiveCode. That should fix the issue for everyone going forward. On Jan 27, 2015, at 9:51 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: I'm trying to use the new TestFlight. I created a new distribution profile. This is supposed to include the Beta entitlement. I refreshed Xcode and the new profile appeared and was on the LC provisioning profile list. I selected it and created a standalone. Uploaded via the application loader. On iTunes connect I see the dreaded To use TestFlight Beta Testing, build 1.326.1 must contain the correct beta entitlement. For more information, see the FAQ. The FAQ states 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. Do I also have to add the Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements key to StoreEntitlements.xcent or Entitlements.xcent or both? Is there a cookbook for this? MacBook Pro OSX 10.9.5 Xcode 6.1.1 LC 6.7.1 Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 11:08 AM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Mike, Yes, I found HockeyApp yesterday as well. Looks very similar to TestFlight. We’ll probably end up giving that a go for now. Thanks, Chris On Jan 26, 2015, at 3:09 PM, Mike Kerner mikeker...@roadrunner.com wrote: There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-re p orts-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe
RE: semi-OT: TestFlight.com beta testing closing
Colin/Chris, Ad Hoc's work just fine. I used a Distribution certificate to generate the new provisioning profile. Apple says in the FAQ 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. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 12:26 PM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Interesting you used the App Store profile. I didn’t think that worked, so I’ve used an Ad Hoc profile when I’ve tried it. I thought an app store distribution profile was strictly for that, the App Store. So your testers can download the build just fine? No problems installing and running on devices? On Jan 27, 2015, at 9:59 AM, Colin Holgate co...@verizon.net wrote: According to what you say Apple say, you would think the provisioning would include the entitlements. One thing though, did you do Ad Hoc or App Store? For an AIR app I have in Test Flight I used the App Store version. ___ 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 ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Ralph, I think I got it to work. I created an app build using an App Store distribution profile, not Ad Hoc, as Colin suggested. I also added the following to my StoreEntitlements file: keybeta-reports-active/key true/ This should go right before the closing /dict tag, if you’re just using a text editor. I would recommend creating a copy of that file before modifying it, just in case. After creating a build and uploading it, I no longer see the beta entitlement warning, and I can turn on beta testing for that build. Pretty cool. :) So it seems as though RunRev simply need to add this to the entitlements file in a future release of LiveCode. That should fix the issue for everyone going forward. On Jan 27, 2015, at 9:51 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: I'm trying to use the new TestFlight. I created a new distribution profile. This is supposed to include the Beta entitlement. I refreshed Xcode and the new profile appeared and was on the LC provisioning profile list. I selected it and created a standalone. Uploaded via the application loader. On iTunes connect I see the dreaded To use TestFlight Beta Testing, build 1.326.1 must contain the correct beta entitlement. For more information, see the FAQ. The FAQ states 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. Do I also have to add the Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements key to StoreEntitlements.xcent or Entitlements.xcent or both? Is there a cookbook for this? MacBook Pro OSX 10.9.5 Xcode 6.1.1 LC 6.7.1 Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 11:08 AM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Mike, Yes, I found HockeyApp yesterday as well. Looks very similar to TestFlight. We’ll probably end up giving that a go for now. Thanks, Chris On Jan 26, 2015, at 3:09 PM, Mike Kerner mikeker...@roadrunner.com wrote: There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-rep orts-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
You say Ad Hoc works fine, but that Apple say to use App Store. In my successful Test Flight test I’m using App Store, not Ad Hoc. Ad Hoc would only work on your 100 internal test devices, to work on the 1000 external devices you should use App Store. On Jan 27, 2015, at 6:54 PM, Ralph DiMola rdim...@evergreeninfo.net wrote: Ad Hoc's work just fine. I used a Distribution certificate to generate the new provisioning profile. Apple says in the FAQ 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. ___ 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
RE: semi-OT: TestFlight.com beta testing closing
Colin, Thanks! Sorry I was not clear. I use Ad Hoc for testing with the internal 100. Ad Hoc has worked in the past and still works. I used Distribution profile when attempting to get TestFlight working. It look like Chris solved this. Chris, Thank you for running this down! Beta should be a check box in standalone settings. Or is it ok to include it at all times? Not clear on this. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Colin Holgate Sent: Tuesday, January 27, 2015 2:00 PM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing You say Ad Hoc works fine, but that Apple say to use App Store. In my successful Test Flight test I’m using App Store, not Ad Hoc. Ad Hoc would only work on your 100 internal test devices, to work on the 1000 external devices you should use App Store. On Jan 27, 2015, at 6:54 PM, Ralph DiMola rdim...@evergreeninfo.net wrote: Ad Hoc's work just fine. I used a Distribution certificate to generate the new provisioning profile. Apple says in the FAQ 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. ___ 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
RE: semi-OT: TestFlight.com beta testing closing
I'm trying to use the new TestFlight. I created a new distribution profile. This is supposed to include the Beta entitlement. I refreshed Xcode and the new profile appeared and was on the LC provisioning profile list. I selected it and created a standalone. Uploaded via the application loader. On iTunes connect I see the dreaded To use TestFlight Beta Testing, build 1.326.1 must contain the correct beta entitlement. For more information, see the FAQ. The FAQ states 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. Do I also have to add the Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements key to StoreEntitlements.xcent or Entitlements.xcent or both? Is there a cookbook for this? MacBook Pro OSX 10.9.5 Xcode 6.1.1 LC 6.7.1 Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Chris Sheffield Sent: Tuesday, January 27, 2015 11:08 AM To: How to use LiveCode Subject: Re: semi-OT: TestFlight.com beta testing closing Mike, Yes, I found HockeyApp yesterday as well. Looks very similar to TestFlight. We’ll probably end up giving that a go for now. Thanks, Chris On Jan 26, 2015, at 3:09 PM, Mike Kerner mikeker...@roadrunner.com wrote: There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-rep orts-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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 ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Ralph, At this point your guess is as good as mine. I’m not totally sure how to make it work. Haven’t had a chance to try it yet. If someone from RunRev happens to see this and wants to chime in, that would be great. I am planning on filing a bug/enhancement request about this, if no one has done it already. I do know that you wouldn’t do it exactly like this, however. As Colin stated, this is how it’s done for Adobe AIR. You wouldn’t use a CDATA block for LiveCode, for example. I’ve got some time today. I’ll play around with it a bit and see what I can figure out. I’ll let you know. Chris On Jan 27, 2015, at 9:51 AM, Ralph DiMola rdim...@evergreeninfo.net wrote: Do I also have to add the Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements key to StoreEntitlements.xcent or Entitlements.xcent or both? Is there a cookbook for this? ___ 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
Re: semi-OT: TestFlight.com beta testing closing
According to what you say Apple say, you would think the provisioning would include the entitlements. One thing though, did you do Ad Hoc or App Store? For an AIR app I have in Test Flight I used the App Store version. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Mike, Yes, I found HockeyApp yesterday as well. Looks very similar to TestFlight. We’ll probably end up giving that a go for now. Thanks, Chris On Jan 26, 2015, at 3:09 PM, Mike Kerner mikeker...@roadrunner.com wrote: There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Interesting you used the App Store profile. I didn’t think that worked, so I’ve used an Ad Hoc profile when I’ve tried it. I thought an app store distribution profile was strictly for that, the App Store. So your testers can download the build just fine? No problems installing and running on devices? On Jan 27, 2015, at 9:59 AM, Colin Holgate co...@verizon.net wrote: According to what you say Apple say, you would think the provisioning would include the entitlements. One thing though, did you do Ad Hoc or App Store? For an AIR app I have in Test Flight I used the App Store version. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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
semi-OT: TestFlight.com beta testing closing
Just thought I’d throw this out there. Sounds like Apple is killing the TestFlight.com http://testflight.com/ beta testing site in favor of their newer TestFlight service. http://www.idownloadblog.com/2015/01/26/apple-closing-old-beta-testing-test-flight/ http://www.idownloadblog.com/2015/01/26/apple-closing-old-beta-testing-test-flight/ Kind of cruddy, imo. Especially because Apple’s new version of the service only supports devices running iOS 8+, which means no more testing apps on older devices, or even on newer devices running older versions of iOS. Their TestFlight app won’t even install unless iOS 8 is installed on the device. In the education market, we need to be able to test different configurations. I was kind of hoping they would leave this service running a bit longer. We may have to look for something else. Does anyone know of other beta testing services that work similar to TestFlight? Also, the last time I checked into using TestFlight in iTunes Connect, I could not get a LiveCode-built app to work correctly. I kept getting a warning about missing entitlements. Does anyone know if this is fixed yet? I haven’t tried it recently. Thanks, Chris -- Chris Sheffield Read Naturally, Inc. www.readnaturally.com ___ 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
Re: semi-OT: TestFlight.com beta testing closing
There is also hockeyApp, but I'm not aware of anyone trying to make it work with LC On Mon, Jan 26, 2015 at 3:38 PM, Chris Sheffield cs_livec...@icloud.com wrote: Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ 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
Re: semi-OT: TestFlight.com beta testing closing
Thanks, Colin. This may help. In the Runtime folder of the LiveCode application bundle, if you drill down into iOS - Device-[whatever], there is an Entitlements.xcent file. I’m assuming this is where that same key could be added. However, there’s also a StoreEntitlements.xcent, with the same contents as Entitlements.xcent. So I’m not sure which one to make the change in. Maybe both? Does anyone know? At some point RunRev will need to update LC to support his, but in the meantime, this may be a viable workaround. Thanks again. On Jan 26, 2015, at 12:33 PM, Colin Holgate co...@verizon.net wrote: With Adobe AIR you have added this to the app descriptor XML: Entitlements![CDATA[keyget-task-allow/keyfalse/keybeta-reports-active/keytrue/]]/Entitlements That then ends up in the embedded provisioning profile. Not sure of the steps for LiveCode. Test Flight’s URL is https://www.testflightapp.com/ https://www.testflightapp.com/, but as you say, it closes on Feb 26th. If you have an HTTPS site you can post builds for your testers, but those would just be from your list of 100, not from the Test Flight 1000 external testers. ___ 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
