matomo-mobile-2
matomo-mobile-2 copied to clipboard
matomo-org
Graphics glitch on iOS version
On the latest iOS version, when opening the Visits Log, after going back a few pages by pressing the „Previous“ button, entries get displayed on top of each other, making them impossible to read.
Thanks for reporting this @KarimGeiger . Does this happen every time you open it?
@tsteur yes, it's reliably reproducible. Sometimes it happens on the second page, sometimes on the third or fourth. The first page is always fine.
Thanks for this @KarimGeiger It took me a while to reproduce it but could see it happening once after moving a lot between pages. It happened for one row for me, and funnily it corrected itself after few seconds. Still struggling to reproduce it more often. Could you let us maybe know your iOS version and your model?
Sure. I’m on 15.3.1 on an iPhone 12 Pro. A wild guess, but maybe it’s to do with how fast the server responds?
Be great if you could check if this happens maybe more when being on a slower mobile data or more on a faster wifi. I couldn't reproduce any difference there so far but that doesn't mean anything. If you notice it sometimes happens more often and sometimes less often that be great to let us know @KarimGeiger it would help us better reproduce the issue and understand why this happens.
Can’t really tell a huge difference. It seems to be a tiny bit more frequent on Wifi than on mobile data, but that may just be my imagination. It is however still present on both. When scrolling through 10 pages, about 4 of them have this issue at some point. Not consistently, though. Additionally, it doesn’t seem to matter if I switch through the pages slowly or in fast succession. And I never had it fix itself, like you described.
Another thing that may be of interest: if it happens, even if I try to go back to the previous page with „next“ and then back again with „previous“, it’s still bugged just like before. Interestingly, if I do it the other way around, it seems to fix itself (first go „previous“ then „next“).
Thanks for this @KarimGeiger . We'll try to reproduce it again and see if we can do something.