Plugin not rendering any map on ios

[melbv]

Hi @esm7

Thanks for the grand plugin which i had been using extensively until it stopped working towards the back end of last year.
I can toggle it on but when i try to open it on iOS, nothing happens. I used the 'Advanced Debug Mode' plugin to try and print the issues but they seem random to me (and not really similar to the issues described thus far).
Would you know what causes the failure?

Thanks in advance
M

[esm7]

It seems like there is a parsing error somewhere in your config or vault.
If you could expand the error that says "unexpected character" (the first one fully showing in your screenshot) and show the stack trace, I might be able to pinpoint better where the problem is, but it is likely in one of the following:

• A tag in your vault that includes a character that Map View does not expect (any tags with special characters of any kind?)
• A display rule that cannot be parsed. To check this, can you paste the displayRules section of your plugin data file (data.json in VAULT/.obsidian/plugins/obsidian-map-view)?

[melbv]

Sure - trying to give you some more colour. All my tags are emojis. I am a simple visual dude..
Attached are the start of my displayrules section + expanded debugging console.

[esm7]

The stack trace gives a hint at what can be patched to prevent a crash, but unfortunately I can't see the root cause from it.
An immediate suspect is the innerHTML of your default rule but it's just a hunch.
I think the best next step would be to try to isolate the possible causes by:

