I just released v3.3.4 and the bug is now fixed!
turns out it was a bug related to the changelog display that only happens on first display (and even then it usually didn't trigger, but with the right timing of bad wifi you could, well, get the crash people were seeing)
turns out it was a bug related to the changelog display that only happens on first display (and even then it usually didn't trigger, but with the right timing of bad wifi you could, well, get the crash people were seeing)
February 3, 2026 at 1:05 PM
I just released v3.3.4 and the bug is now fixed!
turns out it was a bug related to the changelog display that only happens on first display (and even then it usually didn't trigger, but with the right timing of bad wifi you could, well, get the crash people were seeing)
turns out it was a bug related to the changelog display that only happens on first display (and even then it usually didn't trigger, but with the right timing of bad wifi you could, well, get the crash people were seeing)