Ok well I just downloaded the new unity iPhone update. Before it I had the occassional crash but it wasn’t frequent… Now I cant complete a level without it crashing. Just thought I’d mention it.
Please submit bug with your app attached.
i must admit the update has made things more unstable for me as well. notably i now have to constantly shutdown reopen unity for the remote to work - otherwise it just permanently loses the connection. version 1.0 was a rock. i also (now) catch frequent off-the-wall debug strings appearing in the editor after… what… i dont know exactly, its hard to pinpoint. my workflow is pretty intense so im in/out of code, pausing, updating assets… all the stuff unity is legendary for but now just feels a little less solid. everything is still running ok though.
How do I submit a bug / attach the app without unity crashing? (When I experienced crashes it was the iphone game crashing, not unity on my pc).
Thanks
Adam.
I have also noticed much more frequent errors when building my player. Sometimes it’s the AOT Boo error, other times its something else. But I haven’t submitted a bug report because, though it is somewhat frequent, it is still very sporadic and can’t be reproduced based on a certain circumstance that I can tell. But it happens on all of my projects.
It’s only a minor nuisance though since I just have to restart Unity every couple of hours to get it to do a build. Not the end of the world, but it would be nice not to have to.
If you have a problem where the app on the iPhone crashes, then submit the full project folder so that we can make a build. Please make sure to specify if you can fully reproduce the crash and the exact steps on how to reproduce it on the device.
Before you submit though, check if it isn’t a null reference exception, by looking the console log in xCode.
Like Brady, with 1.0.1 I am noticing intermittent failure of AOT cross compile step in the Editor (errors out before XCode launches). This happens apparently when Unity has been running for a long while. Every time after re-launching Unity, it builds on the first try. I have not had any crashes of my app on the device. Sorry I can’t narrow it down or replicate it!
I’m also having trouble with the remote…slowdowns, disconnects, failures to connect. It’s bad enough that I can’t really use it any more 
Unity Remote is working perfectly for me w/ 1.0.1 version. Did you build and install the new Unity Remote on your device?
Yes. The old one did not work at all with 1.01.
Russ- that’s a bummer. File a bug report! Maybe it’s your combination of Mac + wireless setup or something.
Unity Remote has changed qualitatively in this release. Today I noticed I have to futz around with it sometimes to get it to work. Sometimes I gotta quit Unity and re-launch. Sometimes I noticed when the remote says “waiting for game view”, I just start swiping and/or shaking the device and the game control is working, it’s just not displaying images on the remote, which is alright. Sometimes the image takes a second to catch up on the remote. But it usually works perfectly for me once it gets rolling!
That is exactly the behavior I’m seeing, but much more frequent. I have been holding off on filing a bug report because it’s so intermittent…I can’t send them anything that will allow them to reproduce it reliably.
It worked really well on 1.0, so I don’t think it’s my wifi or machine…none of that changed.
I filed one because I sometimes see an assertion failure in the console, and got a screengrab of it
http://intra.unity3d.com/fogbugz/default.asp?70689_7l315j1s
Cool…I’ve seen that assertion too, but hadn’t correlated it. Hopefully that’s enough for them to work with.