Trace Token Logout Bug
Budget: $30 – $250 USD
My cross-platform mobile app keeps forcing a logout right after an order is placed or, at times, the moment the splash screen fades in. Somewhere in the call chain a request is coming back with 401 Unauthorized and the stored access token is subsequently flagged as invalid. I can reproduce the issue but haven’t been able to isolate the exact endpoint or piece of client-side logic that triggers it.
What I need from you:
• Instrument the app code and monitor every outgoing request so we know which API call first returns the 401.
• Verify that each request carries the token in the expected header/body format and that the refresh logic isn’t silently failing.
• Provide a concise report pinpointing the culprit (client implementation, expired/incorrect token, server signature mismatch, etc.).
• Patch the client-side code to prevent the unintended logout and confirm the fix with repeatable steps.
What I need from you:
• Instrument the app code and monitor every outgoing request so we know which API call first returns the 401.
• Verify that each request carries the token in the expected header/body format and that the refresh logic isn’t silently failing.
• Provide a concise report pinpointing the culprit (client implementation, expired/incorrect token, server signature mismatch, etc.).
• Patch the client-side code to prevent the unintended logout and confirm the fix with repeatable steps.