4ef36cc95c
Add logging to help track down problems with Sync
...
Seems like we're running into errors sending the message to kick off the
sync, so positive logging as well as error logging is included.
FREEBIE
8 years ago
675d41843e
Re-enable message box if enter pressed with no text/files
...
Previously the message would stay disabled until the user clicked with
the mouse.
FREEBIE
8 years ago
680f7d8b57
Additional logging for perf analysis and cross-device debuging
...
- How long it takes to get a message through the pre-send checks
- How long it takes to open a conversation for the first time
- The timestamp of any message we send to corellate with other logs
- Add conversation ID to 'decrypt old identity key errors' start/end
FREEBIE
8 years ago
241e26dc17
Don't revoke convo avatar URL on unload - we will need it again
...
FREEBIE
8 years ago
9c7db537d0
libtextsecure.js catch-up
...
FREEBIE
8 years ago
7e9ed1481b
Set receivedAt after decrypt, sort by received then sent
...
FREEBIE
8 years ago
620b71a649
Maintain original received time when processing queued/error msgs
...
FREEBIE
8 years ago
8700112f6d
Decrypt any IncomingIdentityKeyError still sticking around
...
FREEBIE
8 years ago
67cb9bdf54
Disable message box between send request and final send begin
...
Because we do a number of async checks before allowing the real send to
begin, on a slow matchine or when doing a lot of work (like receiving a
lot of messages) there can be a noticeable delay between hitting Enter
and the clearing of the text in the message box. In fact, newly-typed
text can be added to the previous message if the delay is long enough.
This prevents any interaction with the message box until the send has
either been prevented or has started.
FREEBIE
8 years ago
e7450fa0d7
Add a max setTimout for expiring messages (over max == immediate)
...
Discovered a user log where expiring message checks were happening
constantly. This ensures that a very large timeout doesn't roll over
into immediate callbacks.
FREEBIE
8 years ago
e57f155403
Handle rejections from protocol layer (due to missing records)
...
isVerified and isUntrusted both went to the protocol layer, but were not
prepared for rejected promises resulting from missing records. This
prevented send in large groups where there has never been a message
exchanged with one of the members.
FREEBIE
8 years ago
cf5f50cfab
Give initIncomingMessage envelope in background.js error handling
...
FREEBIE
8 years ago
b33c5c4c07
MessageReceiver: Wait for all code paths in handleSyncMessage
...
Without this, the recent changes to wait for read receipts and delivery
receipts don't have much of an effect.
FREEBIE
8 years ago
96b00b3e2d
Throttle expiring messages data query and deletion
...
I believe this to be the reason behind some of the high resource usage
on startup. If a lot of read receipts come in for disappearing messages,
this method can be called many, many times very quickly.
FREEBIE
8 years ago
6caf88c404
Key verification error popup: Remove cancel, empty resolve()
...
FREEBIE
8 years ago
2130795708
Fix 'retry message' scenario: they are now content messages
...
FREEBIE
8 years ago
e0c1f0d27a
MessageReceiver: Process cached before dismissing loading screen
...
FREEBIE
8 years ago
fa00f08c95
MessageReceiver: Fix envelope id logging and make it consistent
...
FREEBIE
8 years ago
82b2a611e3
MessageView: Always remove errors on re-render to prevent doubles
...
FREEBIE
8 years ago
78c02f1154
Restore 'cancel' button on delete message confirmation dialog
...
FREEBIE
8 years ago
559619eb49
Fix sync'd disappearing messages; prevent double-save
...
FREEBIE
8 years ago
7e8f3ab5e7
Fix for "Can't find record for undefined.1"
...
Also, we didn't need to recalculate the number here anyway!
FREEBIE
8 years ago
e223db56d9
Set messageKeysLimit to unlimited if communicating with our devices ( #1348 )
...
Set messageKeysLimit to unlimited if communicating with our devices
FREEBIE
8 years ago
7e0bd82bd3
handleDataMessage: Remove if(confirm) checks, add try/catch
...
FREEBIE
8 years ago
832b343031
Expiring messages: Add clarifying comment about destroy() ordering
...
FREEBIE
8 years ago
7d4ae63501
MessageReceiver: Log empty event, flow promise properly
...
FREEBIE
8 years ago
32e12f7d3c
Conversation.notify(): introduce a promise to track completion
...
FREEBIE
8 years ago
d3fb0e5b46
Expiring messages: destroy only after we've notified conversation
...
FREEBIE
8 years ago
7faf83bc01
Read/Delivery Receipts: Wait for resolution in main queue
...
FREEBIE
8 years ago
92ba295d52
Better logging for sync sent messages, and new (disappeared) msgs
...
FREEBIE
8 years ago
ad8cb870d9
libtextsecure.js catch-up
...
FREEBIE
8 years ago
ec70170829
ConversationView.unload: Add ability to provide reason for logging
...
FREEBIE
8 years ago
c0f8812f9b
ConversationView: when windows are closed, call unload()
...
Anyway, unload() is a more comprehensive method for doing what the close
handler was trying to do before.
FREEBIE
8 years ago
6f1a2a9b3e
Conversation.markRead() - wait for all database saves are complete
...
FREEBIE
8 years ago
b4f6721846
Fix manfest.css, libtextsecure.js catch-up
...
FREEBIE
8 years ago
65283d2794
Unload conversations and old messages every half-hour
...
FREEBIE
8 years ago
4ea457a01c
Fix second fetchConversation call if unread > 0
...
FREEBIE
8 years ago
8c231d9830
MessageReceiver: Flow promises back properly in decrypt error case
...
FREEBIE
8 years ago
31d7e652fe
Dismiss the app loading screen if we failed to connect to socket
...
FREEBIE
8 years ago
af2ce56c8d
Reset MessageReciever queue whenever possible
...
(like we do with the conversation queue already)
FREEBIE
8 years ago
305bd6b3b8
App loading screen: show messages processed so far
...
Also, show the same loading screen on index.js before we've bootstrapped
the app.
FREEBIE
8 years ago
e36aa524c9
background.js: Flow promises properly in error case
...
FREEBIE
8 years ago
39795170c1
Handle the 'extension loaded, reopen window' scenario
...
Not sure exactly how to think about Chrome app lifetimes, so we're
being conservative. We only show the full-application loading screen
once, on first display of the inbox.
FREEBIE
8 years ago
53f2bfbb57
Animated loading screens on startup and first conversation load
...
FREEBIE
8 years ago
3e8b34f3d0
findOrCreateById instead of private-specific method
...
Anyway, findOrCreateById with no type didn't succeed, because the
conversation didn't validate.
FREEBIE
8 years ago
ef3431af1b
isUntrusted: Return false if firstUse is true
...
Because users will see this upon first trying to communicate with a new
contact if they're quick about it.
FREEBIE
8 years ago
f38d715250
Read receipts: Log sender and timestamp when related msg not found
...
FREEBIE
8 years ago
c6bc167975
Increase log length to 5000, since we're logging so much now
...
FREEBIE
8 years ago
82c0b4aaa6
Add return to onContractReceived for consistency
...
FREEBIE
8 years ago
9dc406dc8d
Apply reliable trigger to Backbone.Collection as well
...
FREEBIE
8 years ago
Scott Nonnenberg