Error on installation about async HOT 20 CLOSED

<Notice>: 0x16e033000 -[MIExecutableBundle codeSigningInfoByValidatingResources:performingOnlineAuthorization:ignoringCachedSigningInfo:error:]: 534: Code signing identifier (Async-555549447c21a4d7a1673fddb94d5bd8c86929a3) does not match bundle identifier (Async) for /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.T0sw1F/extracted/Payload/MyApp.app/Frameworks/Async.framework

from async.

How are you installing the framework? And what version of Xcode?

from async.

carthage update --platform ios --no-use-binaries
Xcode Version 8.1 (8B62)

from async.

@cikpis
Did you try rm -rf Carthage/Checkouts/ before carthage update/build ?

from async.

I always remove the whole Carthage folder before doing the update command.

from async.

@cikpis
Hmm that's weird. 2.0.1 has been working fine in my environment. I tested both iOS and tvOS devices and it installs without problems.

from async.

No clue to be honest. But if I use the 2.0.0 version I have no problem. So I think is related with the 2.0.1 even because I saw you changed a lot of code in xproject file.

from async.

@cikpis
Yes, I admit that I changed a lot in #108 🙂. But keep in mind that 2.0.0 has #106 issue when built with Carthage.
If you stick with 2.0.0 for now, you can workaround it by setting CFBundleVersion value at Carthage/Build/iOS/Async.framework/Info.plist before archiving for submission.
I think that's fine, too.

But as I described in #108 , 2.0.0 has a problematic project structure for Carthage. So Carthage users should update to 2.0.1 asap.

Could you provide more info, so maybe we can debug it further?

• Did you cleaned your derived data?
• If building for a iOS Simulator, did you try recreating a new Simulator?
• If building for a device, did you try deleting your old app before install?
• Could you share your entire project or minimum sample project to reproduce?
• When does this issue reproduce? (Does it always on your machine, or in your specific app/library? Is it same on your colleagues' machines?)

Looks like it's a codesigining problem, so I believe there should be old cached data somewhere which is causing problem.
I googled the error message and found similar topics on SO, too.
http://stackoverflow.com/questions/34642165/this-applications-bundle-identifier-does-not-match-its-code-signing-identifier

from async.

Did you cleaned your derived data?
Yep

If building for a iOS Simulator, did you try recreating a new Simulator?
I'm using a device otherwise I couldn't find this problem :)

If building for a device, did you try deleting your old app before install?
Yep

Could you share your entire project or minimum sample project to reproduce?
Nope :)

When does this issue reproduce? (Does it always on your machine, or in your specific app/library? Is it same on your colleagues' machines?)
I tried in a couple and same problem in all.

from async.

I'm having the same problem. Works fine on the simulator but fails on the phone. Installed using carthage. Can remove the Async.framework from my project and everything works fine.

from async.

Interestingly, solved it by downloading the framework separately and building it and adding it in manually, so maybe more of a Carthage problem.

from async.

@moksamedia Thanks for providing info! I'm staring at the buildSetting.. Let me know if you get more info.

from async.

It turns out that INSTALL_PATH configuration has been missing since 2.0.1.
Since this issue reproduces only on devices, I'm guessing that copy-frameworks command is affected somehow.
I will investigate on this when I get time.

from async.

I still cannot reproduce by steps below 🤔:

• Create a new iOS app
• Add Async 2.0.0 via Carthage and install app on device (runs fine)
• Remove Carthage/, "derived directory", and installed app from device
• Update to Async 2.0.1 and install app on device (runs fine)

iOS10.2.1 iPhone 5
Xcode 8.2.1
Carthage 0.18.1

from async.

@cikpis @moksamedia
Could you share the carthage build log ?
Please make sure again that you use the latest version of Carthage, and also that xcode-select -p points at expected Xcode.app/ you use.

from async.

@toshi0383 still this is an issue. Any updated?

from async.

@cikpis Hi, sorry for late response.
I submitted #114.
Async's bundleId has been changed in 2.0.1, so it might affect code-signing.
I restored bundleId in the PR, so I'll be praying after merging.🙏

from async.

Oops, PR automatically closed this one.
Feel free to reopen if issue persists.

from async.

This issue may be related to using a custom fork of a repository as a dependency using carthage, @cikpis could you infirm/confirm my previous statement?

from async.

Sorry guys but I had to remove this library. I had too many problems. Cheers!

from async.