Crashing at splash screen

Hey guys, I'm sorry if this is a repeat question, but I've been crashing just after splash screen.

When I port Unity's 4.3.5f1 IOS build (windows) to my mac, and launch it in Xcode 5.1.1, the only warning I get is the Retina 4 inch Support Missing "Default-568h@2x.png" launch image (which I still can't get to go away)

If I build to a certified device, it's successful but on launch it closes immediately after the launch screen! (that black "unity" screen as I havn't purchased pro just yet)

In the OUTPUT dialog box I do see this;

The assembly mscorlib.dll was not found or could not be loaded.

It should have been installed in the '/var/mobile/Applications/*******/FvA.app/Managed/mono/2.0/mscorlib.dll' directory

I'm very new to macs, and to xcode in general...so I've been tinkering trying to figure out if this is a Unity build issue, or an xcode incompatibility issue or a windows/mac thing...I'm completly lost here. Or maybe I do not have some magical box checked somewhere...

Any help is appreciated! thanks

 

Why not just download that dll and put it there

 

Well like I said, I'm very new to this and downloading .dll's and tossing them in there manually seems strange to me. Shouldn't that .dll have already been in there from unity making the build?

Looking at the build that Unity is creating mscorlib.dll is in there in a few places, just not the specific place Xcode is asking for. I tried to simply "copy/paste" the .dll into the appropriate folder, but the error still showed up, and the app crashes just after splash screen.

 

Well I work with Visual Studio and work with dll files everyday. Also that file is part of the NET framework. On a MAC you should have:


/Applications/Unity/Unity.app/Contents

./Frameworks/Mono/lib/mono/2.0/mscorlib.dll
./Frameworks/Mono/lib/mono/micro/mscorlib.dll
./Frameworks/Mono/lib/mono/unity/mscorlib.dll
./Frameworks/Mono/lib/mono/unity_web/mscorlib.dll
./Frameworks/MonoBleedingEdge/lib/mono/2.0/mscorlib.dll
./Frameworks/MonoBleedingEdge/lib/mono/4.0/mscorlib.dll
./Frameworks/MonoBleedingEdge/lib/mono/unity/mscorlib.dll
./Frameworks/MonoBleedingEdge/lib/mono/unity_web/mscorlib.dll

Just drop that bad boy where ever you need it. Seems that it got corrupted.

 

I've made several rebuilds of this project, and the discouraging thing is, it never gets created from Unity.

I've tried copy pasting that dll, from one spot in the project where it is, to the place Xcode is asking for it, and it still doesn't solve the problem.

Not knowing much about Xcode, this is proving very frusturating

 

Yes there is a copy of it in Data/Managed...however Xcode wants it in another folder as well. What I have done though is on the mac, made a copy of the dll and moved it to the folder in question and Xcode still said it was missing!

Xcode is really proving to be frustrating!

 

Well here's the latest;

This is now a RED error. It seems like Unity doesn't want to make enough Icon images to support all versions of IOS???

This is the "asset catalgue" error I get which seems to me that my Unity build is not coughing out enough Icons to support all available slots for an Iphone build???



Between this, and that other dll file not being created in the oppropriate directories, I feel as if I'm doing something wrong here.

So to list how I'm doing this step by step

- I'm making the project in Unity 4.2.1f4 (because it's a 2d game and to use the latest unity I get a ton of NGUI yellow errors that would be a pain to update and get rid of at this point)
- Open the game in Unit 4.3.4f1 when I'm ready to create a build
- Switch platforms
- build for IOS (default settings, development build checked)
- senf build folder to dropbox
- grab build folder from dropbox onto my mac
- open xcode 5.1
- instantly get 2 yellow errors and now a red error

This one will go away if I ask Xcode to update the file structure...though I do not understand why I get this

 

I always manually drop the needed Icons in the Xcode project after I build it with Unity because they always seem to get corrupted.

Yea Unity has bugs. I work in it every day so I get around these little things. Hells bells.

 

Yeah, still crashing at start up. I get the unity launch image, and then a rief flash of what looks like my stretched out app icon...and then the app disappears.

I'm still seeing this error;

The assembly mscorlib.dll was not found or could not be loaded.

It should have been installed in the '/var/mobile/Applications/******/FvA.app/Data/Managed/mono/2.0/mscorlib.dll' directory.

Where is this??? Is this the same as the Unity build directory? I'm getting the feeling that it's not as I've copied that dll to that location and yet xcode says it's not there. Yet I can't find a folder "var" anywhere on my mac!

 

I'll try that graham, thanks

Out of curisoity, could any of this be a bad provisioning profile? or some other setting i may have messed up in developer.apple?

 

Graham I want to thank you and the others for your attempt at assistance with this; probably the single most frustrating thing to try and work out by myself considering that before this, I have not touched a Mac since 04.

So I have finally gotten this thing to work flawlessly and in fact it turned out that I had missed a few very important steps when creating my provisioning profiles and allowances through developer.apple.com. As well as some key build settings in Unity to insure that it was looking to my certificates.

I have found this https://www.youtube.com/watch?v=VDQgoU75248 And I have to say while, he struggles to explain a few definitions as to what is a Certificate, provisioning profile and Identifiers, he gets the job done.

Sooo, I had to start completely from scratch. I deleted all my old certificates and profiles, and identifiers. And followed this guys video to the letter, and she built up flawlessly!

I have never experienced a more complicated and convoluted system in my entire life. I'm sure their is a reason it has to be the way it is, but let's just say that having gone through this hell and emerging on the other side I can say I absolutely DETEST macs...and apple in general. LOL.

That being said, thanks again to everyone who attempted to help my dumb ass muddle through this.