Android Bug Fix Report

A sign-in lasts 15 minutes before the app has to renew it, and the renewal ticket is single use — using it immediately invalidates it and issues a new one.

When you open the app, the home screen loads the chat list, contacts and unread counts at the same time. After 15 minutes all of them are refused at once, and each one independently tries to renew using the same ticket. The first succeeds and consumes it; the rest are refused — and being refused is what makes the app sign you out.

Session length      15 minutes
Renewal ticket      single use

Reusing a spent ticket:
  401 Invalid or expired refresh token

→ app treats this as "signed out"

Renewals are now serialised. Whichever request gets there first renews; the others wait, notice it has already been done, and carry on with the new session instead of trying again with a ticket that is already spent.

This is very likely also the cause of Bug_004 (friend requests not appearing) — that request would be one of the ones being silently refused.

1. Sign in, then leave the app closed for more than 15 minutes.
2. Reopen it. You must land on your chat list, not the sign-in screen.
3. Repeat after leaving it overnight.
4. Use the app normally for half an hour and confirm you are never signed out mid-use.

The app was forcing every image into a reduced 16-bit colour format to save memory. That format gives green one more bit of precision than red or blue, so photographs — skin tones and gradients especially — pick up a visible green cast and banding.

The same setting also discards transparency, so PNG avatars and stickers were being filled in with black where they should have been see-through. Worth checking as part of the same pass.

The reduced format is now only used when the device is genuinely short of memory and the image has no transparency — which is what the optimisation was meant to do. Normal photos keep full colour.

1. Send a photo with skin tones or a sky gradient — colours must look correct.
2. Compare against the same photo in your gallery, side by side.
3. Check an avatar or sticker with a transparent background shows no black box.
4. Check both the chat thread and the full-screen preview.

There was no relay server in production at all. A call could be created, but the audio and video had no route between the two phones. On mobile networks a direct connection almost never succeeds without one, so calls failed every time.

Worse, the app was being handed an address that pointed at the phone itself — so it was looking for the relay in the wrong place entirely.

A managed relay service is now connected and verified. A second fault was fixed alongside it: starting a call, then immediately starting another in the same conversation, used to be refused — which is exactly what happens when you try voice, it fails, and you then try video.

1. Two real devices on mobile data, not office Wi-Fi — Wi-Fi can mask this fault.
2. Place a voice call and confirm you can hear each other.
3. Hang up, immediately place a video call. Both must connect.
4. Try one call with the two devices on different networks (one Wi-Fi, one mobile).

The image uploaded fine — it could not be fetched back. Image downloads were being rejected as unauthorised. On top of that, images posted some months ago were saved with an address that no longer exists, from before the service moved domain.

Both are handled — downloads are authorised correctly, and old addresses are rewritten to the current one as they are served, so historic images become visible again. Verified against the live service.

1. Post a moment with a photo; it must appear immediately.
2. Scroll to older moments and confirm those images load too.
3. Check from a second account that the image is visible to other people.
4. Same check inside a chat — both use the same mechanism.

You are right, and we now know exactly how much is left. The previous round translated the sign-in, registration, password-reset and two-factor screens. Everything else still has its wording written directly into the code.

Screens still hardcoded : 48 files
Text needing translation: 528 strings

Worst affected:
  Help                    25
  Delete account          23
  Moments                 23
  Contact detail          22
  Minor mode              21
  Chat · Calls            18 each

528 strings across three languages is roughly 1,500 translations. It is straightforward but large, and mixing it into a bug-fix build would produce a change too big to review safely.

It is scheduled as its own release. The sign-in flow is already done, so the very first thing a new user sees is correct in all three languages.

On the next build, sign-in and registration will be fully translated; the rest of the app will still show Chinese. Please do not re-file the remaining screens individually — keep this one finding open to cover them all, and we will tell you when the full pass ships.