Skip to content

Commit

Permalink
Update MESSAGE_DECRYPTION_FAILED to [unable to decrypt]
Browse files Browse the repository at this point in the history
- This mostly reverts 089eb15, but downcases it for consistency with [blocked] and [left Org] messages
- With the last few commits since fda650a, the UI now displays deleted comments and posts in a special manner, without needing to rely on the encrypted message being corrupted/non-decryptable. As such, [unable to decrypt] should only be seen now when there truly is an unexpected issue with decryption
  • Loading branch information
High5Apps committed Aug 26, 2024
1 parent bff05c9 commit db51dbb
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion android/app/src/main/java/com/organize/AESModule.java
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ public class AESModule extends ReactContextBaseJavaModule {
private static final String KEY_ENCRYPTED_MESSAGE = "base64EncryptedMessage";
private static final String KEY_INITIALIZATION_VECTOR = "base64InitializationVector";
private static final String KEY_INTEGRITY_CHECK = "base64IntegrityCheck";
private static final String MESSAGE_DECRYPTION_FAILED = "[deleted]";
private static final String MESSAGE_DECRYPTION_FAILED = "[unable to decrypt]";
private static final String MODULE_NAME = "AESModule";

private static final int INTEGRITY_CHECK_LENGTH_BYTES = 16;
Expand Down
2 changes: 1 addition & 1 deletion ios/AESModule.swift
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ class AESModule: NSObject {
static let KEY_INITIALIZATION_VECTOR = "base64InitializationVector"
static let KEY_INTEGRITY_CHECK = "base64IntegrityCheck"
static let KEY_STRENGTH_256_BIT_IN_BYTES = 256 / 8
static let MESSAGE_DECRYPTION_FAILED = "[deleted]"
static let MESSAGE_DECRYPTION_FAILED = "[unable to decrypt]"

@objc
static func requiresMainQueueSetup() -> Bool { false }
Expand Down

0 comments on commit db51dbb

Please sign in to comment.