Unity 3f5 OSX won't build standalone

Unity Engine
1

Building a standalone acts like it’s working and says that it’s importing the assets. But then the build doesn’t produce an app bundle and sometimes throws this error:

Moving Temp/498df36e4e3094fc7ba52334a729a6b1.dll to Library/ScriptAssemblies/Assembly-UnityScript.dll failed because the file or directory does not exist.

And in fact, the app bundle was not created, so there is no destination. I’ve tried a couple of different destination locations on my machine (permissions in this folder are for Me as read/write).

On OSX 10.6.4.

Monodevelop is connected to Unity, but not running when I do this.

Anything I can do to bust this loose?

2

OK, after reimporting all my scripts, I got some errors in the console that explained the problem. You can’t reference Editor classes in scripts you want to include in the runtime.

3

correct
that was actually never possible, but now it will throw it at you much more obvious than in U2

4

Thanks for the confirmation. It makes sense; it just confused me because it was silently failing for a while. I pulled out all the editor calls.