Hello all and thanks for your interest in helping your fellow CoronaSDK developers out by testing their apps!

We are keeping track of testers' UUID numbers on a shared spreadsheet on Crawl Space's Google Docs account, so if you are serious about helping test and having your own apps tested, email adam@crawlspacegames.com and I will share the document with you, where you can add your information.

Some guidelines reporting:

- Pay attention to bugs, not the ridiculous amount of fun you're having (or a good mixture of both!)
- Take screenshots of odd behavior
- Keep track of what steps you took to reproduce bugs and crashes
- Report back in a timely manner ( otherwise the author may have already submitted their app )

Thank you again for helping out the community!

a.

This sounds great, I'm sending you my email.

Glad to be here.

Email sent! Thanks!

Not sure if this will be helpful or not but I just registered for this service - http://www.testflightapp.com - not sure what the pricing will be in the end and haven't had a chance to actually use it yet but it looks interesting.

hey thanks for that link, I haven't seen that before.

Another beta test site is www.ibetatest.com

WOOOOO WHOOOOO im in will send the email.

Is UUID your device identifier number? How will this work - can you send your app build to other people?

Miro, yes. You need to authorize each device and add their UDID number to your certificates through Apple's provisioning portal. More info here:

https://developer.apple.com/ios/manage/devices/howto.action

This is what I email to people I want to include in my tests:

To be able to install unpublished apps, we’ll need to authorized your iPad/iPhone. To do that, I need the ID number from the iPad receiving the test file.

Then use it to email me your UDID number (that’s the really long ID number for your iPad).

Using this app is much easier than having them try to copy the UDID number from their device. Then I zip my app, put it on my ftp server and give them a URL. Once they've downloaded it and unzipped it, they can drag it into iTunes to install.

The instructions I tell people is how to find their UUID in iTunes, so that they don't have to bother downloading an app:

http://www.appbite.com/how-to-find-your-iphone-uuid-using-itunes/

jhocking, that's great! I've tried getting it from iTunes, but since trying to select it to then copy it seemed impossible, I gave up on that method. Much easier this way, as long as you have your computer handy.

Hey excellent! Glad I was pointed towards this thread!! Also, to email your UDID, there's an app for that!

http://itunes.apple.com/us/app/udid-sender/id306603975?mt=8

Not sure if it's any good, but looks easy enough!

Hey everybody,

So glad for such a positive response! I think I got everyone in the doc now.

It looks like we may need a thread for keeping all these tools easy to find too. Here's an article on the Test Flight App: http://gigaom.com/apple/ios-app-beta-testing-takes-with-testflight/

According to that, it sounds pretty slick. I'm up for giving it a shot, so thanks for finding it Graham!

I think we could start posting builds anytime now. I'll be posting one (hopefully) later this week, and it sounded like a few other folks will be too. I'm sure there will be kinks in the system, but I don't think they'll be too difficult to work out.

Happy testing!

a.

No problem, happy to help! When I get my devices sorted I will be adding them to the list/group as well.

And when I actually get round to making an app/game rather than a tool I will be submitting the builds :-)

Should I have received an email from you about the doc? I think gmail has been randomly dropping some of my messages for a couple weeks now, it is very annoying.

Has anyone else missed the email? jhocking, you do have access, so maybe check your spam folder? I'll resend you the link too.

*snip*

Received my link just fine guys!

Thanks for resending it, I got it this time.

I added an additional column for our email addresses, since I figure we should be able to directly email the people we make ad hoc builds for. The other means we have to tell each other about beta builds is posting on this forum, but I don't know if we can really count on everyone noticing that.

Alright so it looks like Test Flight is really the way to go about beta testing. @GrahamRanson thanks for suggesting it. I would encourage everybody to check it out!

Of course, if anyone has a problem with the system, we can continue posting builds manually for download, and I won't close down the GDoc, but the ease of testing with http://testflightapp.com is incredibly attractive.

Does TestFlight require iOS 4? It's kind of an odd question, but I have purposely not upgraded my phone because of a private app that never got updated.

Come to think of it, even if TestFlight requires iOS 4, would that be any problem for me? I mean, it's not like I'm sending the app to myself.

ADDITION: Y'know, I've been not upgrading for so long that I've stopped thinking about why. But the app I needed, well, I no longer need.

So, uh, how do you recruit testers? I'm still not quite ready to start beta testing but I am getting myself set up. I guess I'll start by sending a tester invite to everyone on the Google doc, and then email some friends who want to help, but does testflightapp have anything beyond their suggestion to tweet about your beta:

http://support.testflightapp.com/kb/tutorials/becoming-a-tester

Hey all,

So we here at Crawl Space have been using TestFlight for a few weeks now, and it's been super stellar both for sending out beta builds AND sending out pre-release builds to writers and reviewers. It makes the whole process massively more simple.

With that in mind, I don't see any need to maintain the G-doc, and I think it may be best to just post the recruitment links on a forum here. If you decide to stop taking requests, simply turn off recruitment in TestFlight. Once everyone is signed up with TestFlight, I think it will solve every problem we have been struggling with.

Yes, TestFlight requires iOS 3.2 or higher. If you want beta testing for 3.1.3 or lower that may need to be on a case-by-case basis.

Probably still a good idea to incorporate the suggestions from Carlos.