Skip to main content
Participant
August 14, 2025

Meta files that fail on Mac due to hardcoded Windows-style path\filename

  • August 14, 2025
  • 2 replies
  • 116 views

Is there a maintained list of Meta UE source files (.cpp/.h) that hardcode Windows-style backslashes in file paths (e.g., path\filename instead of path/filename)? On macOS, those paths aren’t valid and have been breaking packaging/deployment (and sometimes Xcode builds) for me. I’ve confirmed at least two instances and suspect more. A complete inventory would let me verify whether this is the root cause of my Mac build/deploy failures and fix them efficiently.

This topic has been closed for replies.

2 replies

Participant
August 24, 2025

12 days, no response.   What else could be causing the shader issues I'm seeing. Is it possible to even run the META XR plugin when developing for the quest 3 on Mac? I'm now more than 40 days out of commission on this. 

 

VirtuallyARealDinosaur
Community Manager
September 10, 2025

Hello! There is no such list. We don't support Mac with the MetaXR plugin for Unreal or Meta Unreal Fork, however we do release the full source so that developers can perform their own query.