“No Push Request Found” Due to Duplicate Retrieve Transaction Calls in Symantec VIP SDKs

Products

• VIP Service

Issue/Introduction

Symptoms

• Customers see “no push request found” errors when performing transaction retrievals.
• Issue observed on both Android and iOS platforms.
• Failed transactions are more noticeable than successful ones.
• Errors often occur shortly after an initial successful transaction approval.

Environment

Symantec VIP Android & iOS SDKs

Cause

The client application is issuing multiple retrieve transaction calls within a very short time window. The second (and subsequent) calls fail because the original push request has already been consumed by the first retrieval. This is an application-level behavior, not a server-side issue.

Additional contributing factor: Device clock drift can cause timestamp validation failures on push delivery.

Resolution

For Customers / Integrators:

1. Review application logic to ensure only one retrieve transaction call is made per push notification / transaction.
2. Implement the Reset Server Time API call to maintain proper clock synchronization.
3. Correlate failed retrievals with the preceding “authenticate credentials” call to identify timing patterns.
4. Only call Provision Device Certificate if using Device Hygiene / Root detection features.

Debugging Tips:

• Enable application-level debug logging (release builds do not contain SDK debug logs).
• Use VIP Manager transaction reports (available for authenticated credentials).
• Check time differences between authenticate and retrieve calls.

Prevention

• Ensure transaction flow follows the expected single-retrieval pattern.
• Periodically reset server time to avoid clock-related push failures.
• Validate integration against SDK best practices for push handling and transaction retrieval.