It's hard to reproduce because it is not consistent but I see what you mean. Could you link the exact image that you managed to reproduce this. I'll see if I can report this to the image library that we use.
testAccount
joined 1 year ago
Yes but exactly which versions are we talking about. 0.0.43 to 0.0.44?
and from which version were and and which did it stop working?
I tweaked it a bit, might resolve when ever 0.0.45 comes out
Can you give the steps to reproduce this, as I can't reproduce this problem rn.
We didn't actively impose this limit. I switched the image library that the ImageViewer uses. And that was its default zooming limit. I think its the same in other apps where they just keep it to the default settings.
Alright thats strange, in that version I added checks ("account verification checks") to ensure your account and device is in a proper state else it will give info to mitigate the problem. (To prevent external events, like when all the instances revoked the JWT when the hack happened and causing it to stop working for all the users) Here it fails on the first step. The first step checks if there any network capability. But from your screenshot I can clearly see you have wifi/mobile capability.
Could you give me some more information about your device/android version. In that version it now also requires the ACCESS_NETWORK_STATE permission for that check. Maybe you revoked it somehow?
The account is not ready yet msg is just that it hasnt cleared the checks yet. Maybe a better phrasing is in order but i am not sure what that is.
What version are you using? 0.0.44 significantly increased the limit.
It still crashes in 0.0.42 ? In about section you can find the crash logs, can you send me that or make issue on GitHub with those logs?
Lemmy 18.3 added it html sanitation which doesn't seem to be properly configured
Here you go, I added it