How to Detect API issues in WatchOS Apps
Updated: Sep 24
Most of the watchOS apps will have a cloud back end and they communicate using APIs. Any failure in API calls results in bad user experience. It is very difficult for developers to get notified about any such API call issues once the app has gone live.
This is where Finotes comes in.
Once the API integration is complete, Finotes helps to detect API issues in watchOS apps. Finotes is capable of reporting issues in API calls from the app. For implementation details visit Finotes documentation for watchOS (Objective-C and Swift)
API calls from watchOS apps may fail because of the following reasons:
Server-side Application layer issues
Web Server issues
Wrong request parameters
Wrong request headers
Network and execution delays.
Here is a screenshot of a bug report of an API call issue in the watchOS app.
Finotes is capable of reporting API issues like status code errors, delay in API call execution, duplicate API calls. Data points like full URL of the request, URL params, request-response headers, request body are provided with issue reports in Finotes dashboard.
Such detailed reports will help developers to reproduce and fix these API issues fast.
Apart from API call issues, Finotes is capable of detecting crashes, frame rate issues, abnormal memory usage, NSException based crashes, function and feature failures. It also has the capability to report custom issues.
In case request-response headers contain sensitive information, Finotes provides a mechanism to mask such header fields at the client side itself. You can find the documentation here (Objective-c and Swift).