Hi everyone, we're seeing a new issue with a long-running MyGeotab add-in and wanted to check whether others are seeing the same pattern. We have a custom add-in package with standard pages plus Map/Trips add-ins. Standard pages still load, but Map/Trips add-ins fail to install at runtime. Previously this occurred for accounts with Geotab camera devices but now it seems to affect any account. At a high level, it looks like this started after camera add-in behavior changed in our environment. What we're seeingStandard custom add-in pages workMap/Trips add-ins fail with:“Add-in can't be installed”“Can't be loaded”This is reproducible in affected accounts What we testedHard refresh / cache resetAdded bootstrap and handshake logging in map iframe entry pagesConfirmed map iframe boot logs appearAdded asset health checks; assets are reachable (HTTP 200)Added additional safe bootstrap delegation + late-binding handler logic New technical detail we foundWe're also seeing runtime logs from a separate camera add-in bundle (not our code), including:RegisteredName: "mygeotab-camera-addin"CAMERA ADD-IN JURISDICTION: EU/USfeature-flag logic around jurisdiction mismatch handling So while we can't prove causation yet, this suggests a coexistence/platform-level interaction may be affecting map add-in install/hello flow for other custom add-ins. Why we're postingWe'd like to confirm whether there were any recent platform changes affecting Map Add-In install/handshake behavior when camera add-ins are present.If anyone from Geotab or other partners has guidance, we'd appreciate:Any known changes to Map Add-In install/hello flowKnown coexistence constraints with mygeotab-camera-addinRecommended compatibility pattern for custom map add-ins in mixed add-in environmentsThanks in advance.

MyGeotab Map Add-In no longer loading

page-user page-user-michael-oberhausen-5515 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

A broadcast-only group for receiving Geotab integrations news and updates!

Integrators Group

Hi everyone, we're seeing a new issue with a long-running MyGeotab add-in and wanted to check whether others are seeing the same pattern. We have a custom add-in package with standard pages plus Map/Trips add-ins. Standard pages still load, but Map/Trips add-ins fail to install at runtime. Previously this occurred for accounts with Geotab camera devices but now it seems to affect any account. At a high level, it looks like this started after camera add-in behavior changed in our environment. What we're seeing<ul><li>Standard custom add-in pages work</li><li>Map/Trips add-ins fail with:<ul><li>“Add-in can't be installed”</li><li>“Can't be loaded”</li></ul></li><li>This is reproducible in affected accounts</li></ul> What we tested<ul><li>Hard refresh / cache reset</li><li>Added bootstrap and handshake logging in map iframe entry pages</li><li>Confirmed map iframe boot logs appear</li><li>Added asset health checks; assets are reachable (HTTP 200)</li><li>Added additional safe bootstrap delegation + late-binding handler logic</li></ul> New technical detail we foundWe're also seeing runtime logs from a separate camera add-in bundle (not our code), including:<ul><li>RegisteredName: "mygeotab-camera-addin"</li><li>CAMERA ADD-IN JURISDICTION: EU/US</li><li>feature-flag logic around jurisdiction mismatch handling</li></ul> So while we can't prove causation yet, this suggests a coexistence/platform-level interaction may be affecting map add-in install/hello flow for other custom add-ins. Why we're postingWe'd like to confirm whether there were any recent platform changes affecting Map Add-In install/handshake behavior when camera add-ins are present.If anyone from Geotab or other partners has guidance, we'd appreciate:<ol><li>Any known changes to Map Add-In install/hello flow</li><li>Known coexistence constraints with mygeotab-camera-addin</li><li>Recommended compatibility pattern for custom map add-ins in mixed add-in environments</li></ol>Thanks in advance.

Recent Activity

MyGeotab Map Add-In no longer loading