this has worked for me, but every time i build to iphone the files return! I know that unity is for some reason adding in the custom splash screen, then telling me that it wont support them because its not pro. way to go Unity, giving me a month of pro from ggj, and then screwing me over afterwards.
if anyone knows how to keep these files out of xcode, please let me know, i’m using the most updated versions of everything
I know you said you’re using “Updated version of everything?” But that leaves us guessing still - what version of Unity are you using?
I assume that you added a custom splash screen during your ‘demo pro’ period? If so, I expect there are some remnants left behind - maybe try track down where they may be in your Unity project (have you deleted the Library and Temp folders - a long shot, but just in case).
Sorry, I was using 4.6.3.f1. I tried every possible suggested help item and fix, and nothing helped.
No. If a texture option is not working, or there is some clipping here and there, such issues are fine, and we can all merrily laugh at them at the way to the bar, knowing it will all be ok in the next build.
An issue like this ceases all life. All development. I need to test certain features to work in the device, not in the simulator. We can well say that the deployment of the application to the target platform is a basic use case for this software. Smoke testing such critical application functionality should be the first thing done in any even the most archaic QA plan in existence. Thus, I used the term “show-stopping”.
Btw: Those of you using Unity 4, try 4.6.0, this issue is not repeating there!
Currently installed Unity 5, not having this error, yay. 
You’ll note as I’ve said three times - that this IS fixed in 4.6.3p1 (note that is p1 not f1) that was release about a week ago. Again, you did not mention if you’ve tried it or not so I’ll assume that you have not.
Note, that I’ve been using 4.6.3f1 and NOT had this issue - you’re assuming it is happening in every case, it is not. Expecting that UT QA can find all possible instances of every bug with their short turn around (which is amazing) is short sighted. There must be a certain set of events occur for this error to be present. Note the lack of screaming people in this thread? That’s because it only happened for a tiny fraction of users.
As I stated in a previous reply (and you did not confirm either way): I assume that you added a custom splash screen during your ‘demo pro’ period? If so, I expect there are some remnants left behind - maybe try track down where they may be in your Unity project (have you deleted the Library and Temp folders - a long shot, but just in case).
See my point above - this is NOT happening for everyone and IS fixed in the previous patch release (which it seems you keep missing the point despite the fact that I’ve been highlighting the p1 for you every time - please be rigorous when reading help given to you
But again, I have no idea if you’ve tried it yet as you have failed to give sufficient information or you have overlooked the detail in my replies. If this issue is so important to you, read the replies carefully and give explicit detail on in your replies or we’re left guessing and have little chance of helping you.
As stated MANY times, this is fixed in 4.6.3p1 - which has been out for almost a week now.
i love you
I am seeing this exact problem in 4.6.3p2. Like building and deploying for iOS isn’t an interminably long goddamn process to begin with…
And for what it’s worth, Kaharoth’s workaround was effective at patching the issue.
I’m really looking forward to repeatedly deleting files out of the auto-generated xcode project for the next 2 months.
Submit a bug report with a project that reproduces the issue and you won’t need to wait 2 months - they do patch releases every week at the moment.
Also - what is the ‘exact same issue’ there are a few issues discussed in this thread.
kaharoth’s suggestion
worked for me. (Unity 4.6.3f1, Xcode 6.3.2, OS X 10.10.3 Yosemite)
Thank you kaharoth.