Hello everyone! Extremely pleased to highlight a new feature in today’s release that I think is going to make troubleshooting your API integrations in Dropsource a lot easier - Network Logging.
With your app open in the simulator, switch on the Network Activity Log and check out the detail of what your API is doing when your app runs a request. Select the request (in the example below it’s the line that begins “json” and has a query string) and open Preview to see the structures the API is returning to the app.
Just a note that your log will clear when your Appetize session times out so to keep your info visible just interact with the virtual device when it displays “Inactivity Timeout” - this is something we’re hoping to improve in a future version of the feature.
You’ll find info on using the log in a couple of places in the help center - the interaction should be fairly familiar if you’re accustomed to using your browser dev tools:
I know from personal experience and from talking to our community members how much of a pain point figuring out what your requests are doing can be. What is Dropsource receiving, what is my API receiving, is the request running, is the data empty etc etc. In the past we’ve more or less had to rely on external tools such as Postman and Stoplight to troubleshoot these issues, but with this update we can get to the source of an issue without leaving Dropsource.
I’d love to hear what everyone thinks about this - try it and let us know how you get on! What problems can you see this helping to address in your projects? Is the network log easy to use or is there anything you find confusing about it? Anything else you’d prefer done differently?