Android Profile ID Bugfix

₹600-1500 INR

Closed

Posted about 1 month ago

₹600-1500 INR

Paid on delivery

I have an Android app where each user is assigned an ID during registration. The backend stores the value correctly, yet inside the Profile screen ‑ specifically under the “bit” option label – the ID field stays blank. Everything else in the Profile loads as expected, so the problem looks isolated to how that single value is being pulled or rendered on the Android front end. What I need from you is a code-level investigation, a clear fix, and a quick test build that shows the ID appearing every time a profile is opened. Please untangle whatever is blocking the value (API call, mapping, or UI binding) and supply a concise note of what was wrong and how you resolved it so I can reproduce the change across branches. Deliverables • Updated Android source with the bug resolved • One signed APK for verification • Brief changelog or comments pointing to the fix I’ll give you access to the repo and a test account as soon as we start. Let me know if you need anything else to move forward.

Android App Development

Mobile App Development

Java

Software Architecture

Project ID: 40308381

About the project

1 proposal

Remote project

Active 5 days ago

Looking to make some money?

Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

Get paid for your work

Outline your proposal

It's free to sign up and bid on jobs

1 freelancer is bidding on average ₹1,050 INR for this job

@kuldeepsharma30

This is not a backend issue if the ID is stored correctly and other profile fields load, the break is almost certainly in mapping or UI binding on the Android side. I have debugged similar cases where a single field fails due to model mismatch, null handling, or incorrect view binding while the rest of the API works fine. My approach: * Trace API response vs model mapping (DTO → domain → UI) * Verify field key consistency (common issue: name mismatch or missing serialization tag) * Check null/default handling before render * Inspect ViewModel / state flow to ensure the ID is actually passed to UI * Fix binding (XML / Compose) so the value consistently renders I will provide: * Clean fix in source with comments at the exact failure point * Signed APK for quick verification * Short changelog explaining root cause + reproducible fix These bugs are usually small but hidden in flow, so I focus on isolating it fast without over-touching code. Before I jump in: Is your Profile screen using XML-based views or Jetpack Compose?

₹1,050 INR in 7 days