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:
- The Accessibility Inspector is on
- UI Instrumented Testing
- VoiceOver for OSX is On (other ATs as well)
To get this to go away you should:
- Exit Accessibility Inspector (if it’s on)
- Open Simulator
- Hardware -> “Erase All Content and Settings”
- Re run application.
- Literally NEVER run this simulator with the Accessibility Inspector
- Literally NEVER run UI tests on this simulator, which also rely on the Accessibility Layer to do their work, though I don’t think doing so will cause the error to stick around until you “Erase all….” again, it will just be present for that test run.
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!