iOS Build Environment Help Center

Zappar Face Tracking Plugin - file not found error

append delete billygunn

• Windows Version : Windows 7
• Builder Version : 3.45
• iOS SDK : 15.4
• Link to build log : https://pmbaty.com/paste/?2705133670dbe019#GgN8dYF3p8AXwgpjbXJV3wyTqQMhjufAHrxcdx91Gf1a

Hi Pierre,

Hope you are doing good! I am trying to build the Zappar face tracking sample project from their github page. However, I am getting a "file not found" error as you will see in the build logs.

This might be unrelated to the problem but this plugin does require 2 extra steps that you will find in the last post in this page - https://forum.zap.works/t/uar-unity-ios-xcode-undefined-symbol-errors/8699. For following these steps, I dropped the ZCV.bundle file to the build folder and also linked the OpenGL framework through the builder.

I tested the build on a Macbook and the build is working fine without any issues. Can you please let me know what could be going wrong over here on Windows?

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

From the build log I see here, the cause of the error is that ZAPPAR_METAL_SUPPORT is defined to an empty value instead of being defined to a number, which translates into "#if ! && (TARGET_OS_IOS || TARGET_OS_IPHONE)" and corresponds to a case where the compiler error you get would be triggered.

To overcome that, you should either fix the value of ZAPPAR_METAL_SUPPORT in your Xcode project file, or add an explicit -DZAPPAR_METAL_SUPPORT=0 (or 1) compiler flag for the UnityFramework target.

P.S. Of course, add "-framework OpenGLES" in the Extra linker flags as instructed, and make sure the ZCV.bundle directory is embedded in the final app (you can check that in the "build" subfolder by browsing to the compiled .app directory, if it's not there put it there with a pre-packaging script).

But please also note that the OpenGLES framework is deprecated by Apple : https://developer.apple.com/documentation/opengles
I'm not sure it's a good thing for a plugin to rely on deprecated features. It might as well just disappear from recent iOS SDKs.

append delete #2. billygunn

Thanks for the quick reply on a weekend!

I tried setting the value of ZAPPAR_METAL_SUPPORT to 1 as well as 0 and I got the following similar errors :

https://pmbaty.com/paste/?7962abf4a6152356#6aVzpSKHMVQdaxmr9QL2DQaNNQj5ZJN2NQoC68RjmezX

I even tried it with the explicit compiler flags with no luck as I am getting the same errors as the previous logs.

And the plugin does link to Metal and will use OpenGLES only if Metal is not supported (so iPhone 5 and below).

append delete #3. Pierre-Marie Baty

This 

%
#define ZAPPAR_METAL_SUPPORT=1 // Comment out this line if you _do not_ want to include support for Metal.
%

is not the right way of defining a preprocessor definition in C. The right way is : 

%
#define ZAPPAR_METAL_SUPPORT 1 // Comment out this line if you _do not_ want to include support for Metal.
%

Your source code is definitely buggy...

append delete #4. billygunn

Hi Pierre,

Hope you had a good weekend! I tried "#define ZAPPAR_METAL_SUPPORT 1" and now the build is completing which is a good sign.

However, the face tracking is not working as expected and I believe it is to do with the fact that the ZCV.bundle file is not getting pulled in as that is what contains the face tracking model.

I was trying out the suggestion from your first reply - "you can check that in the "build" subfolder by browsing to the compiled .app directory, if it's not there put it there with a pre-packaging script" and I noticed that even though I add the ZCV.bundle file to the .app folder, it gets deleted once the build it done.

What can be done to overcome this?

append delete #5. Pierre-Marie Baty

You can’t do it by hand. You need to use a pre-packaging script to embed the bundle directory in your app before it is sealed by a code signature. Please refer to the builder documentation to find out how to do it.

append delete #6. billygunn

Awesome! That worked after using the pre-packaging script. Thanks Pierre!

append delete #7. Pierre-Marie Baty

You’re welcome. Happy testing !

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty