Codesign keychain issues after data migration: “The specified item could not be found in the keychain.”





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I recently got a new Macbook Pro and migrated my old data to it. Since then, Xcode refuses to build on a physical device. The simulator works fine (since I don't think it requires code signing).



The error I receive is this: "The specified item could not be found in the keychain."



This happens even when I create a blank project and try to run it. The full error:




Codesigning
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
/usr/bin/codesign --force --sign
4FF2B0CA211948E47F41C112A5AD1FE24410A574 --verbose
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
error: The specified item could not be found in the keychain.




I realize it's an error with codesigning. Running "security find-identity -p codesigning" returns 0 identities.



Things I've tried that don't fix the issue:




  • Deleting the "login" keychain and creating a new one

  • Deleting derived data, cleaning build folder, restarting, etc.

  • Using Fastlane to "nuke" all my certificates and provisioning profiles and start over

  • Manually moving new certificates and provisioning profiles into Xcode

  • Using "--deep" on codesign inside the Cocoapods .sh script

  • Restoring my keychain from a time machine backup

  • Running this command


I've spent the past day reading every thread on this and it seems to be an issue related to migrating an old keychain to a new mac. The only "fix" I've seen is reformatting the drive and reinstalling OS X, which I would love to avoid (I also do audio work and this creates a literal week's work to track down and reinstall all my old Audio Units and apps).



If there were some solution like deleting the system keychain and starting over, or somehow getting it to recognize my new mac, or creating a new codesigning identity, that would be ideal. I realize that my understanding of the interaction between codesign and keychain may be limited, but I've tried all the articles on Keychain troubleshooting and thus far nothing has worked.










share|improve this question























  • Still unable to build anything on a device. I've been back and forth with Apple, who has asked for a bunch of screen shots and says everything should work. I'll wipe the system today and report back after.

    – bencollins
    Jan 16 at 17:02


















0















I recently got a new Macbook Pro and migrated my old data to it. Since then, Xcode refuses to build on a physical device. The simulator works fine (since I don't think it requires code signing).



The error I receive is this: "The specified item could not be found in the keychain."



This happens even when I create a blank project and try to run it. The full error:




Codesigning
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
/usr/bin/codesign --force --sign
4FF2B0CA211948E47F41C112A5AD1FE24410A574 --verbose
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
error: The specified item could not be found in the keychain.




I realize it's an error with codesigning. Running "security find-identity -p codesigning" returns 0 identities.



Things I've tried that don't fix the issue:




  • Deleting the "login" keychain and creating a new one

  • Deleting derived data, cleaning build folder, restarting, etc.

  • Using Fastlane to "nuke" all my certificates and provisioning profiles and start over

  • Manually moving new certificates and provisioning profiles into Xcode

  • Using "--deep" on codesign inside the Cocoapods .sh script

  • Restoring my keychain from a time machine backup

  • Running this command


I've spent the past day reading every thread on this and it seems to be an issue related to migrating an old keychain to a new mac. The only "fix" I've seen is reformatting the drive and reinstalling OS X, which I would love to avoid (I also do audio work and this creates a literal week's work to track down and reinstall all my old Audio Units and apps).



If there were some solution like deleting the system keychain and starting over, or somehow getting it to recognize my new mac, or creating a new codesigning identity, that would be ideal. I realize that my understanding of the interaction between codesign and keychain may be limited, but I've tried all the articles on Keychain troubleshooting and thus far nothing has worked.










share|improve this question























  • Still unable to build anything on a device. I've been back and forth with Apple, who has asked for a bunch of screen shots and says everything should work. I'll wipe the system today and report back after.

    – bencollins
    Jan 16 at 17:02














0












0








0








I recently got a new Macbook Pro and migrated my old data to it. Since then, Xcode refuses to build on a physical device. The simulator works fine (since I don't think it requires code signing).



The error I receive is this: "The specified item could not be found in the keychain."



This happens even when I create a blank project and try to run it. The full error:




Codesigning
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
/usr/bin/codesign --force --sign
4FF2B0CA211948E47F41C112A5AD1FE24410A574 --verbose
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
error: The specified item could not be found in the keychain.




I realize it's an error with codesigning. Running "security find-identity -p codesigning" returns 0 identities.



Things I've tried that don't fix the issue:




  • Deleting the "login" keychain and creating a new one

  • Deleting derived data, cleaning build folder, restarting, etc.

  • Using Fastlane to "nuke" all my certificates and provisioning profiles and start over

  • Manually moving new certificates and provisioning profiles into Xcode

  • Using "--deep" on codesign inside the Cocoapods .sh script

  • Restoring my keychain from a time machine backup

  • Running this command


I've spent the past day reading every thread on this and it seems to be an issue related to migrating an old keychain to a new mac. The only "fix" I've seen is reformatting the drive and reinstalling OS X, which I would love to avoid (I also do audio work and this creates a literal week's work to track down and reinstall all my old Audio Units and apps).



If there were some solution like deleting the system keychain and starting over, or somehow getting it to recognize my new mac, or creating a new codesigning identity, that would be ideal. I realize that my understanding of the interaction between codesign and keychain may be limited, but I've tried all the articles on Keychain troubleshooting and thus far nothing has worked.










share|improve this question














I recently got a new Macbook Pro and migrated my old data to it. Since then, Xcode refuses to build on a physical device. The simulator works fine (since I don't think it requires code signing).



The error I receive is this: "The specified item could not be found in the keychain."



This happens even when I create a blank project and try to run it. The full error:




Codesigning
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
/usr/bin/codesign --force --sign
4FF2B0CA211948E47F41C112A5AD1FE24410A574 --verbose
/Users/bencollins/Library/Developer/Xcode/DerivedData/blank-adueeinllraqwwavbsxjkxivjbde/Build/Products/Debug-iphoneos/blank.app/Frameworks/libswiftCore.dylib
error: The specified item could not be found in the keychain.




I realize it's an error with codesigning. Running "security find-identity -p codesigning" returns 0 identities.



Things I've tried that don't fix the issue:




  • Deleting the "login" keychain and creating a new one

  • Deleting derived data, cleaning build folder, restarting, etc.

  • Using Fastlane to "nuke" all my certificates and provisioning profiles and start over

  • Manually moving new certificates and provisioning profiles into Xcode

  • Using "--deep" on codesign inside the Cocoapods .sh script

  • Restoring my keychain from a time machine backup

  • Running this command


I've spent the past day reading every thread on this and it seems to be an issue related to migrating an old keychain to a new mac. The only "fix" I've seen is reformatting the drive and reinstalling OS X, which I would love to avoid (I also do audio work and this creates a literal week's work to track down and reinstall all my old Audio Units and apps).



If there were some solution like deleting the system keychain and starting over, or somehow getting it to recognize my new mac, or creating a new codesigning identity, that would be ideal. I realize that my understanding of the interaction between codesign and keychain may be limited, but I've tried all the articles on Keychain troubleshooting and thus far nothing has worked.







swift xcode macos migration codesign






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 3 at 13:11









bencollinsbencollins

21126




21126













  • Still unable to build anything on a device. I've been back and forth with Apple, who has asked for a bunch of screen shots and says everything should work. I'll wipe the system today and report back after.

    – bencollins
    Jan 16 at 17:02



















  • Still unable to build anything on a device. I've been back and forth with Apple, who has asked for a bunch of screen shots and says everything should work. I'll wipe the system today and report back after.

    – bencollins
    Jan 16 at 17:02

















Still unable to build anything on a device. I've been back and forth with Apple, who has asked for a bunch of screen shots and says everything should work. I'll wipe the system today and report back after.

– bencollins
Jan 16 at 17:02





Still unable to build anything on a device. I've been back and forth with Apple, who has asked for a bunch of screen shots and says everything should work. I'll wipe the system today and report back after.

– bencollins
Jan 16 at 17:02












1 Answer
1






active

oldest

votes


















1














I had the same issue. And I fixed it.



I had yubikey (https://en.wikipedia.org/wiki/YubiKey) in my mac and after removing it from mac all became to work as before.






share|improve this answer
























  • Thanks! I don't believe I have that installed.. I'll keep exploring.

    – bencollins
    Jan 4 at 12:28











  • YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

    – Ales Teska
    Apr 4 at 18:54












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54022972%2fcodesign-keychain-issues-after-data-migration-the-specified-item-could-not-be%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














I had the same issue. And I fixed it.



I had yubikey (https://en.wikipedia.org/wiki/YubiKey) in my mac and after removing it from mac all became to work as before.






share|improve this answer
























  • Thanks! I don't believe I have that installed.. I'll keep exploring.

    – bencollins
    Jan 4 at 12:28











  • YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

    – Ales Teska
    Apr 4 at 18:54
















1














I had the same issue. And I fixed it.



I had yubikey (https://en.wikipedia.org/wiki/YubiKey) in my mac and after removing it from mac all became to work as before.






share|improve this answer
























  • Thanks! I don't believe I have that installed.. I'll keep exploring.

    – bencollins
    Jan 4 at 12:28











  • YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

    – Ales Teska
    Apr 4 at 18:54














1












1








1







I had the same issue. And I fixed it.



I had yubikey (https://en.wikipedia.org/wiki/YubiKey) in my mac and after removing it from mac all became to work as before.






share|improve this answer













I had the same issue. And I fixed it.



I had yubikey (https://en.wikipedia.org/wiki/YubiKey) in my mac and after removing it from mac all became to work as before.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 4 at 11:51









Kirill AveryanovKirill Averyanov

1613




1613













  • Thanks! I don't believe I have that installed.. I'll keep exploring.

    – bencollins
    Jan 4 at 12:28











  • YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

    – Ales Teska
    Apr 4 at 18:54



















  • Thanks! I don't believe I have that installed.. I'll keep exploring.

    – bencollins
    Jan 4 at 12:28











  • YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

    – Ales Teska
    Apr 4 at 18:54

















Thanks! I don't believe I have that installed.. I'll keep exploring.

– bencollins
Jan 4 at 12:28





Thanks! I don't believe I have that installed.. I'll keep exploring.

– bencollins
Jan 4 at 12:28













YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

– Ales Teska
Apr 4 at 18:54





YubiKey is indeed the cause of this for me ... it is because YubiKey add an entry to a Apple Keychain.

– Ales Teska
Apr 4 at 18:54




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54022972%2fcodesign-keychain-issues-after-data-migration-the-specified-item-could-not-be%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

How to fix TextFormField cause rebuild widget in Flutter

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith