I cannot sign in
Wrong email. Your account is the email you registered with. If you bought a ticket as a guest with another address, that address has the tickets, not this one.
Temporary password. After Forgot password the email holds a temporary password. Signing in with it lands on a change-password screen, and the app stays there until you set a new one. That is expected, not a failure.
A code is being asked for. Your organization requires a second factor on this account. Enter the code sent to you; the device is remembered afterwards.
The Fast Login (Dev) button. Only exists in developer builds. If you see it you are not on a store build.
My ticket is not showing up
Email mismatch, nearly every time. Me → Edit profile shows the email you are signed in with; the confirmation email shows the one you bought with. If they differ, sign in with the purchase email or ask the organizer to reassign the ticket. If they match, pull to refresh. See Tickets for the paid-but-no-ticket case.
The schedule says "No sessions on this day"
The calendar opens on the first day that has sessions, so if you are looking at an empty day, tap a marked day or switch to the month view.
If every day is empty on an event that clearly has sessions, tell the organizer which event and that the schedule is blank. Until 2026-09-03 this happened for any event opened by its web address slug rather than its id — sessions, People and media all came back empty because the server looked them up by the wrong key. That is fixed; a blank schedule now means the organizer has not published sessions.
People is empty, or the profile shows an id instead of a session
Same root cause as the schedule, same fix date. If People is empty now, either the event has no participants yet or the request failed — the screen says which, and Retry appears on a failure.
Session names on a profile are resolved from the event's sessions. If you ever see a bare id there, the session was removed from the event.
"Couldn't load the feed" versus "No posts yet"
They are different. Couldn't load the feed is a failed request — the reason is under it and Retry reloads. It usually means no signal. No posts yet means the request worked and the event's page has nothing on it. Only the second one is worth posting into.
A comment failed with "Database operation failed"
Fixed server-side on 2026-09-03. The comment was in fact saved each time; a counter update after it was what failed, and the app showed that error. If you still see it, the server you are talking to is older than the fix — report it with the event name.
My like does not show
Also fixed on 2026-09-03, two ways: the feed is now fetched as you, so the server can mark what you liked, and un-liking now toggles the same reaction instead of adding a second kind. A tap should fill the icon and move the count; if it does not, the request failed and a toast says so.
A repost is a blank card
Fixed: reposts now show the original inside a box. If the box says the shared post is no longer available, the original was deleted.
The drawer lists the same event twice
Fixed. It happened when one ticket referenced the event by its slug and another by its id. If you still see it, both entries are the same event and either one works.
Chat is not live
Messages arriving late, no typing indicator, or the dot in the header off: the live connection dropped. Backgrounding the app, switching between venue Wi‑Fi and cellular, or a captive portal all do it. Sending still works through a normal request, so nothing is lost; reopen the app and the live feed reconnects. A message marked failed did not send — tap to retry once you have signal.
Payment does nothing on the web version
Card payment is only implemented in the iOS and Android apps. On a web build the payment step is a stub. Buy from the app.
Images are slow or blank at first
Event cover images are large files served through signed links. On a slow connection the card renders before the image arrives, so a blank cover that fills in later is loading, not missing. Ticket QR codes do not depend on those images.
Everything is slow
Screens fetch on open and the app keeps very little cached, so speed is your connection. Open what you need while you have signal, and avoid bouncing between tabs on venue Wi‑Fi.
Before asking for help
Have ready: the event name, the email you are signed in with, the email you bought with, and the exact words on the screen. "It does not work" takes several rounds; "No sessions on this day on Open Source AI Meetup, signed in as jane@…" takes one.