iOS Build Environment Help Center

Including UnityEditor.iOS.Xcode libraries

append delete Justin DuPont

Windows version: 11
Builder Version: 3.54
iOS SDK version: 16.2

Hello! I just posted, but this is a completely different topic. (Where these frameworks are not yet included in the project)

In my app, I am trying to use the CoreHaptics Apple framework. However, right now when I include these frameworks in the project manager, apparently they have some dependencies in UnityEditor.iOS.Xcode. I get errors and can't compile, which I can share if needed. These errors also do not appear when I am working in Unity on Mac.

I understand I can add frameworks later in the build step after the XCode project has been built, but how can I include these libraries in Unity so that I can call these haptic methods in visual studios without getting errors?

I greatly appreciate you responding to my multiple questions! Thank you!!

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

Yes, please share the errors you have. Are these errors during the construction of the Xcode project by Unity or during compilation with the builder ?

append delete #2. Justin DuPont

Here is a link to the errors in Unity:

https://imgur.com/a/iW9SXsy

I followed Apple's instructions on how to build and install their new unity libraries, in this case Apple Core and Apple Haptics. With the last step to import the library from tarball in the package manager.

And when the scripts try to compile (to even just enter play mode), I get these errors in console. I looked where the namespaces they claim to be missing come from, and they appear to be a part of UnityEditor.iOS.Xcode (for example you can look up 'plistdocument'.

append delete #3. Pierre-Marie Baty

Hmm. It might be that, Xcode being unavailable on Windows, you won't be able to do that with the Windows version of the Unity editor because it's looking for something that isn't there.

What might work, however, would be that you migrate your project to a Mac (typically the one from which you took your iOS SDK), do your project setup there with CoreHaptics once, then migrate the Unity project back to Windows. After all, you need to do this setup just once ?

Let me know if it did it.

append delete #4. Justin DuPont

Unfortunately I already tried this. I could use the core haptics libraries on my Macbook, but when I pushed the changes to git and tried to work on the project on my windows computer, I started to get these errors.

Do you think there is a way to copy/port over the libraries the unity engine is using? Even if its a bit "hacky"

append delete #5. Justin DuPont

After more research, it looks like this is actually a problem with the unity ios build module, as including this module on paper should solve the problem.

I'll do more research to see if I can find anything and let you know.

append delete #6. Justin DuPont

I actually found the solution to this. One of the Apple Core scripts was missing a UnityEngine.iOS.Xcode include statement at the top.

Thank you for the help!

append delete #7. Pierre-Marie Baty

You're welcome. Could you post here the details of what you've found so that others can benefit of it ?

append delete #8. Justin DuPont

Sure!

So if you import the Apple Core plugin, you have to make sure you have the iOS plugin for Unity installed. Then, in

com.apple.unityplugin.corehaptics@e5a20a3c2d88\Editor\CHBuildStep.cs

You have to add

“Using UnityEditor.iOS.Xcode”

to the top of the script. This should resolve all of the unity errors.

Hope this helps anyone who runs into this issue!

append delete #9. Pierre-Marie Baty

Thanks a lot !

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