Development on MacOS High Sierra

.

Thanks. Let me know if you need any additional information from me.

I'm having this problem as well. Same High Sierra, same error message. As the error message implies, I've installed (and reinstalled) `oculus_runtime_sdk_0.5.0.1_osx.dmg`.

Couldn't open /Users/sk/driftspace-big/editor/Assets/OVR/Plugins/1.19.0/OSXUniversal/OVRPlugin.bundle/Contents/MacOS/OVRPlugin, error: dlopen(/Users/sk/driftspace-big/editor/Assets/OVR/Plugins/1.19.0/OSXUniversal/OVRPlugin.bundle/Contents/MacOS/OVRPlugin, 2): Symbol not found: __dyld_get_all_image_infos
  Referenced from: /Users/sk/Library/Frameworks/LibOVRRT_0.framework/Versions/5/LibOVRRT_0
  Expected in: /usr/lib/libSystem.B.dylib
 in /Users/sk/Library/Frameworks/LibOVRRT_0.framework/Versions/5/LibOVRRT_0

Hello, 
I am having the same problem.
Any news about it?
Regards.

So basically you are saying that supporting GearVR builds on a mac is not a priority?

This is absurd. Apple changes one function to private in High Sierra and instead of fixing it your response is "There is no support for newer Mac OS releases currently." Ignoring every Gear VR developer using OS X.

Great job Oculus.

You guys understand that we aren't asking to be able to run a VR application with a DK1/2 on a mac, like we could way back when. Or even to have support like Vive/SteamVR with the latest Macs.

We just want to be able to hit Play in the Unity editor without the editor blowing up when a call to an OVR run-time function is made. You guys can literally just have every library function return null or some default data if the run-time can't be found - we just need your code to handle thrown exceptions when OVRManager can't access the run-time library so that it doesn't kill the entire function stack.

delphinius81 said:

You guys understand that we aren't asking to be able to run a VR application with a DK1/2 on a mac, like we could way back when. Or even to have support like Vive/SteamVR with the latest Macs.

We just want to be able to hit Play in the Unity editor without the editor blowing up when a call to an OVR run-time function is made. You guys can literally just have every library function return null or some default data if the run-time can't be found - we just need your code to handle thrown exceptions when OVRManager can't access the run-time library so that it doesn't kill the entire function stack.

Exactly this. It's ridiculous that we should have to add preprocessor directives just to prevent tons of errors at runtime.

Yeah any updates on this? If there is no change of thought, i would need to switch to the daydream platform. I'm not satisfied with this situation  :'(

Same issue here with Unity 2017.2.0p2 on High Sierra