koobas.hobune.stream
MapFileParser not found in iOS Postprocessing
Hi,
I'm using Unity 5.1.0p1 Personal and I'm receiving the following error when I attempt to build my project for the xcode environment.
Please help.
Thank you! I was able to get my game working on the iPhone with your fix! I also submitted a bug fix.
Here is a temporal solution.
1.Go to "C:\Program Files\Unity\Editor\Data\Tools\MapFileParser"
2.Duplicate MapFileParser.exe
3.Rename the duplicated MapFileParser.exe to MapFileParser (Remove ".exe" extention)
4.You should be able to build your project in Unity ;)
5.(Optional: For iOS build)
In the same directory as (project name).xcodeproj file, you will see "MapFileParser".
Delete it before compiling the project in xcode. Otherwise you will get "Permission Denied" error.
I am also waiting for someone to find out better solution...
Thank you! This solved my problem for now, was able to build successfully and play on IPhone. Hopefully a more practical fix will emerge soon!**
Well, if that fixes the error it's clearly a bug in Unity. So please make sure you file a bugreport.
Thanks, yuukive! That fixed the error on my iOS builds!
I've submitted a bug for it, on July 7th, 2015. I wonder how long it will take for them to fix it. Should take precedence
This is actually not specific answer for your question but a followup. When you try to build in xCODE, you might get an error saying:
Shell Script Invocation Error....MapFileParser.sh: Permission denied
if so, open Terminal -> Locate the folder of MapFileParser.sh and type -> chmod +x MapFileParser.sh
Solution came from here: http://forum.unity3d.com/threads/mapfileparser-sh-permission-denied-not-set-as-executable-in-unity-4-6-8p1.352136/
I think this occurs mostly when you copy and iOS build from a PC to a MAC.
Hi. In 2020 I'm facing the same problem... I'm pretty new in mac, I'm sharing mac from "$$anonymous$$acinCloud", so I'm not an ad$$anonymous$$, just a user. I'm trying to use your solution but I not sure how to use chomod. Can you tell me what I'm doing wrong?
Actually, the latest Unity3d no longer has this issue! I have latest Unity3d with latest xcode installed.
