Does It Make Sense I'm Getting An Error In A Task Query In iPadOS But Not Android nor Linux? #3814
-
|
Before I start trouble shooting and possibly submitting a bug report I'm curious if a task query that works fine on my Debian/Gnome laptop and my Pixel 7A GrapheneOS phone could not work correctly/throw an error on iPadOS? The following code does as expected on the laptop and phone But then throws the following error on iPadOS Additionally it isn't recognizing the task priorities even if I take out the function task.tags.map line to get rid of the above error. Again, just trying to determine the feasibility of the situation to help avoid going down the wrong rabbit hole. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi, Without knowing anything about your vaults, and if you are even running the same data on this queries, I cannot say whether it makes sense or not that the behaviour is different. But, for the same vault content, with the same Obsidian and Tasks settings, and a non-corrupt Obsidian cache, the line that gives the error should/would give the same results on all platforms. The failing line is this one:
You can find the pattern for doing this safely by looking at the more advanced examples in this section of the Tasks docs - specifically, look for the examples that use |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much! The code above has been working without an error for many months now on my linux machine and android phone. I then synced the same vault to my iPad with the latest version of iPadOS and noticed the error and sorting behavior mentioned above. I'll take a look at the documentation and also redo the setup since the priority information doesn't seem to be coming over correctly either. Thank you again! |
Beta Was this translation helpful? Give feedback.
Hi,
Without knowing anything about your vaults, and if you are even running the same data on this queries, I cannot say whether it makes sense or not that the behaviour is different.
But, for the same vault content, with the same Obsidian and Tasks settings, and a non-corrupt Obsidian cache, the line that gives the error should/would give the same results on all platforms.
The failing line is this one:
tag.split('/')splits the tag in to "words", at any/characters[1]then choses the second of the "words" - and if there was only one "word" in the tag, it usesundefinedinstead#OneWordit …