Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] [iOS] Remote build fails to Sign ipa correctly and fails the build. (With solution)

So recently we've updated to 4.11 preview 5, and I was having issues signing a build ipa.

I was getting the following:

 1>      /usr/bin/codesign --force --sign 9A94A149A6AAAC1AE7163D6C26A767484ECE66AF --resource-rules=Submerged/Binaries/IOS/Payload/Submerged.app/CustomResourceRules.plist --entitlements Submerged/Intermediate/IOS/build/UE4_FromPC.build/Development-iphoneos/Submerged\ -\ iOS.build/Submerged.app.xcent --timestamp=none Submerged/Binaries/IOS/Payload/Submerged.app
 1>EXEC : warning : --resource-rules has been deprecated in Mac OS X >= 10.10!
 1>  Submerged/Binaries/IOS/Payload/Submerged.app: replacing existing signature
 1>  Submerged/Binaries/IOS/Payload/Submerged.app: User interaction is not allowed.
 1>  Command /usr/bin/codesign failed with exit code 1
 1>  ** BUILD FAILED **
 1>  The following build commands failed:
 1>      CodeSign Submerged/Binaries/IOS/Payload/Submerged.app
 1>  (1 failure)
 1>  Execute took 00:00:05.2573007
 1>EXEC : IPP error : RPCCommand MakeApp failed with return code Error_RemoteCertificatesNotFound

the issue being the "User interaction is not allowed" where it's attempting to show the Keychain access Allow dialog.

I was able to find a solution in the following SO answer:


Setting allow all access to the certificate is a good stop-gap measure, however it would be nice if the unlocking of the keychain was part of the build process.

something like:

 security -v unlock-keychain -p "$KEYCHAIN_PASSWORD" "$HOME/Library/Keychains/login.keychain"

I'm mainly posting this as a note to others who may have the same issue later.

EXTRA: The other issue I ran into was the Signing certificate MUST live in the System keychain as well as the Login keychain to work correctly.

Product Version: UE 4.11 Preview
more ▼

asked Mar 23 '16 at 11:54 PM in Packaging & Deployment

avatar image

275 14 20 30

avatar image intoxicat3 Apr 01 '16 at 06:55 PM

Which of the link part was the solution?

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Aug 12 '16 at 02:11 PM by Steve Hardister for the following reason:

Problem is not reproducible or outdated

1 answer: sort voted first

The top answer was the solution I used.

This was on the System keychain copy of the certificate.

more ▼

answered Apr 04 '16 at 12:26 AM

avatar image

275 14 20 30

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question