I’ve been running the app for a long time on the same phone. However, I recently installed something on my phone that logged me out. When trying to log back in, I would tap Get Started, the screen would flash and not do anything. I did however find the fix. I had to change the default browser for Android to something else and it worked.
If support wants to know what caused the issue, it was Sophos Intercept. Sophos changed the default browser to Intercept and it would not allow Wyze to login.
hey @Augustin So I had to delve kind of deep into this because I was not familiar with Sophos intercept, And looking a little bit closer it seems like that runs the browser through itself first and then it’s supposed to hand off to the default but becauseSpphos is your new default, there is no handshake sfor the secure credntials. It’s looking like they use a different protocol than most other browsers, a secure protocol called Oauth, It’s looking like your new default browser failed to get the redirect. I’m seeing it a few times with a few different things not just Wyze. I know stuff like this is typically used on work phones and such, do you have the option to Change it back to a more commonly used browser? im Not entirely sure of what it takes for the secure login credentials to be transferred through things as my IQ is barely higher than my shoe size 
but I don’t know how widespread that particular browser is used and I don’t know if that’s something that Wyze is looking to code into. I wish I could give you more information on that one.
I do have to point out though the fact that you were immediately able to track it back to what you had changed is awesome! It’s that kind of detail that allows good troubleshooting. That’s awesome you were able to capture it and know what the change was that caused the issue. On a side note I would also look for an update to your app if you happen to have it to see if that might solve anything, you mentioned that you had been using this for a while but you know how that stuff goes. I’m thinking potentially maybe there was an update that handled this type of issue but I’ve not run into it myself so I can’t speak from any experience.
It looks like it’s relate to the Link Checker feature in Intercept. A work-around is for me to change the default browser in Android to say Firefox, complete the login through Wyze, then I can re-enable Link Checker.
I don’t believe this is a bug (as this topic is tagged). I’ve been using Sophos Intercept X (currently 9.7.4042) as an anti-malware tool for years and have not experienced problems authenticating with the Wyze app. This is how I have things set on my phone:
I use Chrome on Android only very rarely, and this setup has worked for me for years. This allows links to continue to be checked through Intercept X’s Link Checker and still pass “clean” links to my preferred default browser, which is Firefox, and I prefer Firefox because that allows me to use extensions like EFF Privacy Badger and uBlock Origin.
Incidentally, Intercept X is also what I use for my 2FA tokens (TOTP) for the Wyze app and other sites, and I like that I can copy the Authenticator configuration to another device running the app so that I can retrieve a token from any of several devices when needed. Intercept X uses Android app shortcuts, and there’s one for the Authenticator module, so I have an icon one one of my home screens that makes it easy to tap and see my 2FA tokens.