MapFileParser.sh: Permission denied - not set as executable in Unity 4.6.8p1

I just installed Unity 4.6.8p1 on PC, made a build, copied the build folder to my Mac, and when I build it I get

Shell Script Invocation Error....MapFileParser.sh: Permission denied

It seems the file isn't being set as executable, when I do a chmod +x on it, the build works.

 

Not sure, but this problem didn't happen in the previous Unity version that I had (that's how we make most of our builds here, build on PC, copy to Mac, build and push in Xcode)

 

What I was using before was 4.6.7p2. I'll submit a bug report but I can't include the project with it

 

Case #725127

 

I'm having the same problem. Can you explain how I do a chmod +x?

 

I'm having a similar problem, going to try the chmod command and see if it works. I also compiled on windows and sent to my mac

 

the chmod +x command worked for me!

 

This issue still exists in 5.3.5p7, I always have to manually set this permission in the terminal later if building xcode project on PC and moving files to Mac.

 

When I zip the files on PC, then copy to Mac, the unzip it, it seems to preserve all the permissions. This workaround works best for me and resolves the "Permission denied" error in XCode.

 

@erik_fonseka

You really helped me! Thanks!!

 

Set attributer read-write for all users and groups and all will be fixed

 

@PlayJoWee how do you do that? Can you give the steps. I am still learning the Apple ecosystem.

 

Sorry to necropost but this just occurred for me with 2017.3.0f3, and this was a top result in google.

The error appeared when i started pushing files FROM the windows machine onto a shared drive/folder on the mac .

I tried changing the file permissions on the files directly on the mac, and it still threw the error despite 'everyone' having read/write access.

The solution was to instead, go onto the mac, and pull the files off a windows network drive. Apparently when doing it this way the mac is able to set the file permissions properly.

 

If you hate the command line or can't use it for whatever reason you can usually have scripts run without -x (execute) permission by adding 'bash ' in front of the script under Build Phases>Run Script in XCode
i.e. bash "$PROJECT_DIR/MapFileParser.sh" should work

 

@JoshPeterson This just happened to me on 2018.10f2

• Xcode Project doesn't parse: When the project is build on windows, it generates a faulty shell command to mipfileparser. See here: https://stackoverflow.com/questions...e-project-from-unity#comment88073995_41680328
  
  
• MipFileParser can not be accessed (persmission error)
  

Would be great if you can sort it out.

We use a dropbox account to sync the build artefacts; which by the way, is the most reliable way to not run into permission madness with windows network sharing and ensure everything is in sync blazingly fast as dropbox will snyc over LAN, when the machine with differences are in the same local network. This also syncs permissions. So on your mac, go into your ios-build folder in dropbox and run once

sudo chmod -R 777 .

This will set all permissions of all files and sync it back to the windows machines via dropbox; respecting now the set permissions.

Do use version control for your unity project though!

 

I am on vacation now and can not submit stuff

 

@scheidtventureestate thank you for the fix.

@JoshPeterson has there been any progress on this? Im running the latest IDE, building iOS from Windows to an OSX shared drive and hitting the same issue.

 

[QUOTE = "gracezhu, post: 3500644, member: 1790438"] Nếu bạn ghét dòng lệnh hoặc không thể sử dụng nó vì bất kỳ lý do gì bạn thường có thể chạy các script mà không cần sự cho phép -x (thực thi) bằng cách thêm 'bash' vào trước của tập lệnh trong Tạo giai đoạn> Chạy tập lệnh trong XCode
tức là bash "$ PROJECT_DIR / MapFileParser.sh" sẽ hoạt động [/ QUOTE]
thank you!!!

 

Showing All Messages
/Users/faisalmumtaz/Library/Developer/Xcode/DerivedData/Unity-iPhone-aqzssptynwseuecmulzbxmtwdxoc/Build/Intermediates.noindex/Unity-iPhone.build/ReleaseForRunning-iphoneos/Unity-iPhone.build/Script-033966F41B18B03000ECD701.sh: line 2: /Users/faisalmumtaz/Desktop/Shiekh zayed memorial/builds/IOS Project/Ios/MapFileParser.sh: Permission denied


NEED help i m using xcode9.4

 

