I will diagnose or fix a bug in your lovable or supabase app


About this gig
Your app is nearly working, but login loops, data will not save, or a page goes blank after deployment.
I investigate a specific Lovable or Supabase issue, explain what is failing and, with a repair package, make a focused fix you can verify.
Typical requests:
- Sign-in, session or redirect problems
- Failed reads, writes or file uploads
- React errors and broken page behaviour
- Environment or deployment configuration issues
Please message me before ordering with the steps to reproduce the problem and the result you expect. I will confirm the scope and access needed.
DIAGNOSE: investigate one issue and provide findings and a repair plan. No code changes included.
FIX: repair one agreed issue and provide before/after checks plus handover notes.
FIX + TEST: the same repair with repeatable regression checks and a short walkthrough.
I am an Oxford maths graduate and hackathon winner.
Work starts in a local or staging copy. New features, redesigns and a full security audit require a separate scope.
Get to know Tom T
Oxford maths graduate, app and automation repairs
- FromUnited Kingdom
- Member sinceSep 2026
- Avg. response time1 hour
Languages
English, French
FAQ
What should I send before ordering?
Describe what fails, what should happen and the exact steps to reproduce it. Include a redacted screenshot or error message. If possible, share a sanitised code excerpt or repository summary. Please do not send passwords, API keys or private customer data.
Does the Basic package include a fix?
No. Basic covers investigation and a written repair plan for one issue. It is useful when the cause or repair scope is unknown. A code or configuration repair is included in Standard or Premium after we agree the scope.
Can you guarantee any bug can be fixed?
I assess the issue before accepting a repair package. Problems caused by third-party outages, unavailable access or undocumented dependencies may need further work. A diagnosis identifies what the evidence supports and any blockers; it does not promise a code fix.
Will you need my Lovable or Supabase password?
No. We can start with a sanitised export or repository copy. If access is needed, we will agree the least-privilege collaborator access to a development or staging project. Keep credentials out of messages and uploaded files.
Will you change my live app or database?
Work begins in a local or staging copy. Any live deployment or production database change needs a separately agreed scope and your approval of the tested change. Backups and an appropriate rollback plan must be in place before a live change.
What does one revision cover?
One round of corrections within the agreed issue and expected behaviour. A new feature, different bug, changed requirement or unrelated redesign needs a separate scope.
