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

Can't login (rootless patched Snapchat signature problems) #1288

Closed
4 tasks done
KuVa187 opened this issue Oct 23, 2024 · 10 comments
Closed
4 tasks done

Can't login (rootless patched Snapchat signature problems) #1288

KuVa187 opened this issue Oct 23, 2024 · 10 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@KuVa187
Copy link

KuVa187 commented Oct 23, 2024

Description

After debloating my S22, I encountered a problem where Snapchat (and Twitter), both of which were patched, wouldn't open. I received an error message stating, "The app contains an error... blah blah." I figured out that the issue was related to LSPatch v0.6, the latest stable release version. I then tried ONPatch v0.0.7-alpha.2 from a Chinese Telegram channel (NPatch) and an LSPatch debug build from an LSPatch fork by JingMatrix (lspatch-debug-8fb330f), both of which fixed that problem.

The current issue, however, is that I can't log in, receiving the following error message: "Due to multiple sign-in attempts or suspicious activity, your access to Snapchat has been temporarily disabled." I tested various Snapchat versions, ranging from 12.63.0.55 to 13.12.0.37 (though not every single version in between), but all of them displayed the same error. I also tried the latest SnapEnhance debug build 7458d57 to see if that would resolve the issue, but it didn’t.

To ensure the problem wasn't with the APKs I got from APKMirror, I installed Snapchat without patching, and the login worked perfectly fine. I also tried local patching instead of embedded patching, but that didn’t work either. When I attempted this, it said the signatures didn’t match, so I had to uninstall the "normal" unpatched version of Snapchat to install the locally patched one. I think this might be a clue as to what’s causing the issue, but I’m not sure how to fix it. Does anyone have any ideas on how to get the signature right?

(This was rewritten by ChatGPT)

Reproduction steps

  1. Do some stupid debloating to irreversibly break something in OneUI 6.1 (Android 14)
  2. Install a debug build of LSPatch
  3. Download any Snapchat Apk from Apkmirror
  4. Download any version of SnapEnhance
  5. Patch the two together (embedded method) using LSPatch
  6. Install both the patched Snapchat and SnapEnhance
  7. Restart your device
  8. Open Snapchat and go through the SnapEnhance "setup"
  9. Type in your email and password
  10. Get error message

Logs

If you want to see logs of whatever, write me but I've checked them myself and didn't see any error both in SnapEnhance and in LSPatch.

Snapchat Version

any

SnapEnhance Version

any

Agreement

  • This is not a bug regarding Snapchat+.
  • I have provided a detailed description of the issue.
  • I have attached a log if deemed necessary.
  • This issue is not a duplicate.
@KuVa187 KuVa187 added the bug Something isn't working label Oct 23, 2024
@kamharry
Copy link

Open shizuku
Click on snapchat and optimize app

@kamharry
Copy link

Also wait for Snapenhance and snapchat to load like for 2-3 seconds and then try

@KuVa187
Copy link
Author

KuVa187 commented Oct 24, 2024

I already tried optimizing it and updating the loader (in LSPatch and not Shizuku). Then I restarted my device but it still didn't work. Just for the sake of trying I tried it again but nothing changed. Still the error "Due to ... blah blah ... suspicious blah ... access temporarily disabled".

@KuVa187
Copy link
Author

KuVa187 commented Oct 24, 2024

I tried them (for LSPatch both the release and debug version) but it still doesn't let me login. Probably unrelated but this debug version of SnapEnhance gives me an error when generating mappings "Method setCurrentState must be called on the main thread". This was not the case with the previous debug build (https://github.com/rhunk/SnapEnhance/actions/runs/11255829643).

@kamharry
Copy link

That error is normal
Open Snapenhance and regenerate mapping

@KuVa187
Copy link
Author

KuVa187 commented Oct 24, 2024

yeah but that still doesn't fix my issue

@rhunk
Copy link
Owner

rhunk commented Oct 24, 2024

#637

@rhunk rhunk closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2024
@rhunk rhunk added the duplicate This issue or pull request already exists label Oct 24, 2024
@KuVa187
Copy link
Author

KuVa187 commented Oct 24, 2024

I don't want to lean myself too far out the window but i don't think the people in issue 637 have the same problem as me. Ofc i didn't try everything suggested in that issue yet but force stopping the app (which worked for the other guy) didn't work for me. Oh and I have a question, do i need to tick the "overwrite version code" option in LSPatch or not? Because up until now i always did.

@kamharry
Copy link

Nah dont use override code until or unless u frequently downgrade or update snapchat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants