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

• Standard custom add-in pages work
• Map/Trips add-ins fail with:
  • “Add-in can't be installed”
  • “Can't be loaded”
• This is reproducible in affected accounts

What we tested

• Hard refresh / cache reset
• Added bootstrap and handshake logging in map iframe entry pages
• Confirmed map iframe boot logs appear
• Added asset health checks; assets are reachable (HTTP 200)
• Added additional safe bootstrap delegation + late-binding handler logic

New technical detail we found

We'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/US
• feature-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 posting

We'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:

1. Any known changes to Map Add-In install/hello flow
2. Known coexistence constraints with mygeotab-camera-addin
3. Recommended compatibility pattern for custom map add-ins in mixed add-in environments

Thanks in advance.