Yap, I could reproduce this myself because I created a new iOS certificate for myself that is not installed either. Obviously it is an easy fix to install you by hand (which we did for all builds until now), but I really want to automated the last bit now. Thanks for testing and staying with the pain, we are almost there ;)

Ok... Well...

The good news is that the building worked fine!
- Received the package
- Opened up iTunes
- Dragged the .app folder into the Library section
- It's listed fine alongside the other apps (although it has no rating/purchase date/seller or genre)
- I go to the Device section and select my iPad
- It's listed in the Sync Apps section (although with the default icon)
- I tick it and click Sync and the progress bar reports 'Copying FindIt' and completes in iTunes without error. The app remains ticked
- But on my iPad it simply reports "iTunes Sync: 'FindIt failed to install'"

Any pointers as to where we can look as to the issue? Is there an error log in iTunes or anything?

Edit: Ugh. After a spot of Googling it looks like I must have messed something up in the certification process. I'll have to go through all those convoluted steps again...

Edited by user Wednesday, April 25, 2012 7:16:06 AM(UTC)  | Reason: Not specified

On an unrelated note it still seems awfully big. The whole thing is 70MB (17MB zipped); Of that 56MB is the FindIt file itself.

(The Content is doubled up with both the Atlas files and the single files included, but I assume you're fully aware of that and it's a trivial size in comparison)

There are basically 3 ways on iOS:

- Development, which is a bit easier to test locally and is usually used for debugging. You still need a certificate and mobileprovisioning. <- this is what you are using and what I used mostly for testing, but today I am testing AdHoc a bit ..
- AdHoc Distribution, good for testing with others and building the release version, different certificate (distribution) and different mobileprovisioning files. Other than that very similar to Development, but you can build a IAP file (e.g. for a weblink to install more easily). I am currently trying to build a website for the ipa download directly from a iOS device, which simplifies the process enourmeously.
- AppStore, this is the final version you will build to upload to the Apple AppStore. It is the same as AdHoc, but needs a different AppStore Mobileprovisioning file. This version won't run on any of your devices, only after it is available in the AppStore users can get your app (if Apple approves it).

Also put here: http://deltaengine.net/Wiki.IOSDevelopment

Hope this helps.

Edited by user Thursday, April 26, 2012 2:27:30 AM(UTC)  | Reason: Not specified

Deployment to iPad worked :)

(Revoked the old certificates and went through all the steps again. No idea what I did differently this time, but, hey!)



Now the serious coding work begins...!

Edited by user Wednesday, April 25, 2012 8:08:11 PM(UTC)  | Reason: Not specified

Ok... So I built FindIt and received the new ipa format file - which synced onto and runs fine on my iPad (so yay for that!)

I was hoping it wouldn't work, though, because I built a different app (basically just testing my 2D camera - trying to pan and zoom around a single background image) - and though it installed fine, on running on the iPad the screen goes black for a few seconds before returning to the iPad desktop. No error message reported or anything.
(This new app builds fine for and runs fine on Windows.)

What's the next step I can take to identify what's going wrong?

(Also, if this question should be in a new thread let me know)

Oops! I forgot to mention something very important! I'm reusing the certificates from the FindIt app for this app. Is that likely to cause this issue? You implied I could reuse the same certificates but perhaps I can't?


****

Ok - so my mistake. I needed to create a new .mobileprovision file for the new app. Once I did that it ran ok.

It's just all a bit unhelpful (by Apple, not you!): It should error on installation if it didn't like the certification - or give me some details of the problem at least! Installing fine and then just blackscreening on running is not especially helpful...

Edited by user Friday, April 27, 2012 7:10:53 AM(UTC)  | Reason: Not specified

Just had the same thing happen with one item in my SpaceTD project. Been building all day and suddenly it happens from nowhere:

It put the item into its own dxt5 file but used the Atlas UV coords.

No no, it's no bother at all. Just wanted to raise it in case you needed another example to help pin down the problem.

Sorry about the issues. I finished testing Android, iOS and Windows building in the beginning of the week and had some testers help me out. Build times were also very good (all in the range of a few seconds, iOS a bit more, but still under a minute). When trying it out on the real servers things did not go so well and I was not able to fix all issues so I reverted to the last working version from a week ago (because I am currently in Holidays and Internet sucks here, but I will be back in a week). Sorry that it did not work out for you, maybe I reverted too far back (I tested Android, Windows and iOS building, but maybe my projects were too simple).

It probably makes most sense that I will contact you in a week when I will put the new code live and give you a chance to test it out with your projects.