reported as a bug. Aware there are manual "work arounds" however, keen to see it fixed as it would be a huge productivity increase for me.

https://issuetracker.unity3d.com/is...rom-windows-directly-to-a-macos-shared-folder

 

This. Thanks alot!

 

There is a new issue with this in macOS Catalina with Xcode 10.3. First you get the permission denied, when setting +x it throws "MapFileParser.sh" can't be opened because it's integrity cannot be verified.

 

That works for me too. Just a note; don't use 7z format but use zip format, as zip format does store fat type permissions, while 7z does not.

* at windows, compress Xcode project folder as zip format (LZMA method compresses better than deflate method)
* at mac, unzip it with The Unarchiver

(Windows 10 / Unity 2019.2.2, macos high sierra 10.13.6 / Xcode 10.1)

 

You can run the command man chmod for more details about chmod, but you should be able to run this command on the OSX machine:

chmod a+x /path/to/MapFileParser

dont forget to restart X code again as well "a+x"..

It works for me.......

 

This solution worked for me on version 2018.4.13f1

 

This started happening for us recently when building on a Catalina iMac. We always use zip files when moving from Windows anyway. The error appears for MapFileParser.sh and then for process_symbols.sh.

The above works by recursively applying a+x to all files in the current folder (replace . with the folder if you wish) but it's annoying to have to do this all the time. Not sure if anything can be done on Unity's end, though.

 

This works for me! Thanks

 

We exported out on Windows via zip and copied over to a Mac using Catalina. At first used the default Archive Utility and this issue happened. Found this and used the Unarchiver and works fine.

 

@retox Ya using Unarchiver was the key for me. Downloadable in the Apple Store for free. Didn't have to change any permissions.

 

Hi!
For me the solution was:
1) Set permission running chmod +x command for "MapFileParser.sh"
2) In "MapFileParser.sh" replace the first line from

#!/bin/sh

to

#!/bin/bash

 

I ended up creating a .command script which I'm always running before opening the project on OSX (Open with->Terminal):

Code (CSharp):

1.         void CreateFixIOSBuildScriptsCommandFile(BuildReport report)
2.         {
3.             var filePath = report.summary.outputPath + "/runme_fix_permissions.command";
4.  
5.             File.WriteAllText(
6.                 filePath,
7.                 "# This fixes errors where Xcode couldn't execute these scripts" + "\n" +
8.  
9.                 // Needed because current directory is not set when running .command files. gearsdigital's life-saving comment on this SO answer: https://stackoverflow.com/a/9650209
10.                 "cd \"`dirname \"$0\"`\"" + "\n" +
11.  
12.                 "chmod a+x MapFileParser.sh" + "\n" +
13.                 "chmod a+x process_symbols.sh"
14.             );
15.         }

Add it to your post-build event in Unity.
For ex:

Code (CSharp):

1. using UnityEditor;
2. using UnityEditor.Build;
3. using UnityEditor.Build.Reporting;
4. #if UNITY_IOS
5. using UnityEditor.iOS.Xcode;
6. #endif
7.  
8. namespace YourNamespace
9. {
10.     public class PostprocessBuildUtility : IPostprocessBuildWithReport
11.     {
12.         int IOrderedCallback.callbackOrder { get { return 10000; } }
13.  
14.         void IPostprocessBuildWithReport.OnPostprocessBuild(BuildReport report)
15.         {
16.             if (report.summary.result != BuildResult.Succeeded && report.summary.result != BuildResult.Unknown)
17.                 return;
18.             ManageIOSPostBuild(report);
19.         }
20.  
21.         void ManageIOSPostBuild(BuildReport report)
22.         {
23. #if UNITY_IOS
24.             if (report.summary.platform == BuildTarget.iOS) // Check if the build is for iOS
25.             {
26.                 .. some other code you may have here for managing the iOS build ..
27.  
28.                 // Simply create a .command file which can be run in OSX to fix some permissions
29.                 CreateFixIOSBuildScriptsCommandFile(report);
30.             }
31. #endif
32.         }
33.     }
34. }

Wish there could be something implemented by Unity that won't require us to do this.

Lucian

Edit 19.09.2021: New file needs permissions as well (I think in Unity 2020):

Code (CSharp):

