IMA SDK Making Duplicate Ad-Break Requests with sec-fetch-storage-access Header

[Aditi Gupta]

Hi team, 

We are facing an issue that the IMA SDK is consistently making duplicate HTTP requests to the same ad-break URL for every cue point. The only difference between the two requests is the presence of the sec-fetch-storage-access: active header in the first request.

Testing Done: We created a test application and verified this behavior occurs across multiple SDK versions:

• IMA SDK 3.36.0 with Media3 1.3.0

• IMA SDK 3.31.0 with Media3 1.3.0

• IMA SDK 3.35.1 with Media3 1.8.0  

The duplicate requests happen consistently in all tested combinations.

Network Analysis:
Using Charles Proxy, we confirmed:
• Both requests receive successful HTTP 200 responses
• Timing: Second request occurs immediately after first request completes
• Pattern: Occurs for every ad cue point in the VMAP
• Consistency: 100% reproduction rate across all test scenarios

Impact: This doubles the load on our ad-break endpoints and increases network overhead for our users.

Questions:
1. Is this expected behavior or a known issue?
2. Is there a configuration option to prevent these duplicate requests?
3. What's the recommended approach to handle this?

Please let us know if any other information is required from our end. I have attached screenshots of the charles request showing the same ad break calls. 

Thanks for your assistance.

Best Regards, 

Aditi Gupta

[IMA SDK]

Hi,

Thank you for contacting the IMA SDK Support team.

I checked our sample project using the VMAP sample tags and did not observe any duplicate ad requests. The ad requests were triggered at different cue points, and each ad request appeared to be unique.

To further investigate this issue on our end, could you please share the following:

• The VAST or VMAP tag you are using
• Charles logs showing the duplicate ad requests

This will help us analyze the request behavior and identify any potential issues.

Kindly provide the requested details via Reply privately to the author option.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=IMA+SDK&entry.460850823=500Ht00001u8QuKIAU&entry.80707362=00334779

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Thanks,
 

IMA SDK Team

Feedback
How was our support today?

               
[2025-10-07 15:02:13Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u8QuK:ref" (ADR-00334779)