2018.08.09

Downloading Unity 5 for Windows:If you are working on Windows, you can download the 32-bit version of Unity 5:once you land on the Unity download page,you should see a dropdown menu with title "Additional Downloads" and sub-header "For Windows"; for there you can download the 32bit version called "Unity Editor (32bit)".

Tips:if you experience a "CodeSign failed" error in Xcode when trying to submit your Unity iOS App to the App Store, you can resolve the issue by following one of these procedures:

1. In your Unity project:Select the QCARWrapper.bundle in the Unity Project view (located under Assets > Plugins ), so that its settings are shown in the Unity InspectorChange the settings of QCARWrapper.bundle in the Unity inspector from "Any Platform" to "Standalone + Editor". ​

(或者)OR:2. In the Xcode project generated by Unity:Go to Build Phases > Copy Bundle ResourcesRemove the QCARWrapper.bundle file from the listRebuild

原文链接

2018.7.20

1. validateRenderPassDescriptor:551: failed assertion `Texture at depthAttachment has usage (0x01) which doesn’t specify MTLTextureUsageRenderTarget (0x04)’ ”’ 

两种办法解决

1.1 Product -> Scheme -> Edit Scheme -> Run -> Options -> GPU Frame Capture -> OpenGL ES 

1.2 Unity Other Setting -> Auto Graphics API 取消勾 -> OpenGLES2  

2018.6.27

1. 编译出现错误：

编译出现："_kSecReturnData", referenced from:（以下省略）..."

解决方法：添加库文件Security.framework即可

2.真机运行，BuildSettings->bitcode 改为NO，

出现的错误：

ld: '/Users/xxxxxx/Desktop/新建文件夹2/Libraries/Plugins/iOS/libQCARUnityPlayer.a(Tracker.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64

3.Library Search Paths，Header Search Paths 中 路径中注意查看是否有"\"，有的话讲"\"改为"/". 

出现的错误：

Apple Mach-O Linker (ld) Error Group

ld: warning: directory not found for option '-L/Users/xxxxxx/Desktop/新建文件夹2/LibrariesPlugins/iOS'

ld: library not found for -lVuforia

clang: error: linker command failed with exit code 1 (use -v to see invocation)

        简单记录下，方便以后使用，运行编译Unity工程中出现的问题，具体问题具体分析，根据报错，修改调试。希望帮到遇到相同问题的朋友。