Closed janluke closed 2 years ago
Sorry for the late response, I must have missed this. Is the problem resolved in v1.1.4 @janluke?
Sorry, I've not had time to try this out but I guess you did if you closed the issue.
v1.1.3 was basically a bugged release. I haven't double checked, but if it worked in v1.1.2, it should work in v1.1.4 👍 Please feel free to double check though
Just a quick report, likely a bug. This happens with v1.1.3 but not with v1.1.2.