iOS: Capture to Daily Note Shortcut fails if Daily Note doesn't exist

Once you’ve done the above, delete everything above this line.

Steps to reproduce

  1. Setup new empty vault (on iOS) and create Daily Notes folder. Setup Daily Notes core plugin to place in folder.
  2. Create a new shortcut in the iOS app. add the “Capture to Daily Note” action and fill out text with something like “Testing” and assign to the empty vault
  3. Run Shortcut. Expect Error “File: “Test/Daily Notes/2026-01-23.md” not found”

Did you follow the troubleshooting guide? [Y/N]

Yes, I went through the troubleshooting guide

Expected result

It will add the text “Testing” the day’s daily note. If the daily note doesn’t exist, a new one will be made and then text added.

Actual result

Shortcut app will send a notification or prompt you saying “File “Test/Daily Notes/2026-01-23.md” not found.” (today’s date)

Environment

SYSTEM INFO:
Operating system: ios 26.2 (Apple iPhone15,2)
Obsidian version: 1.11.5 (279)
API version: v1.11.5
Login status: logged in
Language: en
Catalyst license: none
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none


Additional information

shortcut action:

Context: I’m using this capture to daily note as a task quick capture (working with the Tasks community plugin). I would think that expected behavior for this shortcut action to create a new note (with the appropriate daily note template if specified) and then add the text. If this isn’t what the devs meant, I’d greatly appreciate a workaround or alternative to achieve this functionality. Thanks!

Which app?

Which Obsidian URI is begin executed exactly?

Anyway, we are investigating this matter as we had a couple of reports.

Ok, we managed to reproduce a problem. It should be fixed in Obsidian 1.11.6.

Let me know if it solves the problem for you when you get it.

1 Like

I’ve just updated to 1.11.7 and I’m still seeing this issue

@gedthecreator can you create a new vault and make a screen recording of the problem happening there?

I have the feeling that either this is a plugin problem or we are not understand what the problem is.

Also please, run the command “show debug info” and paste the output in your reply