You might have a better experience opting out of beta since beta versions are definitely expected to have a lot more bugs and issues than the public releases. What I do is keep at least one device on the production version, and then others on the beta. Or sometimes if the beta breaks something important to me, then I will sideload a previous version back on from APK mirror.
That ain’t it, but I’m gonna. Even when wyze uploads updates to the reg app after beta it’s the same. I see it in the forums all the time.
I have the same problem with the new version that apparently updated on my Galaxy s22 last night. This morning I am running Wyze Version 3.2.8.b603 and it crashes on startup every time. I will try updating or reinstalling the app. I hope Wyze is working on this problem.
As others have mentioned, uninstalling & reinstalling fixed the crashing issue I had.
I would like to know as well
This was a real pain, But after uninstalling and then reinstalling the app it works again.
Please, having to uninstall the app is NOT a solution to a problem that Wyze created. The company needs to ship an update that fixes this.
Wyze isn’t what they used to be, they have no business in making robust products but would rather be a jack-of-all-trades hardware company. Now shoving AI into everything (like everyone else) and even replacing their human customer support with AI. I think it’s best to scrap all the hardware, uninstall the software permanently, and move on to a more reputable company. Beta or not.
This is a beta and that’s what beta is, full of bugs that we as beta testers discover and report.
I guess you and I have a different understanding of what is acceptable or not in a beta. Not all bugs are created equal, and I completely understand the point of a beta as well as the fact it will have bugs.
A bug this severe should have never seen the light of day in a beta channel, and people defending it should really take a step back to realize that.
I hate that everyone is so delighted to uninstall and reinstall! This is not a fix, it’s a temporary solution at best. Still no notification toggle in the pan v3s.
I am getting to that point myself, when you do get to a real person it takes days upon days of emails to get no where! I’ve been with wyze from their beginning and have been let down to many times to count!
You know what? Block me please. I’m so sorry I have a simple solution to fix the beta’s issue. This is why I don’t bother to post. People like your self! Never happy! I’m blocking you so don’t bother responding.
I am not defending anything but it has been my experience that Wyze doesn’t do alfa testing, they are passing that to beta testers. I am not arguing with you, all I’m saying is that only non beta testers who have been upgraded to a beta version have the right to complain. We, the beta testers should not as we signed up for this. If we don’t like it we can always opt out.
Are you a beta tester? If you are then keep on testing and report your findings either here or directly to Wyze.
What you are describing is a non beta issue, this thread is about 3.2.8 app Beta Test.
Not saying it is acceptable, but it boils down to, do you want it to work or not.
I just read another post that you don’t have to delete the app, but rather delete cache and Data. That seemed to fix the issue, I believe you saw that post.
I believe the issue had to do with the Version being lower than the previous beta, but cannot prove that.
With that said, as a beta tester, I accept the risk that any app or FW Update could cause some unwanted issues. I personally am ok with that. I would rather be part of the solution and provide detail quality feedback so when an update gets released to production, there would be minimal issues. Now I know some will say that this is not the case, but I personally have not had major issues. When I did, they were fixed relatively quickly. But everyone will have there own experiences with this as well.
All this to say, if uninstall a previous app and putting another one down does fix the issue, that is what I do and it is minimal issue to me,
How do we leave the beta? I cant even sign into the app now. Get log in is strange and they said blocking…
The google and other log in icons dont respond at all.
Thanks
Yes, that was answered Saturday afternoon by Jason:
3.2.8. b603 is the one with the issue
Welcome to the Forum, @jamesjhalliwell!
If you visit the Android App Testing page in Google Play Store while logged into your Google account, then you should see a LEAVE THE PROGRAM button if you’re currently opted-into the β program.
More information is here:
The question was why did we get a 3.2.8 beta when we were already testing 3.3.0.