New grapheneOS update broke snapchat

matchboxbananasynergy

There doesn't seem like anything GrapheneOS has done that breaks Snapchat. Another user has already confirmed it works fine for them. It sounds like you're doing something that's triggering some anti-abuse check for them or something.

43t34fg4 Gatekeeping what people use on GrapheneOS isn't allowed here. If they need to use that app, GrapheneOS is one of the best systems to do it on. The privacy and security features are more useful for apps that can be invasive, not less.

peppe

all I'm saying is my setup before the update was working perfectly and now after the setup its not working anymore.

And to the people who say they have checked you haven't. instal a vpn/sockdroid and try logging lnto snapchat and then tell me if it works or not (probably won't)

de0u

peppe all I'm saying is my setup before the update was working perfectly and now after the setup its not working anymore.

Ok. But that by itself isn't enough data to be actionable.

peppe I checked again with help from other people and when you use sockdroid to run mobile proxies it gives you that error which was never the case before the update. when I disable socksdroid all works well

That report doesn't say which version of which OS the other people are using. If those people are using something that isn't GrapheneOS, then this issue does not require GrapheneOS. If those people are using last month's GrapheneOS and it SocksDroid causes SnapChat to reject them, then this issue does not require the recent GrapheneOS update. Debugging an issue requires multiple data points. If it possible to report OS versions (build numbers) for some people who SnapChat is accepting even though they are using SocksDroid, that would be pertinent.

peppe And to the people who say they have checked you haven't.

I wonder how it is that you might know that? (If you don't know that, then the assertion might not be productive forum behavior.)

other8026

peppe And to the people who say they have checked you haven't.

This isn't called for. People who have helped you troubleshoot have taken time out of their days just to help out a fellow community member. You respond by essentially saying that they're being dishonest. This isn't appropriate.

A GrapheneOS update is unlikely to have caused this issue. It is almost certainly Snapchat doing this for their own reasons. You would probably be better off contacting them.

peppe

I'm all for getting help but saying it works but not having the same is kinda pointless.

I'm running grapheneOS on a pixel5a with the latest update and latest snapchat update from the aurora store.

here is a video showing the problem. It's not snapchat thats the problem. socksdroid hasn't received any updates its grapheneOS.

[removed]

other8026

peppe I don't know what to tell you. Three people (me and two others) have said that we believe this is entirely on Snapchat's end. It's the most likely explanation. Nothing in recent GrapheneOS updates would have caused Snapchat to start blocking your logins because they detect something suspicious. You don't even need to update Snapchat for there to be a change like this. This could be a result of server side changes on their end. They can easily flag known VPNs or proxies, or whatever. It's almost certain that a GrapheneOS update being installed right before this started is merely a coincidence.

You can keep thinking it's GrapheneOS's fault all you like, but there's no evidence to support that claim. Not sure what else I or others can say to help you realize that.

By the way, I removed the link to your video because your credentials were visible. I'd recommend you change your password right away. You should be able to do that via the "forgot my password" option.

GrapheneOS

It sounds like your VPN server is being blocked. As you said, it works when you aren't using that.

peppe

Only one way to find out. Flashed the custom rom and going to start over and instal an older version of grapheneOS and see if that works.

And yes I know security and all of that. It's a $50 phone that I only use for snapchat so security updates don't really matter to me. It just needs to work again.

peppe

LLLLFFFFFFFGGGGGGG

as I suspected it was a grapheneOS update. installed redfin-factory-2024042100 and all is working again. You guys didn't make it easy on me with deleting old system updates. But it got it working again. I hope you guys fix it with the next update

43t34fg4

I am actually coming across this issue right now. Got a 2ndary phone to be more social with and am experiencing the same SnapChat error. When trying to login, it says, "Due to repeated failed attempts or other unusual activity, your access to Snapchat is temporarily disabled." I know it isn't repeated attempts because it happened even on my first attempt ever on the phone. I will say this: I am using a VPN (the same exact one and server as a 3rd non-GOS phone I have and on the non-GOS phone, it works just fine).

EDIT: And just to clarify, even though it says that access is disabled, I can still use it just fine on the non-GOS phone. Am on the latest version of GOS on a Pixel 8.

HelloMe

Newest versions of Snapchat don't like it if you switch phones or log out. If you look at their support account on Twitter, a ton of people are having the same issue. I got it solved by deleting Snapchat, installing an older version of it, logging in and then updating to the newest version. Avoid logging out or you would have to do the same thing again

Yderkone

HelloMe Which Version are you using?

Yderkone

You can use Version 11.95.0.39 to get it working.
https://www.apkmirror.com/apk/snap-inc/snapchat/snapchat-11-95-0-39-release/snapchat-11-95-0-39-android-apk-download/download/?key=803d9f97cddac55a7a417f244842d0d355c4b81b&forcebaseapk=true

matchboxbananasynergy

We had someone in our chat rooms the other day insisting that a GrapheneOS update had broken Snapchat. I was able to install it and create an account and login just fine on GrapheneOS. It seems Snapchat is raising their anti-abuse system's sensitivity, resulting in errors, but that seems to not be in any way related to GrapheneOS itself.

tech_noob

It shows how aggressive snap is. I've got the same problem trying to install on my sons phone. Will not sign in with google dependences and the apk from aurora store. I will try Yderkone fix.

https://www.apkmirror.com/apk/snap-inc/snapchat/snapchat-11-95-0-39-release/snapchat-11-95-0-39-android-apk-download/download/?key=803d9f97cddac55a7a417f244842d0d355c4b81b&forcebaseapk=true

Should I try exploit protection compatiblity mode?
Will post the outcome when I have a another crack.

matchboxbananasynergy

tech_noob Should I try exploit protection compatiblity mode?

Shouldn't make a difference.

Some people elsewhere have reported a VPN might be another reason for the error, so perhaps try without one.

Lefpadlog

tech_noob Did the method work for you? I tried to install it, but it says that the apk seems to be invalid.

tech_noob

matchboxbananasynergy Yea.. not using a VPN.

Ethan-929292

Not using a VPN either, and had this issue

juliang

Running into the same issue, though I can't tell since when this is the case as I never had snapchat on graphene OS.

I did reach out to snapchat's support and they mentioned two points:

If you are using a VPN, we recommend that you switch it off. If you are not using a VPN, try switching to a different network (changing from WiFi to a mobile network, switching to a different WiFi network, etc.).

If you are experiencing issues creating an account and have a rooted device, you may want to try unrooting your device, removing any exploitation software, and reinstalling the app before creating an account.
Rooted devices circumvent security defenses built into the mobile device, exposing your Snapchat account to additional risk and may not be supported.

The network thing didn't make a difference for me with/without a VPN, wifi or my cellular connection, neither did installing version 11.95.0.39.

I suspect this is related to the second point about "rooted devices". To me this sounds like they introduced some kind of detection and just throw you the "SS03" or "something went wrong".
The exploit protection compatibily flag also didn't change it.