What's new

TetherBay 0.2.650 packages the latest documented beta improvements across relay resilience, network fallback, storage, and encrypted sync. A clip sent to one device could stop that device receiving any clipboard at all.: Addressed clips are served ahead of broadcast ones so that an earlier send cannot be skipped while it waits for its recipient. The query that does this dropped the cursor bound entirely, so an addressed clip the recipient neither applied nor dismissed was re-served on every poll and hid every later clip from that device until it aged out of the ten-event history. Clients in exactly that state are the norm rather than the exception: any build older than the dismissal route only advances its own c A clip this device cannot decrypt no longer blocks the ones behind it forever.: An event whose account key had not arrived held the cursor so a late key could still open it. Since addressed clips are served first, an event that would never open sat at the head of the queue indefinitely. The wait is kept but now ends after ten minutes, at which point the event is retired and the feed drains. Contact Clipboard failures are now reported instead of swallowed.: Every failure path in the feature was invisible once it left a developer's machine: the launcher logged breadcrumbs that never become issues and kept only the exception type name, and the server turned a database outage, a blob-storage failure or an unreadable stored grant into the same retryable error with nothing recorded anywhere. Infrastructure failures on both sides are now captured. Input validation stays quiet on purpose. A share link that fails on your own machine no longer blames the server.: When this device could not read or write the record that makes a link upload safe to retry, the app reported a server error code for a request it had never sent, and filed it alongside real relay outages. It now says that the link could not be prepared on this device, and is counted separately.