[GH-ISSUE #302] 用Quicker里的AES加密后推送,Bark 收到通知解密失败 #267

Closed
opened 2026-03-03 11:42:03 +03:00 by kerem · 1 comment
Owner

Originally created by @FanXiangTM on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/Finb/Bark/issues/302

已确定密钥和IV都没错,却只能收到 "Decryption Failed"

Originally created by @FanXiangTM on GitHub (May 1, 2025). Original GitHub issue: https://github.com/Finb/Bark/issues/302 已确定密钥和IV都没错,却只能收到 "Decryption Failed"
kerem closed this issue 2026-03-03 11:42:04 +03:00
Author
Owner

@Finb commented on GitHub (May 6, 2025):

加密推送需要发送端和接收端,使用同一种加密方式和参数加解密,任何一端有差异都会解密失败。
我只能保证APP内复制出来的加密脚本,可以正常加密,同时APP可以正常解密。
第三方的实现是否正确无法保证

<!-- gh-comment-id:2852856412 --> @Finb commented on GitHub (May 6, 2025): 加密推送需要发送端和接收端,使用同一种加密方式和参数加解密,任何一端有差异都会解密失败。 我只能保证APP内复制出来的加密脚本,可以正常加密,同时APP可以正常解密。 第三方的实现是否正确无法保证
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Bark#267
No description provided.