Alamofire: example.app/Frameworks/Alamofire.framework: unknown error -1=ffffffffffffffff Command /bin/sh failed with exit code 1

[panduranga2016]

ℹ Please fill out this template when filing an issue.
All lines beginning with an ℹ symbol instruct you with what info we expect. You can delete those lines once you've filled in the info.

Per our *CONTRIBUTING guidelines, we use GitHub for
bugs and feature requests, not general support. Other issues should be opened on Stack Overflow with the tag alamofire.

Please remove this line and everything above it before submitting.

• [ ] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

What did you do?

ℹ Please replace this with what you did.

What did you expect to happen?

ℹ Please replace this with what you expected to happen.

What happened instead?

ℹ Please replace this with of what happened instead.

Alamofire Environment

Alamofire version: 4.5.1
Xcode version: 9.1
Swift version: 4
Platform(s) running Alamofire: iOS 9.0
macOS version running Xcode: Mac O.S. Sierra 10.12.6

Demo Project

ℹ Please link to or upload a project we can download that reproduces the issue.

[tadas-subonis]

@panduranga2016 What was the problem?

[tadas-subonis]

@panduranga2016 What was the solution?

[tadas-subonis]

You must be joking.

On Wed, Dec 13, 2017 at 11:23 AM, Pandu Ranga Mallipudi <
[email protected]> wrote:

Send your project. I will clear the issue.

On 13 Dec 2017 14:56, "Tadas Šubonis" [e-mail] wrote:

@panduranga2016 https://github.com/panduranga2016 What was the
solution?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
issuecomment-351333024>,
or mute the thread
AXlYGHYRYVM5XOBGO9zlF0XOiTqMnytpks5s_5hCgaJpZM4QtH6r>

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Alamofire/Alamofire/issues/2369#issuecomment-351348301,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPFssOL-Ccz6j2IW8K0zuZBjhyJBp8yks5s_6WdgaJpZM4QtH6r
.

--

Kind Regards,
Tadas Šubonis

[tadas-subonis]

To whoever else stumbles on this issue - the problem was with keychain use through SSH. I had to execute these in my session to fix it:

security unlock-keychain -p MY_PASS~/Library/Keychains/login.keychain
security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k MY_PASS ~/Library/Keychains/login.keychain
security set-keychain-settings ~/Library/Keychains/login.keychain

I've also removed my current certificates system/account certificates by removing my account from XCode (I use fastlane to do building) but I suspect that this shouldn't have impacted it.

[panduranga2016]

Have you resolved the problem?

On Thu, Dec 14, 2017 at 1:29 PM, Tadas Šubonis [e-mail]
wrote:

To whoever else stumbles on this issue - the problem was with keychain use
through SSH. I had to execute these in my session to fix it:

security unlock-keychain -p MY_PASS~/Library/Keychains/login.keychain
security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k MY_PASS ~/Library/Keychains/login.keychain
security set-keychain-settings ~/Library/Keychains/login.keychain

I've also removed my current certificates system/account certificates by
removing my account from XCode (I use fastlane to do building) but I
suspect that this shouldn't have impacted it.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Alamofire/Alamofire/issues/2369#issuecomment-351635704,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXlYGCkweT74qt-hGE-oOHxJsIsx30Soks5tANVkgaJpZM4QtH6r
.