Repository navigation
Replies: 3 comments
|
AI description for Android login problem, works on my end, im going to sleep (2AM lol): Subject: Android login ec=28/E005 — root cause is the empty ta analytics blob (identity.go:629) I've found the cause of the "a device of its own gets tokens, but not a session" / ec=28/E005 wall on reconnect. Cause. internal/auth/identity.go builds the ta analytics blob only for iOS and sends ta="{}" on Android:
|
|
Hi @C485, thank you. The #32: Android
A guest login is accepted with either, so the gate applies to established accounts. As you suggested, #33: tokens refresh the way the 1.0.364 client does it. It refreshes before the login when #34: your flow, as one command. It logs in as a guest, verifies the email, logs the account's roles, trades the
On your question: I'll do the Go side myself. This login path has a lot of redaction and test hardening, and it was quicker to land it directly. What would help me most from you is evidence:
The world map in your screenshot looks great, by the way. |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm ready to implement full flow that doesn't require any spoofing at all.
The flow goes like this:
Tell me what you need, an AI instructions how to implement this or should i do it? I'm using ollama and opencode for this and i think that you're using clode.
Let me know, i can make PR but you need to take a look at it because i have 0 experience with Go
@ljagiello
All reactions