This is for UT. What do you need for bug reports - ie if I send my project, won’t you need a provisioning profile?
Hello,
No, we just need your project, and a dexscription of how to reproduce the problem and what are you trying to achieve 
Basically we need your project folder (generally that would be zip archive containing Assets and Library folders), project description and steps to reproduce the issue.
Conducting a special repro project instead of submitting a whole 700+ MB one would save us a lot of time. Also bugreports with repro projects are of higher priority as they don’t steal whole evening just in order to reproduce the bug.
What I would like to notice explicitly is that normally we do not fix bugs discussed over forums until they are properly submitted. We assume that if people do not eager to submit a bugreport, then the issue is not really that important.
E.g. now we hear some Indie license users experience troubles with static batching, but as we don’t have bugreports and cannot reproduce the bug, we also cannot fix it. And next Unity iPhone release is not far away…
Oh tell us whats coming in the next version, please good sir?
Just hints…
if no one submits a static bug repro project, then be sure to have it in the next Unity iPhone version 
Ough… I’ve lost entire friday trying to recreate/reproduce it.
I guess it will be mainly the hotfix for some of the most urgent things mentioned elsewhere. Like full Snow Leo compatibility, the missing specular shader fix etc…
I guess no new features…
Sorry Woz, this isn’t the static batch bug. I can’t help ya there. My project crashes Xcode when I build from 1.5 but not from 1.0.2. I submitted a report already but just got the ok to send the project. I’ll try to clean it up some so it’s not so much to go thru.
sure, we’ll have a look at it