Xcode 10 Command PhaseScriptExecution failed with a nonzero exit code (EXPANDED_CODE_SIGN_IDENTITY: unbound variable)

Question

This error pops up when doing Project > Test

/Users/.../Project/Pods/Target Support Files/Pods-Target/Pods-TargetTests-frameworks.sh:
line 104: EXPANDED_CODE_SIGN_IDENTITY: unbound variable
Command PhaseScriptExecution failed with a nonzero exit code

How do I resolve "Command PhaseScriptExecution failed with a nonzero exit code" error when trying to test a project with cocoapods?

Did you try Xcode 10 GM seed? Did you raise the issue on https://github.com/cocoapods/cocoapods/issues? What is a minimal Podfile that can reproduce your issue? — Cœur, Sep 13 '18 at 06:01
https://stackoverflow.com/questions/53289524/xcode-10-2-1-command-phasescriptexecution-failed-with-a-nonzero-exit-code/60090102#60090102 — Anurag Sharma, Feb 06 '20 at 08:07

Nuzhdin Vladimir · Accepted Answer · 2019-02-08T15:41:44.427

25

This helped me

sudo gem install cocoapods --pre
pod update

I've read BugReport. Problem was similar to mine and it was fixed in 1.6.0.beta.1 (2018-08-16) (changelog).

Updated(thanks to Cœur)

1.6.0 (2019-02-07) Was published

sudo gem update cocoapods

This should work now.

edited Feb 08 '19 at 15:41

answered Oct 05 '18 at 14:21

Nuzhdin Vladimir

1,714
18
36

1

Yeah, this fixed it for me. Kind of ridiculous that we need to use the beta release to avoid this issue. Hopefully they'll get the next stable release out quickly – sdailey Oct 19 '18 at 18:03
1

1.6.0 stable was released two days ago: no need to install a beta version of CocoaPods anymore: `sudo gem update cocoapods` is enough now. – Cœur Feb 08 '19 at 15:35
Before doing this laborious task try solution 3. Mines working for this. :) – elk_cloner Mar 27 '19 at 10:08
This helps to ignore code signing for pods, but the code signing of the main mac app also needs to disable. – Preetam Jadakar Jul 01 '19 at 07:35

score 21 · Answer 2 · answered Oct 14 '18 at 11:31

I have facing the same issue, i believe this issue have something link to keychain access too (code signing problem), I go to keychain access unlock the login then lock it again fixed this issue. After uploading toOSMojave and Xcode 10 keychain need to reverify the password. (how i find this? while facing same issue and trying all available option, i think to generate certificate again, but while generating private key i found keychain login user name and password is wrong type of message- i lock and unlock again solved my problem). Note this process required your login pass phare.

How to fix:- short tip

Go to keychain access -> right click on login -> lock & unlock again 
-> clear Xcode project and make build again.

Locking and unlocking the keychain fixed it for me. Either way, this fixes the issue with the password verification prompt. — Michael, Nov 18 '18 at 22:39

score 4 · Answer 3 · answered Sep 16 '18 at 10:44

4

Some Framework or SDK require Code Signing.

I done code signing and resolved the similar problem for me.

answered Sep 16 '18 at 10:44

Ashvin

8,227
3
36
53

yoAlex5 · Answer 4 · 2022-07-29T08:21:06.843

2

EXPANDED_CODE_SIGN_IDENTITY: unbound variable
Command PhaseScriptExecution failed with a nonzero exit code

I had the same problem after updating BuildSettings and Podfile

I just restarted Xcode and opened a workspace - .xcworkspace (not project - .xcodeproj)

[Workspace vs Project]

edited Jul 29 '22 at 08:21

answered Aug 02 '19 at 10:51

yoAlex5

29,217
8
193
205

Worked - I had the Project file open, not the Workspace... :/ – Dylan May 22 '20 at 09:44

score 1 · Answer 5 · answered Jun 12 '19 at 08:52

1

Go to pod folder and change the file as executable file. It works for me.

chmod +x filename

filename => your file name like "swiftlint"

answered Jun 12 '19 at 08:52

Balaji G

77
5

