Help us improve Unjabbed
Find A Genuine New App BugAnd Get A One MonthPREMIUM FREE SUBSCRIPTION
Only the first confirmed report of a genuinely new technical fault qualifies. Known, duplicate, fixed and expected issues do not qualify.
Report a ProblemCheck before reporting
Known Issues
Look here first. You can still send extra information about an existing issue—it may help us solve it.
Google Play renewals were not always recognised
Some successful Google Play subscription renewals did not update paid access inside Unjabbed. This could temporarily lock paid features, including Who likes you, even though Google had processed the payment.
Resolved 13 August 2026: Paid access was restored for the confirmed affected members. Future renewals are now received automatically and checked directly with Google before access is denied. No Android app update was required.
An unsent web chat message could disappear after a refresh
An unfinished message in the web app could be lost if the conversation refreshed, including while viewing a member profile.
Resolved 8 August 2026: The web app now keeps each unfinished message with the correct conversation during a refresh and clears it after the message is sent.
PayPal checkout could fail to open in the web app
Starting a PayPal subscription could fail when the browser blocked the checkout hand-off or the returned PayPal address was unavailable.
Resolved 8 August 2026: PayPal checkout now opens safely from the member's click, checks that the destination is a secure PayPal address and shows a clear support message if checkout cannot start.
Web account deletion code could be replaced
Opening or reloading the Delete Account screen more than once could send a new confirmation code and make the earlier code stop working. The account would remain active when the older code was entered.
Resolved 31 July 2026: The current deletion code now remains valid for 10 minutes, and repeat requests resend the same valid code. This affected the web app; the Android app was not affected.
Android relationship status changes may not save
Selecting a different relationship status in Edit Profile can update the screen without sending the change to the server.
Being fixed 14 August 2026: A narrow repair has passed the app checks. Google Play beta delivery and a real-phone save check are still being completed before this is marked fixed. The web app is not affected.
No issues are currently listed as under investigation.
Reports being checked will appear here without identifying the member who reported them.
No individual items are listed yet.
This section will explain common experiences that are expected behaviour or normal dating outcomes rather than app faults.
Tell us what happened
Report an app problem
Please be specific. Screenshots and short screen recordings are optional, but they can make the problem much easier to understand.
Help shape Unjabbed
Suggest and Support New Features
Share a clear idea, see approved suggestions and upvote the ones you support.
Member ideas
Approved feature suggestions
Upvote any idea you would like Unjabbed to consider. One verified email address can have one vote on each suggestion, and you can withdraw your vote later.
Upvotes help Unjabbed understand what people want. They do not guarantee that a feature will be built. Repeated and automated voting is blocked.
Share your idea
Suggest a new feature
Check the approved suggestions first. If your idea is new, explain what it should do and why it would help.
Confirm your upvote
Enter your email so we can make sure each person votes once.
A fair, simple guide
Programme Rules
These rules explain what can qualify as a genuine app bug and how every report is checked.
A report may qualify when
- You are the first person to report the newly discovered fault.
- Our investigation confirms that something in the app is not working as intended.
- The issue is not already known, fixed or expected behaviour.
- Your report includes enough detail for us to understand and check it.
These are not app bugs
- Community size or the number of members in your area.
- Location coverage, personal preferences or lack of chemistry.
- Ghosting, unanswered messages or normal matching outcomes.
- A known issue, duplicate report, fixed issue or expected app behaviour.
How the programme works
Eligibility and decisions
Every decision must be based on the member’s real experience and the available evidence.
First verified report
Only the first verified report of a newly discovered technical fault can qualify.
Investigation comes first
We check what happened, the account state, device, app version and surrounding journey before deciding.
Three possible decisions
A report is recorded as not a valid app bug, a duplicate or known issue, or a valid new confirmed bug.
The thank-you
After a new valid fault is confirmed, the eligible member receives one month of Premium subscription.
Known, fixed or expected
Duplicate, known, fixed and expected behaviour does not qualify, but extra useful information is still welcome.
Accurate information
Please provide a genuine account of what happened and only share files you have permission to provide.
An original feature suggestion may receive the thank-you after release. If you are the first person to suggest it and Unjabbed later implements and releases it, you will receive one month of Premium subscription free. This can happen because strong member upvotes helped us choose it or because Unjabbed decided it was a good enough idea. Upvotes help us decide, but do not guarantee implementation.