Summary
On iOS, an embedded Map View loads the basemap correctly, but GPX tracks related to the note do not render.
The map itself is initialized and interactive (tiles, zoom controls, etc. are visible), but the GPX path is completely missing and the map does not auto-fit to the track.
I already experienced this occasionally with Map View 6.1.2, but with 6.1.4 it appears to fail consistently in my vault.
This may be related to #404, but my reproduction is different: I am not directly embedding the GPX with ![[route.gpx]]. The GPX is referenced from note metadata and displayed through an embedded Map View.
Environment
• Map View: 6.1.4
• Obsidian iOS:
• iOS: 26.6.1
• Device: iPhone 17 Pro Max
• Vault stored/synced through iCloud
• GPX files are stored inside the vault
Vault structure / setup
A RideDay note contains a link to its GPX file in frontmatter, for example:
track_file: [[2026-09-04.gpx]]
The note also contains an embedded Map View which finds related files, using a query equivalent to:
with auto-fit enabled.
The GPX file itself is valid and exists in the vault.
Steps to reproduce
- Create or open a note containing a track_file property linking to a GPX file.
- Add an embedded Map View configured to show files related to that note.
- Open the note on iOS.
- Scroll to the embedded map.
Expected behavior
The embedded map should:
• load the basemap
• render the GPX path
• auto-fit to the GPX bounds
Actual behavior
The basemap loads successfully and the map controls work, but:
• the GPX path is not rendered
• auto-fit does not fit to the track
• the map remains at an unrelated/default location
So this does not appear to be a tile-provider or general map-loading problem — only the GPX/path layer is missing.
Screenshot attached shows the basemap loaded correctly while the expected track is absent.
Version behavior
Map View 6.1.2
This problem already existed occasionally on iOS.
Sometimes the GPX rendered correctly, sometimes it did not.
Map View 6.1.4
In my current setup the GPX path appears to fail consistently on iOS.
This looks like the older intermittent iOS/path problem may have become fully reproducible, or another regression may now be interacting with it.
Additional notes
My vault also contains property/tag-based Display Rules.
Because of that, I noticed #404:
Display rules crash when rendering GeoJSON/GPX path embeds
However, this case differs from #404 in a few ways:
• the GPX is not embedded directly with ![[route.gpx]]
• the GPX is linked through note metadata (track_file)
• the path is expected to be rendered by an embedded Map View query
• the issue is observed specifically on iOS
• the basemap itself renders successfully
It may nevertheless share the same path/display-rule code path.
I can provide a minimal test vault / GPX file or additional debugging information if useful.
Summary
On iOS, an embedded Map View loads the basemap correctly, but GPX tracks related to the note do not render.
The map itself is initialized and interactive (tiles, zoom controls, etc. are visible), but the GPX path is completely missing and the map does not auto-fit to the track.
I already experienced this occasionally with Map View 6.1.2, but with 6.1.4 it appears to fail consistently in my vault.
This may be related to #404, but my reproduction is different: I am not directly embedding the GPX with ![[route.gpx]]. The GPX is referenced from note metadata and displayed through an embedded Map View.
Environment
• Map View: 6.1.4
• Obsidian iOS:
• iOS: 26.6.1
• Device: iPhone 17 Pro Max
• Vault stored/synced through iCloud
• GPX files are stored inside the vault
Vault structure / setup
A RideDay note contains a link to its GPX file in frontmatter, for example:
The note also contains an embedded Map View which finds related files, using a query equivalent to:
with auto-fit enabled.
The GPX file itself is valid and exists in the vault.
Steps to reproduce
Expected behavior
The embedded map should:
• load the basemap
• render the GPX path
• auto-fit to the GPX bounds
Actual behavior
The basemap loads successfully and the map controls work, but:
• the GPX path is not rendered
• auto-fit does not fit to the track
• the map remains at an unrelated/default location
So this does not appear to be a tile-provider or general map-loading problem — only the GPX/path layer is missing.
Screenshot attached shows the basemap loaded correctly while the expected track is absent.
Version behavior
Map View 6.1.2
This problem already existed occasionally on iOS.
Sometimes the GPX rendered correctly, sometimes it did not.
Map View 6.1.4
In my current setup the GPX path appears to fail consistently on iOS.
This looks like the older intermittent iOS/path problem may have become fully reproducible, or another regression may now be interacting with it.
Additional notes
My vault also contains property/tag-based Display Rules.
Because of that, I noticed #404:
However, this case differs from #404 in a few ways:
• the GPX is not embedded directly with ![[route.gpx]]
• the GPX is linked through note metadata (track_file)
• the path is expected to be rendered by an embedded Map View query
• the issue is observed specifically on iOS
• the basemap itself renders successfully
It may nevertheless share the same path/display-rule code path.
I can provide a minimal test vault / GPX file or additional debugging information if useful.