Map views with a KML layer crash: "KmlLayer ... no longer available in Maps JavaScript API 3.66"

Hi all,

Since today, every map view in our app that has a KML layer fails to render and shows “An unexpected error occurred (id: 169344)”. The whole view crashes, not just the KML overlay. Nothing changed on our side.

Setup: a dashboard with an interactive table of work packages driving a “WP Points” map view of survey points. The map has a KML layer (from Google My Maps) that shows our area boundaries.

Stack trace (from Copy Error Information):

Error: The KmlLayer functionality in the Maps JavaScript API is no longer available in the Maps JavaScript API as of version 3.66. For more info, see https://developers.google.com/maps/deprecations.
    at new un (https://maps.googleapis.com/maps-api-v3/api/js/66/11a/intl/en_gb/main.js:217:30)
    at T.updateMap (https://www.appsheet.com/assets/ee1bdc70....js:1:15916)
    at T.onMountCallback (...)
    at Object.mountMap (...)
    at T.componentDidUpdate (...)

Steps to reproduce:

  1. Open a dashboard containing a map view that has a KML layer configured.
  2. Select a row in the interactive table that drives the map.
  3. The map view fails with the error above.

Our understanding is that Google removed KmlLayer from the Maps JavaScript API in v3.66, and the AppSheet map component still calls it whenever a KML layer is configured. AppSheet doesn’t let us pin the Maps API version, so we can’t work around it ourselves.

Questions for the AppSheet team:

  1. Is this a known issue, and is there a fix or ETA?
  2. Will KML layers move to a supported rendering method (e.g. GeoJSON / Data layer), or is KML support being retired?
  3. In the meantime, is there a supported way to show boundary polygons on an AppSheet map view?
  4. Can map views fail gracefully, i.e. still render the points when the KML layer fails instead of crashing the whole view?

Impact: our field operations team uses this view daily to review survey points against area boundaries. For now we’re removing the KML layer to get the map back, but reviewers lose the boundary context they depend on.

Screenshot below (identifiers redacted):

Tagging for visibility: @Jose_Arteaga @Michelle @Steve @Suvrutt_Gurjar @WillowMobileSys

@Ryan_Wagner, this looks like the same issue you reported in KML Deprecation.

Thanks

Update: Google’s Maps Platform deprecations page (linked in the error itself) confirms this:

  • KML Layer is listed as “Deprecated as of April 30, 2026”, and KmlLayer is no longer available in the Maps JavaScript API.
  • Per Google’s KML Layer Migration Guide, 3.65 is the last version that supports KmlLayer, and it stays available until May 2027. AppSheet is now loading 3.66, which is why map views with a KML layer crash.
  • Google’s recommended replacements for custom vector data (points / polylines / polygons, like our area boundaries) are data-driven styling for datasets, GeoJSON via the Data layer, or third-party libraries such as deck.gl or geoxml3. Data-driven styling for boundaries only covers Google’s administrative boundaries (country, state, county, locality, postal code), so it doesn’t help with custom survey areas.

Since AppSheet controls which Maps API version loads and how KML layers are rendered, none of these options are available to app creators. Could the AppSheet team either pin the map component to 3.65 as a short-term fix, or move KML layers to one of the supported methods above?

@Steve and the AppSheet team (@Jose_Arteaga @Daniel_Rey @Rob_Just @Aleksi), flagging this for visibility: since AppSheet moved to Maps JavaScript API 3.66, any map view with a KML layer crashes completely with “An unexpected error occurred”. Details, stack trace and Google’s deprecation notes are in the posts above.

This affects every app that uses KML layers, and there’s no workaround on the app-creator side because AppSheet controls the Maps API version. Is a fix or ETA available?

Calling in a few more active community members in case you’ve seen this or found a workaround: @kim_nilsson

@Jose_Arteaga, this needs Engineering involvement.

Thanks @Steve and @saravana_ni,

Please find the latest update for this issue here:

I will continue sharing updates on that thread.

Thanks @Steve and @Jose_Arteaga for escalating this so quickly.

Update from AppSheet Support (via a support ticket I raised): on October 24 they confirmed that the issue affecting Map views using KML/KMZ overlays has been resolved.

Confirmed on our side: I’ve re-tested our map views with the KML layer and they load correctly again, boundaries included.

Thanks,
Saravana

Please find the latest update: