(You also end up needing to play around with xcode-select and related tools to do CLI stuff with the Xcode related tools.) You just have to make sure that any builds for submission are done using the production Xcode. I usually do that in the periods like right now where the transitions are happening. If you want to check if the issue is still there using the betas of Xcode, you can have both the production version and the beta installed at the same time. But, that might help narrow down the source of the issue and if it might end up being an actual problem. This particular library conflict seems to be related to building on M1 based machines, but that could be misleading again. If you really want to track it down or feel like it might eventually cause a problem in your own project, I'd try seeing if it happens for builds for all platform/architectures. You could report the error to Apple like suggested in the one thread - but I think we all have a feel for what good that would do. If the build is failing, look for a different cause of the failure. I'd probably ignore the warning if the build is working. Lots and lots of these types of threads relating to Dart/Flutter projects where the build fails for an unrelated reason but this is the last build warning that is seen before the build fails. The way the command line tools report back warnings in the build process makes it look like this warning is the issue in failed builds where the real issue is totally unrelated. The problem with getting decent hits is that almost everything is actually unrelated to the warning. I tried to do a web search for this warning. The other thing that can make it difficult to trace these types of problems is that the library location that's reported could be in a sandbox that you can't directly see unless you take the time to search around through APFS mounts and locations in the caches in ~/Library. This would be even more likely to be true in projects with cross-compilation. The reported location of the conflicting libraries could be in a framework, not the actual machine. Objc: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1fe3afb28) and /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice (0x115f6c308). Objc: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1fe3afad8) and /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice (0x115f6c2b8). I can ente rmy Home-Dir, that is not even a git directory and just issue 'git': mini:~ tja$ git Īnd no, it has nothing to do the with actual project! I could understand the situation with some wild library that got installed wrongly or something, but one of the two logged libraries does not even exist! I have Homebrew not installed, but instead Mac Ports. I installed Xcode from the App Store, as the dummy I am :-) The error never caused the project not to work, but it is troubling to see.Īre you on the beta of Xcode or the current release? I have had this type of conflict with some demo projects I've looked at. I have no idea if this is a reliable piece of info though. I saw some people mentioning a link between this particular library conflict and having Homebrew installed. The person that replied to this question is generally knowledgable on dev related issues. But, there is this thread (very short) at the dev forums: It could be a configuration error in the project. It seems that I would need to remove one of those files or said: Googling around did not help much, pointing mostly to Flutter, which I don't have installed.Īnybody has an idea what could cause such messages? Objc: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1ec6e7b28) and /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice (0x1161a8308). Which one is undefined.Īfter that, I ran 'xcodebuild' and got exactly the same error message: objc: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1ec6e7ad8) and /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice (0x1161a82b8). Objc: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1ec6e7b28) and /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice (0x115ddc308). ' on some github repository and got the following messages: objc: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libauthinstall.dylib (0x1ec6e7ad8) and /System/Library/PrivateFrameworks/amework/Versions/A/MobileDevice (0x115ddc2b8).

Big sur uninstall xcode