4.3 1191 Pre-release changed theme upon update [Fixed b1195]

[vitor]

Just updated to 4.3 [1191] and my Alfred theme changed to something else, but upon going to Alfred Preferences → Appearance, my theme was still selected. Simple fix: had to select another theme and then mine again to get back to normal, but this might be worth fixing internally.

 

Naturally, due to the nature of the issue I can’t retest to make sure it wasn’t an isolated incident.

 

macOS 10.14.6 (18G6032)

Alfred 4.3 [1191]

[rileytwo]

I think the theme is reset to the default 'Alfred' theme.

 

I was able to reproduce by quitting and opening Alfred. Alfred Preferences showed the theme I had selected as still being set, although the default Alfred theme was used. @vitor's fix worked for me as well.

 

macOS 11.0.1 (20B29)

Alfred 4.3 [1191]

[Andrew]

I haven't looked into this deeply yet, but I imagine what is happening (due to the enhancements in Alfred's window config in 4.3 pre-release) is Alfred is internally getting the "current theme" before it's dark mode internal helper is setup. As such, Alfred might have been showing you e.g. the selected light mode theme for your current dark mode.

 

Out of interest, are you both in dark mode?

[Andrew]

Note, if you haven't seen the upcoming 4.3 changes on theming, take a look here:

 

 

[vitor]

56 minutes ago, Andrew said:

Out of interest, are you both in dark mode?

I am!

[rileytwo]

I am as well. From what I can tell, the theme is reset regardless of the blur method in use. I tried Light/Dark/Deprecated and No blur, but all were reset after restarting Alfred.

[raguay.customct]

I’m also getting this issue, and it happens everytime I reboot. I also am on dark mode using the Dracula-Pro theme. This theme has no blur setting at all.

Edited November 30, 2020 by raguay.customct

[Andrew]

I'll update the pre-release later today with a fix for this, it's caused by essentially what I described above.

[Andrew]

If you update to the 4.3 b1193 pre-release, this should now be fixed

[vitor]

7 hours ago, Andrew said:

If you update to the 4.3 b1193 pre-release, this should now be fixed

 

Confirmed. Thank you.

[raguay.customct]

Sorry, I forgot to reply. Yes, it’s working fine for me now also. Thanks!