Report a bug

A bug is iTweet behaving differently from how it is documented or designed to behave: a button that does nothing, a reel that will not upload, notifications that arrive twice, a screen that crashes, a counter that disagrees with reality, or text that overflows its container. If the product is working as intended and you disagree with the intent, that is feedback or a feature request — still welcome, but it travels a different queue.

Reports about content or people — harassment, spam, impersonation, illegal material — are not bugs. Use in-app reporting on the post, reel, comment or profile so moderators receive the context attached to the item. Account access problems are covered by our Account Recovery and "I can't log in" articles.

• Force-close and reopen the app, then try once more — transient network state causes a large share of reports.
• Confirm you are on the latest version from Google Play; fixes ship frequently.
• Try the same action on another network (Wi-Fi vs mobile data) to rule out connectivity or DNS filtering.
• Check whether it happens on a second device or on the web app — that tells us whether it is client-specific.
• Search the Help Center; known issues and their workarounds are documented as they are confirmed.

The builder above captures the fields our engineers actually need: the surface, severity, a one-line summary, numbered steps, and the expected versus actual outcome. Write the steps as if for someone who has never used the app — "tap the profile avatar, then Settings, then Notifications" beats "go to notification settings". If the bug is intermittent, say how often it reproduces and what you were doing immediately before it.

Add anything that narrows the search: the exact error text, a username or post link involved (yours, not someone else's), the approximate time it happened with your timezone, and whether it started after an update. Never include your password, one-time codes, backup codes or session tokens in a bug report — nobody at iTweet will ask for them.

A ten-second screen recording is worth several paragraphs, especially for animation, scrolling and playback bugs. Capture the whole screen so we can see the state of the tab bar and any banners. For crashes, a recording of the moments before the crash is more useful than the crash screen itself.

On the web app, open your browser's developer console and copy any red error text. On Android, an in-app diagnostics bundle is available from Settings → Help; it contains version, device model, locale and recent non-sensitive client logs. Blur or crop anything private before attaching — other people's names, DMs and phone numbers included.

Blocker — the app is unusable, data is lost, or accounts are inaccessible. Triaged the same day, worked continuously until mitigated. Major — a core feature is broken with no workaround; triaged within one business day and targeted for the next release. Minor — incorrect behaviour with a workaround; batched into a scheduled release. Cosmetic — visual and copy issues; grouped into polish passes.

Triage weights severity, the number of affected users, whether the report reproduces on our side, and whether a safety, privacy or billing surface is involved. Reports touching payments, private messages, account access or personal data are escalated regardless of the severity you selected.

iTweet AI acknowledges your report with a reference, deduplicates it against existing tickets, and routes it to the owning team. If we cannot reproduce it, you will get one specific follow-up question rather than a form letter. Confirmed bugs move to a fix queue; where a workaround exists we publish it in the Help Center while the fix is in flight, and release notes name the fixes that shipped.

Duplicates are not wasted. Volume on a single report raises its priority, so file yours even if it looks like something already discussed. Reports we choose not to fix are closed with a reason.

If you have found something with security impact — authentication bypass, access to another user's data, a way to defeat rate limits, a flaw in our encryption handling, or an injection — do not file it as a normal bug and do not post it publicly. Report it through iTweet AI and mark it as a security disclosure; it is routed to the security team on a private channel.

Please give us reasonable time to remediate before disclosing, test only against your own accounts, and avoid privacy violations, data destruction and service degradation. We do not pursue good-faith researchers who follow responsible disclosure, and we credit reporters who want to be named.

Android issues involving notifications, calls or background upload are often caused by battery optimisation or aggressive OEM task-killing — tell us your device manufacturer and whether iTweet is exempt from battery restrictions. On the web, note your browser, version and any content-blocking extensions, since blockers can break media playback and push registration. If you use the app through a VPN or a work-managed profile, mention it: filtered traffic looks like a platform bug from the inside.