Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sign-in problem #637

Open
4 tasks done
Averagegithub-enjoyer opened this issue Jan 29, 2024 · 48 comments
Open
4 tasks done

Sign-in problem #637

Averagegithub-enjoyer opened this issue Jan 29, 2024 · 48 comments
Labels
bug Something isn't working discussion Discussions issue help wanted Extra attention is needed

Comments

@Averagegithub-enjoyer
Copy link

Description

When trying to sign in it displays error saying "due to multiple sign in attempts or suspicious activity your access to snapchat has been temporarily disabled."

Reproduction steps

  1. Attempt to sign in
  2. See error.

Logs

I'm not entirely sure how to find any logs

Snapchat Version

12.70.0.34

SnapEnhance Version

1.2.6

Agreement

  • This is not a bug regarding Snapchat+.
  • I have provided a detailed description of the issue.
  • I have attached a log if deemed neccessary.
  • This issue is not a duplicate.
@Averagegithub-enjoyer Averagegithub-enjoyer added the bug Something isn't working label Jan 29, 2024
@VendorAttestation
Copy link
Contributor

If you're using a custom rom/kernel go back to stock they hate custom roms

@authorisation authorisation changed the title Sign-in problem bug: Sign-in problem Jan 29, 2024
@authorisation authorisation added low priority This is on the low priority list or still in discussion. Implementation is not guaranteed. help wanted Extra attention is needed labels Jan 29, 2024
@RSR1337
Copy link

RSR1337 commented Jan 29, 2024

If you're using a custom rom/kernel go back to stock they hate custom roms

True 👍

@DjCrqss
Copy link

DjCrqss commented Jan 29, 2024

+1, using the latest APK and LsPatch unrooted method. Previous APK and SnapEnhance 2.0.5 worked fine.

Update: using the latest LsPatch and the SnapChat 12.69.0.26 APk worked perfectly for me. New Snapchat may have more security. ApkMirror link

@Anshu-Bijarnia
Copy link

+1, using the latest APK and LsPatch unrooted method. Previous APK and SnapEnhance 2.0.5 worked fine.

Update: using the latest LsPatch and the SnapChat 12.69.0.26 APk worked perfectly for me. New Snapchat may have more security. ApkMirror link

Were you using stock rom or custom?

@DjCrqss
Copy link

DjCrqss commented Jan 29, 2024

+1, using the latest APK and LsPatch unrooted method. Previous APK and SnapEnhance 2.0.5 worked fine.
Update: using the latest LsPatch and the SnapChat 12.69.0.26 APk worked perfectly for me. New Snapchat may have more security. ApkMirror link

Were you using stock rom or custom?

Stock Samsung OneUI 5.1 ROM on android 13

@rhunk rhunk mentioned this issue Jan 30, 2024
4 tasks
@RevealedSoulEven
Copy link
Contributor

Even that version is not working too for custom roms

@Not-Smelly-Garbage
Copy link

Back up your config by exporting it through the snapenhance app, then toggle everything off and log in. It should work, then you can import all your previous settings and be good

@RevealedSoulEven
Copy link
Contributor

Back up your config by exporting it through the snapenhance app, then toggle everything off and log in. It should work, then you can import all your previous settings and be good

Even uninstalled it. Still the same

@histefanhere
Copy link

Any snapchat version, no patches, added sc to magisk denylist, hidden apps via hide my applist and still doesn't allow login. It's possible this might not be a SnapEnhance issue but this is nonetheless a good place to discuss this.

@RevealedSoulEven
Copy link
Contributor

Any snapchat version, no patches, added sc to magisk denylist, hidden apps via hide my applist and still doesn't allow login. It's possible this might not be a SnapEnhance issue but this is nonetheless a good place to discuss this.

Actually, it's a custom rom check, where your device fingerprints and play integrity is checked. Even if you bypass play integrity it won't work coz it needs even Strong Play Integrity to be true

@VendorAttestation
Copy link
Contributor

Any snapchat version, no patches, added sc to magisk denylist, hidden apps via hide my applist and still doesn't allow login. It's possible this might not be a SnapEnhance issue but this is nonetheless a good place to discuss this.

Actually, it's a custom rom check, where your device fingerprints and play integrity is checked. Even if you bypass play integrity it won't work coz it needs even Strong Play Integrity to be true

Custom roms no longer work people need to go back to stock also no Strong Play Integrity is not enforced only Key Attestation / Play Integrity Basic (Standard Aswell) also some phones are banned especially older that are no longer widely used on snapchat as they probably fell victim to abuse.

@Blurry-face-99
Copy link

I don't understand why the support from the Snapchat side is zero except an automated email. Also, did the issue got resolved yet?

@karimmec999
Copy link

Can i bypass custom rom check by using and spoofing device informations (like changing build.prop, spoofing imei, device id ...etc)

@fluid46
Copy link

