MikePendo
commented
2 weeks ago Hi @johntmcintosh, So just to be more clear I will try briefly explain how the pendo sdk works in terms of offline storage. Offline storage supports by default up to 10MB (FIFO)but can be configured to a different size on our BE (pendo mobile offline ). Then the SDK will send those analytics based on number of events OR time trigger OR immediate events. SDK should not start to collect analytics if it didnt get successful setup and start session and that based on your connection.
Your case is slightly different as the SDK detects available connectivity BUT when it tries to connect it get blocked by the host app. The error log is kinda explains it:
Error: '{
URL = "https://data.pendo.io/v2/devices/getAccessTokenSigned";
errorDescription = "No data received or bad JWT in access token request.";
httpErrorDescription = "An SSL error has occurred and a secure connection to the server cannot be made.";
httpErrorUnderlyingError = "The operation couldn\U2019t be completed. (kCFErrorDomainCFNetwork error -1200.)";
httpStatusCode = 0;
retries = 2;
}'The issue occurs here httpStatusCode = 0 that kinda not really valid status opcode and unfortunately we dont properly handle it. As a result SDK starts to collect analytics and attempts to process it. Although it still should properly handle 10MB I noticed that in some cases the allocated memory wasn't released within the proper time and that where you see those huge peaks in the memory usage
If its possible maybe you could share the sub id of the account it was crashing?
(I will verify the configuration for offline analytics).
Best practice would be:
-
verify that CNAMES are correctly configured and nothing blocks sdk connection
-
Setting max offline storage amount to reasonable value (please share the sub id so I could verify)
We will try to release a fix that will handle the case of status code 0
johntmcintosh
sigsbeym
Platform + Version iOS 17
SDK Version 3.3.1
Framework Native iOS, mostly UIKit with some SwiftUI
Describe the bug We observed a scenario that results in unbounded memory growth from the Pendo SDK when Pendo API calls timeout.
This problem initially manifest to us through reports of app terminations due to high memory usage. Here's a plot showing memory usage by the app over the course of an hour with and without Pendo's API calls timing out.
When the API calls timed out 100% of the time, we would see the app's memory growth climb from our typical 100 MB to 1.6 GB and then be terminated by the OS.
Our app is primarily used in restricted network environments. Although we are aware of the guidance on which hostnames should be allowed, one of our customers did not have Pendo hosts allowed, resulting in all API calls to Pendo being routed to the customer's internal network rather than to your API. These calls would eventually fail with timeouts.
In my testing, after launching the app with Pendo's API blocked by a proxy, starting a session, and triggering a few events, I observe Pendo getting stuck in an infinite attempt to get an access token. pendo-logs.txt has a snapshot of the logs that we see repeating every approx 30 seconds once this loop begins.
Our customers use the app continuously for 1-2 hours at a time, and during that time a significant number of screen change events are generated. My light investigation suggests that over time as more and more events are generated, each one in starting up more and more attempts to get an access token, and each attempt continues looping. Over time this eventually results in the memory growth shown in the graph above.
For our customers
To Reproduce Steps to reproduce the behavior:
data.pendo.iowith 100% packet loss.PendoManager.shared.setDebugMode(true)pendoManager.startSession(...)with a user's detailsscreenContentChanged()as screens change.Expected behavior We expect the SDK to be more resilient to failing network conditions and gracefully handle 100% packet loss without resulting in unbounded memory growth.
Logs pendo-logs.txt
Sample Code n/a