Your next step is to take your project and begin building a test project out of it by reducing the code smaller and smaller iteratively to narrow in on why this is happening for only your app. The difference Is likely not something about the map view's configuration, but something else in your project that is influential on your app, such as any methods that are swizzled, or additional libraries that you're using that are altering the behavior of the system.
When creating such a test project, don't overthink it too much based on your existing knowledge of how your app works, go as fast as you can to remove significant code, make just enough changes to make it compile (such removing method bodies except for a single line that returns), and verify if the problem still exists or not. If it still exists, remove more things! If it doesn't, then you can look through the last removal and focus on narrowing what you removed there. By moving quickly here and not overthinking it, you can get down to the vicinity of the issue, especially when focused on things like swizzling and third-party libraries, quite reasonably.
— Ed Ford, DTS Engineer