Communications Debugging Tips That Help When You Get Stuck
summary
Practical debugging checklist for network problems in Android apps: log full exceptions and stack traces, inspect HTTP status codes and response bodies/headers, and reproduce requests on a PC to determine server vs client issues. Demonstrates tools and techniques: Charles for HTTPS interception, rewriting and mirroring; Postman and curl to reproduce requests; Android Studio Network Profiler and OkHttp logging interceptor for in‑app tracing; plus using mock JSON files and a local mock server to validate client behavior.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:26Common comms issues causes
- 2:52Basic troubleshooting
- 3:54Dev vs API dev views
- 5:47Basic comms failure checks
- 7:12HTTP status codes & exceptions
- 9:28Response validation & parsing
- 10:58Debugging tools overview
- 13:36Generic HTTP clients
- 15:08Comms tools benefits
- 16:39Web view communication checks
- 17:43Charles setup basics
- 19:55Charles troubleshooting
- 21:22Sending requests & responses
- 23:15Receiving responses & app code
- 24:46Environment factors & sharing
- 25:29Mock data for problems
- 27:17Summary & advice
- 28:26Debug tools by purpose
- 30:17Q&A
related talks
36mDAAS: Debugging as a skill!
37mDebugging Android Devices in the Field
33mDebugging: All You Need to Know
40mThe 2016 Android Developer Toolbox
53mThe 2016 Android Developer's Toolbox
37mAndroid Developer Options Deep Dive
38mBreak your App before Someone Else Does
22mEverything you ever wanted to know about error handling in Android