search

jemast / Unity-Entitlements-Tool

Unity Entitlements Tool lets you codesign all the things! Automate OS X code signing for your Unity projects.
http://jemast.com/unity/unity-entitlements-tool/
16 stars 5 forks source link

Unable to Build and Run Normally #1

Closed tingham closed 11 years ago

tingham commented 11 years ago

Hello. Now that I'm using the Unity-Entitlements tool (which is a life saver) I'm unable to build to an application that I can run locally. I can run in the editor; but I cannot build and run a version in the Finder.

Even after moving the files generated by UET (entitlements and postproc.) away from the assets directory, the built binary shows the following in the console after immediately closing upon launch:

4/28/13 6:48:43.079 PM storeagent[44390]: Unsigned app (/Users/tingham/Builds/demo/My.app). 4/28/13 6:48:43.373 PM com.apple.launchd.peruser.501[230]: ([0x0-0x695194b].unity.Mutiny.My[12827]) Exited with code: 173

Are there cached details after using the code signing tools that need to be manually cleared for this to work again?

jdiprizio commented 11 years ago

Hello.

Very sorry I missed it as I'm not using Git issues for support. Actually exit code 173 is normal for apps built with Mac App Store Receipt Validation enabled in Unity, as the app will look for a valid Mac App Store which it cannot find if it wasn't downloaded from the Mac App Store.

Your issue was not directly tied with Unity Entitlements Tools but rather Mac App Store Receipt Validation so I'm closing this.

To people reading this, you should contact us directly through our website or email (contact -a-t- jemast -d-o-t- com) for support.