Log in or register to post comments

Occasional Build Issue

December 13, 2010 - 1:20pm #1

When I build an application in Unity, I tend to get the error "IOException: Win32 IO returned 1224. Path: C:\.....MyProjectName\Temp\StagingArea\res\values\strings.xml".

This always occurs during the 'Converting java .class to dex-format' of the build, and immediately drops out of the build process when it happens. Weird thing is... if I keep attempting to build, it will eventually go through and deploy the app to my device (Nexus One).

Not a high priority error since it seems to fix itself if I persist long enough but it often takes 5-6 build attempts to be successful. Any ideas? :)

--Kenner

Re: Occasional Build Issue

January 6, 2011 - 10:21am #4

Sure, I'd like to see an example of the issue. You can zip up the project and send it to

. Also, let me know what OS you are using for development. Thanks!

- Kim

Re: Occasional Build Issue

January 6, 2011 - 9:30am #3

Just realized I'd forgotten to reply to this one. :)

I'm using the most recent version of Unity, 3.1.0f4. Deleting the Temp/StagingArea doesn't seem to change the frequency of it occuring.

I made a little test app and it built just fine consistently. Something else to note is that I'll also occasionally get an "Error in file E:/BuildAgent/work/...../BuildPlayerWindow.cs at line:289" or "Error building Player because scripts had compiler errors."

Should I send an example application that's having an issue?

--Kenner

Re: Occasional Build Issue

December 13, 2010 - 1:30pm #2

Hmm, we haven't heard of this one before, what version of Unity are you using?

I found this post in the Unity forums, sounds similar but there's no clear solution:

http://forum.unity3d.com/threads/48935-Win32-IO-returned-1224

Do you get the same behavior if you try building a basic Unity application without the QCAR SDK?

Finally, you might try deleting the entire Temp/StagingArea folder before building your project. It's one extra step, but if your OS is keeping a lock on the file that could help clear it for a fresh build.

- Kim

Log in or register to post comments