Bear Failing Silently on .md import after update

Bear feedback Bear Bug Report
1
  • Bear Version: 2.10 (14800)
  • OS Version: Mac OS 26.6.2
  • What were you doing: Importing .md files
  • What feature did you use: Import Notes…
  • What happened: Fails silently
  • What did you expect to happen: Note should appear

I have several AI tools generating .md documents for me that I import into Bear. This has always worked flawlessly. Now Bear won’t import them and if I open them with Bear directly they appear as attachments in the note.

This only fails for .md files. HTML imports cleanly.

❯

mdls -name kMDItemContentType -name kMDItemContentTypeTree bear-test.md
kMDItemContentType = "net.daringfireball.markdown"
kMDItemContentTypeTree = (
"public.item",
"public.text",
"public.data",
"public.content",
"net.daringfireball.markdown",
"public.plain-text"
)

Feels like this happened during the update for OS27 that you all put out.

I tested on a machine that has Mac OS 27 installed and this is not an issue there

This is a work machine - so I cannot upgrade to OS 27 until Enterprise Technology has cleared the way - which could be a while. Import from Folder does work (as does the scripted callback method) but would love to see this resolved. I use Bear across my device family.

2

Same thing here, and I’ve got a detail that might help narrow it down.

Bear 2.10 (14800), macOS 26.6. Same symptom: opening a .md file with Bear gives me a blank note with the file hanging off it as an attachment.

What surprised me is that if I copy the exact same file to .txt and open that, it imports perfectly. Full text, markdown rendered, title picked up from the leading # heading. Only the extension is different. So the text import path itself looks fine, it’s specifically .md that’s getting routed to the attachment handler.

I went down the file-association rabbit hole first assuming it was something on my end, and it isn’t. net.daringfireball.markdown still conforms to public.plain-text → public.text → public.data, and rebuilding the Launch Services database didn’t change anything. Making Bear the default app for .md didn’t either.

It also fails identically through every route I’ve tried: double-click, Open With, and Bear’s own “Send to Bear” item in the Services menu.

Started for me on Sep 16. The x-callback-url workaround is holding me over, but it’d be great to get Open With working again.