1. chmod +x usymtool

 

Same problem again on unity 2019.4.1f1

 

This also hit me with the 2019.4.1f1 upgrade, however I believe the issue relates to installing from the command-line on macOS instead of with Unity Hub. I use the UnitySetup PowerShell tools to manage Unity installs, which internally install the package according to the Unity command-line instructions (i.e., using sudo installer) into a temporary volume, and then rsync's these files to the destination directory (this is necessary because the installer tool doesn't allow installation into arbitrary directories).

By contrast, Unity Hub directly extracts the .pkg with xar and tar, skipping the postinstall script within the .pkg.

Within the .tar file the permissions are correct, but somewhere during the installer process the execute bits on MapFileParser.sh are lost.

 

I have the drive mapped on my pc to the mac . I just copy the folder to it and am not archiving at all.

 

I zipped the iOS build file from PC and Unzipped in my mac. I set up command in terminal

(base) Name-MBP:~ UserNameMac$ chmod +x /path/to/MapFileParser

It is perfectly working on latest version of Unity 2019.4 and Xcode 11.5.

Note: Copy the path when you will go to the folder and right click the MapFileParser.sh file and then click "Copy MapFileParser.sh" option.

 

ATM I empty the folder on the MAC and copy the new xcode files into that and just do a chmod 777 *.sh as I leave the terminal window open along with xcode. But I am now going to try generating the xcode project directly to the macs drive via a share to the PC. If that works that will save me about 1.5 minutes in getting it there.

TRIED IT, that sucked still had to do the chmod 777 and lost the folder so the terminal folder was moot and had to change folders again.

 

Yes, its works for me!

 

For anyone else still facing this issue in Unity 2020, you can save the following script (attached also) to an Editor folder in your project and it will take care of setting the correct permissions when Xcode builds (you need to clean your Xcode project if built previous for this to take effect)

Code (CSharp):

1.  
2. using UnityEngine;
3. #if UNITY_EDITOR
4. using UnityEditor;
5. #endif
6. #if UNITY_IOS || UNITY_IPHONE
7. using UnityEditor.iOS.Xcode;
8. #endif
9. using UnityEditor.Callbacks;
10.  
11. public static class iOSBuildPermissionFix
12. {
13. #if UNITY_EDITOR && (UNITY_IOS || UNITY_IPHONE)
14.     [PostProcessBuild(0)]
15.     public static void OnPostProcessBuild(BuildTarget buildTarget, string path)
16.     {
17.         if (buildTarget != BuildTarget.iOS)
18.         {
19.             return;
20.         }
21.  
22.         string projectPath = PBXProject.GetPBXProjectPath(path); ;
23.         PBXProject pbxProject = new PBXProject();
24.         pbxProject.ReadFromFile(projectPath);
25.  
26.         string targetGUID = pbxProject.GetUnityFrameworkTargetGuid();
27.  
28.         string shellPath = "/bin/sh";
29.         int index = 0;
30.         string name = "Fix Permissions in Windows Generated XcodeProject";
31.         string shellScript = "chmod a+x \"$PROJECT_DIR/MapFileParser.sh\"";
32.         pbxProject.InsertShellScriptBuildPhase(index, targetGUID, name, shellPath, shellScript);
33.         pbxProject.WriteToFile(projectPath);
34.  
35.         Debug.Log("<color=green>iOS Build Permission Fix</color> Applied to XcodeProject");
36.     }
37. #endif
38. }
39.  

The key thing is that this needs to be applied to the Unity Framework Target Build Phases, not the Unity-iPhone one. Shown in orange below is the Run Script that tries to execute MapParser.sh, it would be nice if Unity could just add the chmod command themselves to that Run Script build phase

 

plz help!
i am getting this error

/Users/Arno/Library/Developer/Xcode/DerivedData/Unity-iPhone-bvktsxkdtsxzvdakehktvfqcltvp/Build/Intermediates.noindex/Unity-iPhone.build/ReleaseForRunning-iphoneos/UnityFramework.build/Script-9D3DC87A221D90AB00B2960B.sh: line 2: /Users/Arno/Downloads/XCode/MapFileParser.sh: Permission denied

 

#Unarchiever was the key THANK YOU SO MUCH )))))