Correct. Your suggestion to set a different browser to be default worked. Switched from FireFox to chrome and the log in worked correctly. Yes, remembered to set back to FireFox after I was done.
Thanks
1 Like
You’re welcome! Glad that helped! 
That’s a good question. I’m wondering if their distribution is all messed up. I can tell you that I have 3.2.8 b603 and there is no new version available to me. I can also tell you that my #$%^& iPhone is on 3.2.7 (1) but Test Flight says there is a new version 3.3.0 (2) available. But if I attempt to install it, it says that I am on the latest version. Go figure…
Won’t surprise me a bit.
This was posted a while ago that’s why I raised the question when they posted the 3.2.8 
:
That’s funny, I on the other hand I can go back and forth between 3.2.8 and 3.3.0 in TestFlight on both iPhone and iPad.
Some Posts have been deleted as they were not following the community guidelines, specically: Keep it Tidy
Please ensure that posts remain on topic does not divert from it. I realize that at times, topics become open ended, but we try to ensure each topic keeps on point.
2 Likes
When I cleared Cache it didnt work for me either but when I cleared Data and Cache it worked. I did not hv to reinstall app.
2 Likes
Now running 3.2.8. b603. Same issue as the others on Android. Opens and crashes. After clearing cache (didnt work) then DATA, app started working again. Something is clearly wrong with the recent release.
The Wyze app updates are mostly to pump more advertisements and make a profile on you.
Your input is highly valuable 
Not sure where to post this.
A few days ago I saw a post from a wyze employee stating that a new beta had been posted. Usually takes a few days for it to appear on Google play.
I kept looking for that posting and could no longer find it in Beta category.
Today I received a new phone and when it finished transferring old phone to new I checked the wyze app release and it had updated to b604.
I looked again in the beta category and could not find b604.
b604 does appear to fix the app startup crash.
But I am seeing a terrible performance hit on my camera group. More error codes than I have ever seen. I’ll document once I feel everything is stable.
I am still finishing up the new phone so I may find something I’ve missed.
What’s interesting is I see no postings on the forum from anyone.
p.s. Galaxy s24 ultra, android 14, December update.
1 Like
I noticed the new update but I’m not noticing a difference with my groups (no errors).
What camera models are doing it?
Give me some time.
I still want to restart the router and uninstall/install the Wyze app.
Said to better half this morning–“new phone can be a couple of hours or a week” . Been at it for 8 hours. 
1 Like
Your going to love this. Definitely a candidate for the bizarre bin.
Background. I have a litmus test that I put every release through.
I have a camera group with 10 cameras. A mix of 3-WBCP, 3-PS V3, 2-V4, 1-OG-T, 1-Doorbell v2. When I open the group I expect the first camera to come up within about 4 seconds, each following camera in 1-2 seconds as I scroll down the cameras. WBCP take approx 10 seconds.
When everything is right I can scroll down the list slowly and reach the last camera in about 15 seconds.
When wyze breaks something I will start seeing error codes, off-line, bouncing balls etc.
Long winded way of saying in this case it was not wyze but the speed of my new phone.
As I was bringing up the new phone I kept saying to self this thing is stupid fast. My S21 was snappy. This is warp speed. I made a mental note to turn the animations back on in developer options.
As I was observing the weirdness as my group was opening I realized that when I paused the error code would go away. I would scroll to the next camera and the same would happen.
Following screenshot shows the nonsensical error code. It was hard to get a shot as the code would only stay on screen for a second or so.
Now my brain put 2 and 2 togather. I had a race condition.
Hmmm-- what happens if I turn the animations back on.
It cured the error codes and my litmus test started passing. To make sure I tested 3 times. Animations off, error codes, unusable. Animations on, no error codes. Usable.
I am speculating that the animation gave wyze enough time to get a valid stream.
Anyway b604 seems back on track.
Put this one back in the bizarre bin.
Long day. Signing off
1 Like
Huh, that is interesting. You would think that shouldn’t make a difference. It will be good to keep an eye out for it.
The plot thickens. My old phone (S21 ultra) is still on b603.
I usually turn off the animations. I like a faster screen response. When I checked the animations they were turned on. Hmm, I don’t remember setting them on, but I could have fat fingered them doing some earlier testing.
For grins I turned off the animations on the old phone (b603). Low and behold I saw the same garbage as I saw on the new phone (b604) including bouncing balls, timeouts and nonsensical error codes as seen below.
I don’t know when this crept into the code but there is something there.
If your seeing connectivity issues with grouped cams it might be worth checking if animations are off.
For those on Android the settings can be found in Developer Options. For those using android 14 there is now a setting in:
Accessibility > Vision Enhancements > Reduce Animations.
Still in the bizarre category!!
This is a special beta test of the service, running in parallel with the regular 3.3 beta test. I apologize for any confusion. Did you notice the icon in the attached image? Clicking it will enable landscape mode.
Yes I did and that is not landscape mode by any stretch.
Did you read my post?
1 Like
I sincerely apologize for the inconvenience caused. Please upgrade to version 3.2.8.b604 to resolve your crash issue
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.