Fix 'retry message' scenario: they are now content messages
FREEBIE
This commit is contained in:
parent
e0c1f0d27a
commit
2130795708
2 changed files with 2 additions and 2 deletions
|
@ -39434,7 +39434,7 @@ MessageSender.prototype = {
|
||||||
},
|
},
|
||||||
|
|
||||||
tryMessageAgain: function(number, encodedMessage, timestamp) {
|
tryMessageAgain: function(number, encodedMessage, timestamp) {
|
||||||
var proto = textsecure.protobuf.DataMessage.decode(encodedMessage);
|
var proto = textsecure.protobuf.Content.decode(encodedMessage);
|
||||||
return this.sendIndividualProto(number, proto, timestamp);
|
return this.sendIndividualProto(number, proto, timestamp);
|
||||||
},
|
},
|
||||||
|
|
||||||
|
|
|
@ -144,7 +144,7 @@ MessageSender.prototype = {
|
||||||
},
|
},
|
||||||
|
|
||||||
tryMessageAgain: function(number, encodedMessage, timestamp) {
|
tryMessageAgain: function(number, encodedMessage, timestamp) {
|
||||||
var proto = textsecure.protobuf.DataMessage.decode(encodedMessage);
|
var proto = textsecure.protobuf.Content.decode(encodedMessage);
|
||||||
return this.sendIndividualProto(number, proto, timestamp);
|
return this.sendIndividualProto(number, proto, timestamp);
|
||||||
},
|
},
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue