Thread Starter
TheTou
(@thetou)
looks like they rushed-released 1.3.3 to correct this bug, I just found it by refreshing while posting here
yes it seems to work again with 1.3.3, thanks for the info!
@jorritschippers: Thank you! This solved the problem for me!