score 1 · Answer 6 · answered Nov 20 '19 at 10:44

1

On the top of - Pods-yourProjectName-frameworks.sh

export EXPANDED_CODE_SIGN_IDENTITY=""
export EXPANDED_CODE_SIGN_IDENTITY_NAME=""
export EXPANDED_PROVISIONING_PROFILE=""

this is an issue with pod update.

answered Nov 20 '19 at 10:44

Venu Gopal Tewari

5,672
42
41

This worked for me on Xcode 12 beta 2 (Catalina) with Cocoapods v1.5.2 ! Thank you! – Akshay Jul 11 '20 at 16:44

score 1 · Answer 7 · edited Feb 11 '20 at 23:22

1

I had the same problem and could solve it, by just renaming the project. In my case this error was, because I had a ' symbol in my project name.

edited Feb 11 '20 at 23:22

Twenty

5,234
4
32
67

answered Feb 11 '20 at 22:56

Vlad Antonov

166
1
8

score 1 · Answer 8 · answered Mar 09 '20 at 05:20

1

Delete the Pods directory and the Podfile.lock file.
Run pod install to re-create them from scratch.
Clean the Xcode project.
Build the Xcode project.

answered Mar 09 '20 at 05:20

Andrew Koster

1,550
1
21
31

score 1 · Answer 9 · answered Jan 05 '22 at 20:02

If you're on an M1/Apple Silicon Mac, make sure you have your Excluded Architectures set up properly. I don't know why this is necessary, but here's how you do it:

Go to Build Settings
Make sure you view "All" (default is "Basic")
Expand "Excluded Architectures"
Under debug, select Any iOS Simulator SDK, and add a value for "arm64"

Do the above settings for each relevant target, in my case I have "Pods", "Project", and then the iOS target.

score 0 · Answer 10 · answered Nov 12 '18 at 21:04

0

Well, a simplepod install worked for me :)

answered Nov 12 '18 at 21:04

Alejandro Vargas

1,327
12
26

Evelyne Sütő · Answer 11 · 2019-01-16T15:15:00.797

I've had the same problem. It turns out that by switching between Xcode9 and Xcode10 sometimes it can happen that the command line tools used for building can be switched so I was trying to build it with 9.4 command line tool instead of 10 which caused the issue.

Going to preferences and setting the command line tool to the right one fixed the issue for me.

Another thing that helped me is to disable and enable iCloud again. (Not sure why.)

score 0 · Answer 12 · answered Apr 17 '19 at 16:44

Ive been dealing with this issue for a couple of days now. What did it for me was.

-Update cocoapods to the last version
-Update all pods
-Opening keychain access and delete the key made by xcode (with xcode closed)
-Opening Xcode will recreate a new key and will ask you for the password.
-After this I cleaned and built and the application ran on my physical device.

I hope this is helpful since its a very annoying bug.!

score 0 · Answer 13 · answered Jan 29 '21 at 09:06

0

Restarting the mac helped me,not the xcode.

answered Jan 29 '21 at 09:06

SHINTO JOSEPH

377
4
17

score 0 · Answer 14 · answered Mar 23 '21 at 17:22

0

Check the issue clearly, if it is related to swiftlint.yml then this hidden file must be present in your directory. If you are working on more than one module then you can copy and paste it from your other modules if any.

answered Mar 23 '21 at 17:22

Syed Hussaini

11
2

score 0 · Answer 15 · answered Jan 08 '22 at 14:11

0

nvm alias default 16.6.0 if you want it pegged to that specific version.

You can also do nvm alias default 16.

answered Jan 08 '22 at 14:11

Алексей Жук

1
1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 08 '22 at 15:54

score 0 · Answer 16 · answered Jun 02 '22 at 09:06

0

In My case, I tried many solutions but all in vain

Solution: I just do "Pod deintegrate" and then "pod install" then my project is working perfectly.

answered Jun 02 '22 at 09:06

Muhammad Usman

141
1
4

Xcode 10 Command PhaseScriptExecution failed with a nonzero exit code (EXPANDED_CODE_SIGN_IDENTITY: unbound variable)

16 Answers16

Linked