[Bug] Issue with Snapenhance feature

[erevos13]

Steps to reproduce/复现步骤

1. Patch snapchat with Snapenhance module
2. Go to user interface > message indicator > enable adds a lock icon next to the messages that have been sent only to you
3. Open snapchat, send a snap only to a single friend and ask them to send a snap only to you
4. Lock icon will not appear or will appear for the snap which you have sent but not for the snap u have received

Expected behaviour/预期行为

Lock icon appears for the snap which you have received i.e the person have send snap only to you

Actual behaviour/实际行为

But lock icon is not appearing

It was working on official lspatch but suddenly it stopped working because lspatch started crashing and switched to forked version
What i believe is patching conflicts or messing up with encryption keys ?

The se dev responded this but it is not working
"When you log in, it generates an encryption key pair and this is sent to Snapchat servers, so other users receive your public key and then they can send you encrypted snaps. Their encryption is slightly different, but the concept remains the same."
"The lock icon means that the Snap has been encrypted with fidelius encryption (usually between two users). If your friend has recently been added, the keys may not have been exchanged. Unfortunately I can't fix this, you can try reconnecting to your account that should regenerate those keys."

So can you take a look at it maybe lspatch is messing up with encryption?

Xposed Module List/Xposed 模块列表

SnapEnhance

LSPatch version/LSPatch 版本

0.6-421

Android version/Android 版本

14

Shizuku version/Shizuku 版本

13.5.4

Version requirement/版本要求

• I am using latest debug CI version of LSPatch and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Apk file/Apk 文件

No response

Logs/日志

Details

# Replace this line with the log / 将此行用日志替换

[JingMatrix]

Are you able to take logs using adb? Please first try the latest debug CI build, and then post your logs using

adb logcat -s AndroidRuntime LSPatch LSPosed LSPatch-MetaLoader LSPatch-SigBypass LSPosed-Bridge LSPlant LSPosedContext zygisk64 LSPlt Dobby LSPosedService '*:E'  > lspatch.log

Remember to keep catching your logs till that your issue appears.

[erevos13]

I ll check and post

[erevos13]

Which method to use when patching Snapchat with Snapenhance?
Loader dex enabled ?

[JingMatrix]

I suggest not to check the option Inject loader dex.

[erevos13]

Where are logs saved ? I am finding nothing

[JingMatrix]

The command here #15 (comment)
will save logs to a file lspatch.log.

[erevos13]

Thats what i am saying there is no lspatch.log file i am finding !?
Otherwise it usually saves log files in my platform tools folder but i am not finding it anywhere!

[JingMatrix]

Could you please test if adb devices shows your device?
If that is correctly setup, then adb logcat will print your logs on screen.

Please provide screenshot so that I can see the errors or problems.

[JingMatrix]

Provide the screenshots of your command so that I can help.

[JingMatrix]

Does this print anything on your screen:

adb logcat -s AndroidRuntime LSPatch LSPosed LSPatch-MetaLoader LSPatch-SigBypass LSPosed-Bridge LSPlant LSPosedContext zygisk64 LSPlt Dobby LSPosedService '*:E'

Once again, provide your screenshot.

[erevos13]

Does this print anything on your screen:

adb logcat -s AndroidRuntime LSPatch LSPosed LSPatch-MetaLoader LSPatch-SigBypass LSPosed-Bridge LSPlant LSPosedContext zygisk64 LSPlt Dobby LSPosedService '*:E'

Once again, provide your screenshot.

yes alot of things..
but i found out that when i unplug the device with command on after that lspatch log file is saved..
i am uploading it

[JingMatrix]

Instead of unpluging, you press Ctrl + C to terminate the recording of logs, which will then give you the log file.

[erevos13]

lspatch.log

[JingMatrix]

The uploaded log is not completed, please record sufficient time to capture the problem of current issue.