Hi. Has this been resolved? I’m having the same issue. Thanks
I’m having the same issue! I have to double scroll 25+ times to review footage from 7am on the day of choice, and if I actually view an event, when I’m done, I now (as of the last 2 weeks) get booted back to the top 11pm footage and have to double scroll another 25+ times to get back to 7am… it’d be nice if I could just go directly to whatever time of day I’m trying to get to, which is usually 7am for me.
Seems to be fixed in IOS App 2.44.5.x but not the Android version yet.
Thanks. Looking forward to this being fixed
You could try an older version of the App before this bug started.
I am having this same issue? Any update from wyze team when this will be fixed?
I am having this same issue after recent app update, Is this going to be fixed anytime soon or should I just downgrade the app?
Also, I am not able to install older version. It says package is invalid.
We are still looking for the root cause of the issue on Android, the fix we made prior only fixed the issue on iOS.
Same problem with my Pixel 4xl
I have been experiencing this issue for some time now. It is getting very annoying.
Can you please fix? Happens on both android and IOS
Can you tell me the app versions you are running? We fixed it on iOS a while back and we are working on the fix for Android.
I stand corrected. It looks like this issue is just recently working as it should in IOS.
It continues to be an issue with Android and has been for many months. When can we expect a fix?
We have found the root cause for the issue in Android and are currently working it into an app update so it should be coming soon, I do not have an exact ETA however.
It may be of interest to know the TimeLine behaves correctly and revert back to the last viewed area in Android version 2.45.0 (342) and IOS version 2.45.1 (1).
We pushed a hotfix out today that fixes the issue in Android.
Thanks WyzeJasonJ !!!
Android Wyze App Version 2.45.6(361) seems to have fixed the “return to event list in the wrong place” again.
It appears an app update yesterday fixed this issue for me on Android. Thx.