Failed to Load Optimized Model - Googlemaps Sdk iOS

Failed to load optimized model - GoogleMaps SDK IOS

If you have already double-checked the basic setup for the "google maps ios-sdk" with an APIkey for your app's bundle identifier here and still have the same problem then probably you have not enabled the google maps API. Go to your app-project's dashboard on https://console.developers.google.com and click the "ENABLE APIS AND SERVICES". There, under the MAPS section select "the Google maps sdk for ios" and enable it.

CoreData: annotation: Failed to load optimized model error on google map sdk iOS 11

This issue was reported in Google issue tracker:

https://issuetracker.google.com/issues/64504919

As I can see, the issue was marked as fixed today (October 24, 2017). The Google rep wrote

We believe that this issue should be solved in the Maps iOS SDK v2.5 release. If this issue still occurs, please let us know.

It looks like you have to update your SDK to the latest version 2.5 in order to solve the problem.

UPDATE

It looks like the issue wasn't solved in version 2.5, the bug was reopened in Google issue tracker.

CoreData: annotation: Failed to load optimized model at path 'Users/~/GoogleMaps.bundle/GMSCacheStorage.momd/StorageWithTileProto.omo'

I just spent 5 hours with the same problem. Sometimes the map would show up and sometimes it would not. In the end, I found out I had a problem with my key. I accidentally deleted its permission to iOS. Some emulators were showing the map because they had the key cached. And some others were displaying the "StorageWithTileProto" error, because they had the tiles cached with the old key but no authorization do show it.
I would recommend anyone with the "StorageWithTileProto" to test it with a new unrestricted key and to fully delete the app from the device/emulator before testing it. This might solve your problem as well.

Google Maps SDK for iOS Runtime warning - Core Date Failed to Load Optimised Path

Apparently this was fixed today, in 1.10.4.

FYI, it didn't cause any problems as far as I concern, other than the message on the log.

---

Related Topics