fluid46 commented Feb 5, 2024

Also having this issue, using version suggested, latest LSPatch and stock ROM, unrooted android.

@VendorAttestation
Copy link
Contributor

Can i bypass custom rom check by using and spoofing device informations (like changing build.prop, spoofing imei, device id ...etc)

You will bootloop so no maybe hooking possible

I don't understand why the support from the Snapchat side is zero except an automated email. Also, did the issue got resolved yet?

if you think there gunna help you for using a mod lol nah its against TOS

@karimmec999
Copy link

Can i bypass custom rom check by using and spoofing device informations (like changing build.prop, spoofing imei, device id ...etc)

You will bootloop so no maybe hooking possible

don't worry about boot looping because i tried doing all what i mentioned above....so any possible would be helpful
Thanks.

@Verequies
Copy link

Verequies commented Feb 12, 2024

Not sure about you guys. But I just spend a couple hours narrowing it down.
Running LMODroid 4.2 on an LG V30+ (H930DS) with Kitsune Mask (Magisk Hide + Enforce SU List enabled), LSPosed, Play Integrity Fix, Hide My Applist (Snapchat hidden from everything and Applist Detector confirms) and Iconify.

I managed to get it to work with a failing Safety Net (not sure why - sometimes its working sometimes it isn't - have to fix this) and basic integrity on Play Integrity Checker. Could be because I spammed checked these services.

Regardless of what I did, the only thing that allowed me to login, was disabling USB Debugging in Developer Options. Quite strange but it worked. Even on the latest version. I might check with Hide My Applist to see if an option to hide this can be added in.

@mzashh
Copy link

mzashh commented Feb 13, 2024

basically your device is banned, the ban is usually tied to IMEI but recently they have upped their security and they are using some other way to detect so spoofing won't help.

however i have a very easy fix for you and should work for root and non root as well, only works for device ban not permanent ban

  1. basically download an old version of Snapchat from 2022 or something it should be v11.78.xxx something like that. APKMirror link

  2. install it and you can login now since it doesn't have any device ban detection.

  3. now after logging in you can update to the latest version via playstore or via apk and you should still be logged in.

note: if you uninstall Snapchat or logout you will have to follow these steps inorder to login again

@Verequies
Copy link

Verequies commented Feb 13, 2024

@mzashh I'm not sure you understand. My device is certainly not banned. I am able to uninstall the app and install it from Play Store and log in successfully without any problems as long as I turn USB Debugging off or in terminal set svc.init.adbd to stopped or empty string by running setprop init.svc.adbd stoppped.

I have decompiled and am currently reverse engineering the app to check how they are checking for USB Debugging status properly. My hopes is that I can add a way to intercept this check into the IAmNotADeveloper Xposed module. That way all apps that do this kind of check will benefit from it.

@Calamardins
Copy link

Does anybody here know a solution to use Snapchat and SnapEnchance with emulators? I used Nox with kitsune (Nox emulator being the only one I could use Magisk on) but now I can't even login on Vainilla Snap with any emulators.

@mzashh
Copy link

mzashh commented Feb 14, 2024

@Verequies thats weird, USB debugging or adb service seems to have no effect for me. i can login fine. the login issues is caused by a variety of different reasons, be it a device ban, play integrity issues, or in your case usb debugging. and the method i provided is a universal solution, definitely not a convenient solution but one that should definitely get you logged in for the time being.

@computer-catt
Copy link

I've had this issue a bit ago, the issue was that i had been trying to log into my account with the wrong password

@VendorAttestation
Copy link
Contributor

VendorAttestation commented Feb 18, 2024

[Current Known Causes]:

Semi-Bypassing (Won't ALWAYS WORK) AS of 12.69 + there is a new Token so use this version to Bypass alot of detection then upgrade:

[Recommended Rooting Option]:

@Calamardins
Copy link

I was able to log in with an old phone while failing play integrity using dual messenger, with the main app I got the too many attempts msg but I was able to login in with the dual version, someone more skilled than me should look into this and the possibility of using apps like pararell space to bypass the login, I just did it by plain luck while playing around I got no technical knowledge.

@zenveh
Copy link

zenveh commented Feb 23, 2024

Hi all, not too techy here but ive had this problem and just managed to fix it.
I am on a samsung s21 ultra normal stock ui and all, unrooted.
The account wasnt blocked as worked on separate unmodded phone, and normal play store snapchat worked
This problem occurred for me when i tried updating it.
I deleted both snapehance and snapchat(dont keey the files it asks if you want to otherwise itll be a pain to fix)
got newest stable builds apk of both
Install snapehance and toggle off all settings /anything changed
Turn off USB debugging (not my idea i read it here, dont know if turning off all snapenhance modules or this fixed it, maybe both)
I used lspatch and shizuku, shizuku works with wireless debugging
Use lspatch to install the mod, i didnt enable the option to downgrade as didnt want to risk it, dont know if it works
I believe thats all i did, i hope this helps others, ill try and help any more if can.
Gave me an error saying password was wrong which is odd because i know it's right, but just used phone number to login and all was well, toggled everything back on and works fine.

@Techwizz-somboo
Copy link

@Verequies thats weird, USB debugging or adb service seems to have no effect for me. i can login fine. the login issues is caused by a variety of different reasons, be it a device ban, play integrity issues, or in your case usb debugging. and the method i provided is a universal solution, definitely not a convenient solution but one that should definitely get you logged in for the time being.

This fixed it for me too!

@devilbager
Copy link

I was able to fix it by pressing the "optimize app" button with LSPatch with the newest snapchat version from the play store.

@bocajthomas bocajthomas unpinned this issue Mar 25, 2024
@authorisation authorisation changed the title bug: Sign-in problem Sign-in problem Mar 26, 2024
@bocajthomas bocajthomas pinned this issue Apr 2, 2024
@bocajthomas bocajthomas unpinned this issue Apr 5, 2024
@bocajthomas bocajthomas pinned this issue Apr 5, 2024
@FlashNUT
Copy link

FlashNUT commented Apr 8, 2024

Hi guys. I am not as good as you are at these kind of things but what seemed to work for me was to create a new account after i installed snapchat and apply snapenhance to it. after i created that account i could easily change the account and it worked. Also i am on non rooted.

@bocajthomas
Copy link
Contributor

Hi guys. I am not as good as you are at these kind of things but what seemed to work for me was to create a new account after i installed snapchat and apply snapenhance to it. after i created that account i could easily change the account and it worked. Also i am on non rooted.

People Don't want to create a new account on each update 😒

@FlashNUT
Copy link

FlashNUT commented Apr 8, 2024

Hi guys. I am not as good as you are at these kind of things but what seemed to work for me was to create a new account after i installed snapchat and apply snapenhance to it. after i created that account i could easily change the account and it worked. Also i am on non rooted.

People Don't want to create a new account on each update 😒

well yes but. I created a new gmail adress and you can create as many snapchat accounts as you want with that email. after you create a snapchat account with that email you can log with your original snapchat account that you wanted to use without getting that error.

@authorisation authorisation mentioned this issue Apr 9, 2024
4 tasks
@Eatham532
Copy link

Closing the app and reopening worked for me. I have also tried changing the password not sure if that impacted

@krone0001
Copy link

whats the latest fix for 2.0 cuz its doin it to me

@Eatham532
Copy link

whats the latest fix for 2.0 cuz its doin it to me

Try to quit the app from the app drawer and reopen it.

@shaunbharat
Copy link

I fixed this by going into developer settings and explicitly turning off wireless debugging. Then I logged in using my number instead of my username.

@NicoaraAlex
Copy link
Contributor

I found a workaround, it's simpler and it works for me: before logging out, I deactivate SnapEnhance from the LSPosed application, close and open the snap (in the bar) until the SnapEnhance settings wheel disappears, then log out or delete the memory on Snapchat. When I log in, I do the same, I activate SnapEnhance after logging into my Snapp account.

@amandy85
Copy link

@authorisation how to/where to run script? the other solution did not work for me.

Run it as a script using v2
Script is patched, here's the unobfuscated version.

loginfix.zip

🚨where to run that script ❓❓❓❓

@authorisation
Copy link
Collaborator

@rhunk found some new ancient magic spell. Try this out if you're having issues on a custom rom.

loginfix_v2_obfed.zip

@Jacobfed1

This comment was marked as spam.

@authorisation authorisation mentioned this issue Jun 14, 2024
4 tasks
@authorisation authorisation added discussion Discussions issue and removed low priority This is on the low priority list or still in discussion. Implementation is not guaranteed. labels Jun 16, 2024
@OctavXD
Copy link

OctavXD commented Jun 27, 2024

So any work around that actually work?

@fairy-root
Copy link

Here's the fix for non root users

When using Shizuku / LSPatch

After selecting which app you want to modify (in this case Snapchat)

  1. Choose Local not Integrated mode
  2. Disable (uncheck) SnapEnhance from the modules
  3. Login to Snapchat
  4. Back to LSPatch, enable the SnapEnhance module
  5. Force Stop Snapchat
  6. Open Snapchat, and you'll see it working.
  7. Enjoy.

@kamharry
Copy link

kamharry commented Sep 8, 2024

https://github.com/JingMatrix/LSPatch/actions/runs/10714678100

Use debug build

Patch with debug build and optimize in lspatch

@duffyduck00
Copy link

What version of snapchat are you using ? I have the big problem, that i cant even install the app on waydroid. I cant find the app in google playstore, cause playstore tell me, that snapchat isnt available for my device and if i try to install previous downloaded .apk file - nothing happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working discussion Discussions issue help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests