Issues with SDK 6 – SAS Token Images, BlueDot Size, and Accessible Doors

Hi Mappedin team,

We’re using Mappedin SDK 6 with the following stack:

  • Vue 3

  • Vite

  • Typescript

We’ve run into a few issues:

  1. SAS Token Images

    • When fetching spaces / location-profiles and POIs, the images/logos return SAS token errors in the console.

    • Any guidance on configuration or known fixes?

  2. BlueDot Rendering

    • The BlueDot appears too large when the map is small (e.g., 776px x 387px) and when stackedMaps expanded mode is active.

    • It displays fine in fullscreen.

    • Is there a recommended way to normalize its size across viewports?

  3. Accessible Doors

    • In CMS, some doors are set to Never use (Door → During Navigation → Never use).

    • However, they still appear in navigation paths when using:

      mapView.navigation.draw()
      mapData.getDirections({ accessible: true | false })
      
    • Shouldn’t these restricted doors be excluded? Or is there additional configuration required?

Any help or clarification on these would be greatly appreciated!

Thanks,
William – Frontend Developer @ Igotcha

Hi William,

What version of Mappedin JS are you using? Please update to the current Mappedin JS version v6.0.0-rc.3 if you are using a previous one.

I do recognise the first two issues as bugs that have been fixed.

Accessible doors is a relatively new feature in the Mappedin Editor and if you are using an older version of Mappedin JS from before this feature was added the navigation will not respect that setting. This capability requires Mappedin JS v6.0.1-beta.43+.

Let me know if you continue to see any of these issues after upgrading to the latest version.

Mark

Hi Mark,

Thanks for your reply.

I just updated mappedin version from 6.0.1-beta.48 to 6.0.1-beta.53 (“@mappedin/mappedin-js”: “^6.0.1-beta.53”).
Can you confirm if this is the latest release, or would you recommend switching to v6.0.0-rc.3 instead?
At this stage:

  • The BlueDot still renders quite large in a small container.

  • We’ll be testing the accessible doors again with the updated version (6.0.1-beta.53) and will let you know the results ASAP.

Thanks again for your support and clarification!

(attachments)

I do recommend upgrading to v6.0.0-rc.3, but note that there are some breaking changes between our beta and rc builds. These are outlined in the Mappedin JS Release Notes.

6.0.1-beta.53 is our final beta.

Also, to clarify v6.0.0-rc.3is newer than 6.0.1-beta.53 (even though the beta has 6.0.1 vs 6.0.0).

Thanks,

I will try that and let you know ! Appreciate the clarification though