Keep a baseline you can run
Save the delivered source, dependency versions, setup notes, and tests. Tie them to the app version and package hash used during the work.
Keep a redacted example of each successful response. That baseline makes changed fields and new errors easier to spot.
Separate server changes from app changes
A server can change without a new APK. A new APK can also keep the same API behavior. Record both the app build and the date of a passing client run.
Test the existing client before assuming the whole integration needs to be rebuilt. Compare the calls that fail with those that still pass.
Check shared dependencies first
If many calls fail at once, review login, refresh, common headers, and request signing. If one call fails, review its path, inputs, body, and response shape.
Use request IDs and redacted logs to keep the comparison precise. Do not print credentials while debugging.
Change the smallest complete unit
Update the shared session flow when it changed, then run every call that depends on it. Update a response parser when fields changed, then test empty and partial data.
A patch is complete when the dependent workflow passes, not when one error disappears.
Use a repeatable update checklist
Start by recording the new package hash and version. Run the old client’s tests with a fresh allowed session. Keep the successful calls and the failing calls in separate groups.
Compare the shared flow first when all calls fail. Compare the endpoint and parser when one fails. Keep a redacted record of the request and returned error, including the time and server request ID.
After changing code, rerun dependent calls and their error cases. Save the client version, app version, test time, and result together. This record makes a later update a comparison instead of a fresh guess.
App build: package + version + SHA-256
Client build: source version
Session: fresh / refreshed
Calls passed: workflow names
Calls failed: error + request ID
Fix: changed request or parser
Retest: dependent calls + error casesKeep a change record
Write down the affected build, changed calls, test date, and result. Include a clear command to run the tests.
Open an update project with the new package and the failing workflow when you need specialist work.
Build what you need.
Upload your app. We extract its APIs and build your client.
Upload your app