-
Notifications
You must be signed in to change notification settings - Fork 16
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
Doesn't work on Oreo for unknown reason #273
Comments
I'm thinking that this is the cause. It's a class not found on Oreo (only sdk 31+), but I'm unsure why snapchat is calling it when the module is enabled.
|
Never mind, that doesn't pop up anymore in the logs. Logs seem pretty bare minus some warning about the landing page error. I'm stumped on the issue. I've tried enabling and disabling various settings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I tried out snapmod today and I couldn't get it to work, at all. I'm using LSPosed zygisk (most recent version), the correct Snapchat version (snapmod downloads the brindings for it just fine and says everything is good). But, when I activate the module Snapchat gives me a dialog popup about it being a camera application and it needs access to the camera (which it does have the camera permission). If I touch "okay" then I get directed to settings for Device admin for whatever reason. I'm using a custom built rom (Resurrection Remix) on Oreo. There is nothing in the logs of LSPosed that is helpful, and I tried GravityBox and that worked fine so LSPosed is working fine in general. I do have the right Snapchat version, and I even downloaded from a different source just to see if that was the issue, and same results. It was a bigger one so it wasn't a fake (unless the bundle version should be used but seemed like everyone was using the apk version).
I attached my logcat collected as soon as I enable the module and navigate to snapchat. There is some stuff in there that looks like could be useful. I have no idea though and open to any suggestions for debugging. Thank you
logs-2022-10-16-19-13-51.zip
The text was updated successfully, but these errors were encountered: