You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now, there is no way to set any retry timing when it comes to failing engagement calls. We've had users blocking tracking requests on certain apps via tools like Duck Duck go, and then see constant retries in the Apptentive SDK.
It would be awesome if we could either set how often the SDK tries to trigger another engagement call, or could even back off to be as aggressive / wait for next app launch / etc. Currently it looks like it just immediately retries after failing constantly and never stops.
Here's an example after a couple of engagement calls were blocks from DuckDuckGo:
duckduckgo_retry.mov
The text was updated successfully, but these errors were encountered:
Hey Team,
As of now, there is no way to set any retry timing when it comes to failing engagement calls. We've had users blocking tracking requests on certain apps via tools like Duck Duck go, and then see constant retries in the Apptentive SDK.
It would be awesome if we could either set how often the SDK tries to trigger another engagement call, or could even back off to be as aggressive / wait for next app launch / etc. Currently it looks like it just immediately retries after failing constantly and never stops.
Here's an example after a couple of engagement calls were blocks from DuckDuckGo:
duckduckgo_retry.mov
The text was updated successfully, but these errors were encountered: