Custom Editor issues (macOS)

Bugs
#1

I can no longer open files on my Mac that I have previously set a custom editor for in Defold e.g. I double click to open Context.lua file I will get an alert saying that:

The document “Context.lua” could not be opened. Defold cannot open files in the “Lua” format.

I’ve set .lua files to have a default application of MacVim and I’ve set up Zed as my custom editor in Defold. So the Mac should be opening this in macVim if I open from the Finder.

In addition, opening files as “Code in Custom Editor” opens Zed but the Zed menu does not appear. It stays as Defold. My guess is that this is somehow interfering with the OS in such a way as it does not understand the application it is opening files with. This means I can’t use the Zed functionality from a menu bar.

This also happens with .png files which no longer open in Preview and show a similar message about Defold being unable to open files in the PNG format even though it should be opening Preview.

#2

I haven’t heard of anyone recently having issues with opening script files in a custom editor. I don’t think we have changed anything related to this in some time.

You mean double click from the Asset Panel within the Defold editor or from Finder on your Mac?

#3

What os version are you using?

#4

This is in the Finder and the associated app is set to MacVim.
macOS 15.1

I upgraded from 14 to see if I could fix the problem.

#5

Could it be that the MacVim file association somehow got forgotten by the OS?

#6

It showed as MacVim in the file info and has the MacVim icon next to .lua files in Finder. Double-clicking to open in Finder tries to open Defold but displays an alert saying that Defold can’t open lua files.