Reputation: 58129
While running my project (which doesn't even use MapKit
), my console gets spammed with more than a hundred class duplicate warnings:
objc[6377]: Class ___MKPlaceBusinessInfoItemAccessibility_super is implemented in both /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/AccessibilityBundles/MapKit.axbundle/MapKit (0x12f128f00) and /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/AccessibilityBundles/VectorKit.axbundle/VectorKit (0x12f2187b0). One of the two will be used. Which one is undefined.
These warnings were not present with Xcode 9.0.0, I am only experiencing this on Xcode 9.0.1 and above.
I am aware that this is a bug and I found a radar that is about this issue. Is there a way to silence these warnings without affecting the visibility of other SDK warnings?
Upvotes: 46
Views: 6751
Reputation: 18900
This is actually a bug in the current iOS Framework and has nothing to do with anything in your app, module cache, libraries, etc. The reason this appears to be non deterministic is that it is only there when the Accessibility Layer is active, which it isn't on the simulator, except under very specific circumstances. The three I'm aware of:
To get this to go away you should:
Every time you do one of those last two bullet points, you will have to clear the data again...
The core issue is that MapKit and VectorKit both link to core accessibility bundles, but apparently have not done so dynamically, so those bundles are included in both modules. Such warnings are very safely ignored, though very verbose and frustrating.
Unfortunately there is no other fix for this... maybe you could download an old version of the simulator if you don't need iOS 11 features. Or just don't run instrumented tests/Accessibility Inspector/VoiceOver/I HOPE THEY FIX THIS SOON!
Upvotes: 28
Reputation: 5202
As you can see, there's something wrong with CoreSimulator
of /Applications/Xcode.app
. Apple Xcode Developer defined this symbol in both MapKit
and VectorKit
, which is the fundamental error.
You cannot modify Xcode, so only Apple's Staff can solve it.
Just stop wasting your time, except falling back to Xcode 9.0
Upvotes: 1
Reputation: 1
My case is a bit different: I met this issue while running XCUITest. After launching the XCUITest process, the target app crashes upon launch. However, after I removed all the Web proxies, this issue is fixed!
Upvotes: 0
Reputation: 3597
I don't give a damn about accessibility in the simulator so I just renamed one of the duplicate files so it wouldn't be found:
mv /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/AccessibilityBundles/MapKit.axbundle/MapKit /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/AccessibilityBundles/MapKit.axbundle/MapKit_
lol
Upvotes: 4
Reputation: 11
Exactly the same problem, in my case, I tried to delete all the files in DerivedData folder, but still not work.
And later I found that if I switch to another kind of simulator, for instance, switch from 'iPhone 8' to 'iPhone 8 plus', the warning would disappear.
So, simply delete the 'iPhone 8' simulator from simulator list, and then add the 'iPhone 8' simulator again, it works.
Not sure if the problem will come again, since it's also my third time dealing with this.
Upvotes: 1
Reputation: 31
Resetting the iOS simulator fixed this for me. Simulator -> Hardware -> Erase All Content and Settings...
Upvotes: 2
Reputation: 9
Solved!
-On simulator --Hardware ----Erase all content and settings -Close xcode and simulators -remove the content of ~/Library/Developer/Xcode/DerivedData/ModuleCache -Start xcode...
Upvotes: 0
Reputation: 389
Got the same issue on 9.0.1.
rm -rf ~/Library/Developer/Xcode/DerivedData/ModuleCache
. This issue was solved for me.
Upvotes: 10