1. Backing up your data.json.
2. Removing the displayRules from your data.json (or renaming it to something else like displayRulesBackup so it's effectively removed).
3. If this solves the issue, and Map View comes up with your markers showing a default set of display rules, try to isolate one by one what the offending rule might be.
4. If it's not the display rules at all, we'll continue to dig deeper.

[melbv]

Grand - thanks for the path forward! Ill do that a bit later today and will revert! M 24 Feb 2026 at 08:04 by ***@***.***:

…

esm7> left a comment > (esm7/obsidian-map-view#385) <#385 (comment)> The stack trace gives a hint at what can be patched to prevent a crash, but unfortunately I can't see the root cause from it. An immediate suspect is the > innerHTML> of your default rule but it's just a hunch. I think the best next step would be to try to isolate the possible causes by: Backing up your data.json. Removing the > displayRules> from your data.json (or renaming it to something else like > displayRulesBackup> so it's effectively removed). If this solves the issue, and Map View comes up with your markers showing a default set of display rules, try to isolate one by one what the offending rule might be. If it's not the display rules at all, we'll continue to dig deeper. — Reply to this email directly, > view it on GitHub <#385 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AVIFVNTDAZV2Q3MVI226G5D4NPZWLAVCNFSM6AAAAACV47LMM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNBZGY3TMOBWGE>> . You are receiving this because you authored the thread.> Message ID: > <esm7/obsidian-map-view/issues/385/3949676861> @> github> .> com>

[melbv]

I cannot seem to expand the console log to find the culprit. It seems to be nested at n-th level somewhere.. However, removing manually from data.json all displayrules did help and now the plugin does load and display. In iOS wity Liquid Glass, i cant seem to access the right setting from the app (attached). Ill re-inject markers 1 by 1 into the json directly manually today to test. 24 Feb 2026 at 08:04 by ***@***.***:

…

esm7> left a comment > (esm7/obsidian-map-view#385) <#385 (comment)> The stack trace gives a hint at what can be patched to prevent a crash, but unfortunately I can't see the root cause from it. An immediate suspect is the > innerHTML> of your default rule but it's just a hunch. I think the best next step would be to try to isolate the possible causes by: Backing up your data.json. Removing the > displayRules> from your data.json (or renaming it to something else like > displayRulesBackup> so it's effectively removed). If this solves the issue, and Map View comes up with your markers showing a default set of display rules, try to isolate one by one what the offending rule might be. If it's not the display rules at all, we'll continue to dig deeper. — Reply to this email directly, > view it on GitHub <#385 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AVIFVNTDAZV2Q3MVI226G5D4NPZWLAVCNFSM6AAAAACV47LMM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNBZGY3TMOBWGE>> . You are receiving this because you authored the thread.> Message ID: > <esm7/obsidian-map-view/issues/385/3949676861> @> github> .> com>

[esm7]

So this confirms the problem is indeed in the display rules. Pinpointing the rule that causes the issue will both provide an immediate work-around for you and will probably allow me to fix the broader issue for others!

[melbv]

Will have a look today and let you know 24 Feb 2026 at 09:13 by ***@***.***:

…

esm7> left a comment > (esm7/obsidian-map-view#385) <#385 (comment)> So this confirms the problem is indeed in the display rules. Pinpointing the rule that causes the issue will both provide an immediate work-around for you and will probably allow me to fix the broader issue for others! — Reply to this email directly, > view it on GitHub <#385 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AVIFVNQTISYRART2UAU7DNL4NQBZDAVCNFSM6AAAAACV47LMM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNBZHEZTOOJZGA>> . You are receiving this because you authored the thread.> Message ID: > <esm7/obsidian-map-view/issues/385/3949937990> @> github> .> com>

[melbv]

Just tested them all and the below got the plugin to crash - they represent a quarter of my marker setup.

    {
      "query": "tag:#☕️",
      "preset": false,
      "iconDetails": {
        "prefix": "fas",
        "icon": "fa-coffee",
        "markerColor": "cyan"
      }
			},
    {
      "query": "tag:#🛍️",
      "preset": false,
      "iconDetails": {
        "prefix": "fas",
        "markerColor": "yellow",
        "icon": "fa-shop"
      }
    },
    {
      "query": "tag:#⚽️",
      "preset": false,
      "iconDetails": {
        "prefix": "fas",
        "icon": "fa-futbol",
        "markerColor": "red",
        "shape": "square"
      }
    },
    {
      "query": "tag:#🏔️",
      "preset": false,
      "iconDetails": {
        "prefix": "fas",
        "markerColor": "green-dark",
        "icon": "fa-mountain",
        "shape": "square"
      }
    },
    {
      "query": "tag:#🖥️",
      "preset": false,
      "iconDetails": {
        "prefix": "fas",
        "icon": "fa-server",
        "markerColor": "orange-dark",
        "shape": "star"
      }
    },
    {
      "query": "tag:#⚜️",
      "preset": false,
      "iconDetails": {
        "prefix": "fas",
        "icon": "fa-scroll",
        "markerColor": "blue-dark",
        "shape": "star"
      }
			}

Is there anywhere where i can get a list of accepted color and shape values? I have to re-enter all my markers as the plugin actually (weirdly) de-cached all the files that it caught with the tag search and, at the end, wrote over all the markers i pasted directly into the data.json file...

[esm7]

I think these are the colors supported by Leaflet.ExtraMarkers (but can't make sure right now):

const colors: {
  "red": "#a23337",
  "orange": "#ef9227",
  "orange-dark": "#d73e29",
  "yellow": "#f5bb39",
  "cyan": "#32a9dd",
  "blue": "#1b75bb",
  "blue-dark": "#276273",
  "purple": "#440444",
  "violet": "#90278d",
  "pink": "#c057a0",
  "green-light": "#70b044",
  "green": "#009549",
  "green-dark": "#006838",
  "white": "#ffffff",
  "black": "#231f20",
};

You pinpointed the problem well enough so I can probably recreate it, but until I manage to work on it (maybe next week), can you try to isolate it further and see if it's a matter of the color names or the emojis?
e.g. if you change all colors to 'red' in your rules, does it work?
If you change all tag names to letters, does it make it work?

(Please note that indeed Map View will rewrite display rules after settings are saved, so make sure to back them up when doing this investigation)

[melbv]

Clearly the emojis - your marker setting does also flag these emojis when you enter the 'tag:#' + 1 of the below emoji into the marker settings widget. A '!' appears next to it. This emoji '🏛️' also does not work! Let me know when you have had a look. Good luck 24 Feb 2026 at 10:44 by ***@***.***:

…

esm7> left a comment > (esm7/obsidian-map-view#385) <#385 (comment)> I think these are the colors supported by Leaflet.ExtraMarkers (but can't make sure right now): const colors: { "red": "#a23337", "orange": "#ef9227", "orange-dark": "#d73e29", "yellow": "#f5bb39", "cyan": "#32a9dd", "blue": "#1b75bb", "blue-dark": "#276273", "purple": "#440444", "violet": "#90278d", "pink": "#c057a0", "green-light": "#70b044", "green": "#009549", "green-dark": "#006838", "white": "#ffffff", "black": "#231f20",}; You pinpointed the problem well enough so I can probably recreate it, but until I manage to work on it (maybe next week), can you try to isolate it further and see if it's a matter of the color names or the emojis? e.g. if you change all colors to 'red' in your rules, does it work? If you change all tag names to letters, does it make it work? (Please note that indeed Map View will rewrite display rules after settings are saved, so make sure to back them up when doing this investigation) — Reply to this email directly, > view it on GitHub <#385 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AVIFVNSS4WQZWO64JQTTMKT4NQMPVAVCNFSM6AAAAACV47LMM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNJQGM4TQMBYHA>> . You are receiving this because you authored the thread.> Message ID: > <esm7/obsidian-map-view/issues/385/3950398088> @> github> .> com>