hammerspoon doesn't play nice with spotify's pwa

[oldsouless]

Env

Macos Big Sur latest Hammerspoon latest Application: Spotify's pwa bundle

Issue

• Expected: Open spotify's pwa with hammerspoon running without issue.
• Actual: Open spotify's pwa with hammerspoon running causes spotify's pwa to flash briefly and then close. Alternatively opening hammerspoon with spotify's pwa already running causes the pwa to close as if it was sent a kill signal. No visible log errors or message from hammerspoon's console and hammerspoon is the only app that behaves this way in conjuction with the pwa. Note that Spotify's native app works fine with hammerspoon but their are valid reasons to prefer the pwa: faster, lighter, ui preference.
• Tried recompiling hammerspoon with the spotify extension disabled, still the same result.

[cmsj]

at a guess, I would imagine that this is actually the PWA crashing when something sends it accessibility events. Are you using something like hs.window.filter in your Hammerspoon config? If so, that would likely be interrogating the PWA when it launches, to find out some information about it, and some bug in the PWA causes it to then crash.

It's possible we might be able to figure out some ways to ignore that particular app if it's unstable - I wonder if you open Console.app, does the PWA show up in the Crash Reports section?

[oldsouless]

I indeed use hs.window.filter.new():setCurrentSpace(true):setDefaultFilter{}) in my config; commenting that out fixes the issue but ideally wouldn't have to; the pwa doesn't appear in crash reports.

[cmsj]

Have a look at http://www.hammerspoon.org/docs/hs.window.filter.html#ignoreAlways - if you can figure out the right window title to put in there it might help?

[oldsouless]

Confirmed working with ignoreAlways and the 'title' but would prefer to use the bundle id instead, is that an option?