v1.0.94 — Getting Your Account Back
Also on Google Play — same app, auto-updating.
Two of the fixes here reach people who never touch a proxy, and neither group could tell us about it: one has an app that never opens, and the other looks like the app simply lost their account.
Fixed: some devices bricked by 1.0.91 were still bricked, even on 1.0.92 and 1.0.93. The hotfix cured most of them, but not all — and the ones it missed had no way of saying so, because the app still just sat on the loading screen.
When 1.0.91 crashed part-way through updating its database, the changes it had already made stayed put, while the note saying "this database is now up to date" was never written. Every launch afterwards started the update again from the beginning and tripped over its own earlier work. 1.0.92 fixed the exact step named in the crash report it was written from — so anyone whose update had got one step further kept crashing, just on a different step.
Every step of the update is now safe to run twice, from any starting point, so a device still stuck comes back on its own. Nobody's data was ever lost: the update simply never finished. (From member logs on a Walmart onn 4K box and a Galaxy S23, both still crashing after the 1.0.92 fix.)
Fixed: signing out and back in left your profiles, favourites and history behind on the server. You would sign in, everything would check out, and the app would ask you to set up a profile as though the account were brand new. Signing in again changed nothing, because the problem was not the sign-in.
Your device keeps a bookmark saying how far through your account's changes it has read. Signing out correctly wiped the local copy of your stuff — but left the bookmark at the end, so the next sign-in asked the server "what's changed since I last looked?" and the honest answer was "nothing". Everything was still safely on the server the whole time; the app was asking the wrong question. The bookmark is now cleared along with the data it describes, and devices already stuck this way heal themselves on the next sync.
SOCKS5 proxies are now supported, not just HTTP ones. Settings › Network › Proxy has an HTTP / SOCKS5 switch. SOCKS5 is what most people are actually given when a network blocks something outright, and it has a second advantage that matters here: it looks addresses up at the proxy, so it still works when the network's DNS is the thing doing the blocking — the single commonest reason a provider appears unreachable.
It covers everything the app does: signing in, channel lists, the guide, artwork, and video. Video needs a word of explanation — neither player engine can speak SOCKS5, so the app's built-in relay carries it, automatically, with nothing extra to switch on. HTTP and SOCKS5 keep their own address, port and sign-in details, so switching between them never mixes the two up.
You can now set up a proxy from the sign-in screen, before you sign in. If your network blocks your provider, the proxy setting was the thing that would have saved you — and it was locked behind signing in, which was the thing you couldn't do. There is now a Behind a proxy? Set one up button on that screen, and if sign-in fails for a network reason the way out appears right under the error. The button doubles as a status, so a proxy left switched on can never be a silent surprise.
Signing in no longer pretends your account is empty when KwickSync can't be reached. It used to drop you straight onto "Set up your profile", which looks exactly like losing everything. You now get told that sync couldn't get through, that nothing has been lost, and offered Try again — with the option to continue without it if you'd rather.
Fixed: the "Xtream Login" tab changed shape when you picked it. Selecting it added a tick that stole enough width to break the label onto two lines, so the tab visibly jumped as you moved across the row.
Installing keeps all your profiles, favourites, and history.