Hi,
Thank you for contacting the IMA SDK Support team.
The Error code 1009 refers to the VAST response document is empty. The errors are reported when there are no video files or tracking events included in a returned VAST response. Kindly ensure there are no errors with the start or end dates in the order or line item, and all targeted key-values are valid. Also, ensure that the correct ad units are targeted, and the size configured in the line item matches the size of the targeted ad units. For more information, kindly refer to the 1009 VAST error.
This error is not specific to the SDK but rather on ad configuration.
You can call the adsManager.destroy() when switching to a new video to clean up the currently playing ad. At any time, destroy can be called to end ad playback. There is no need to reinitialise the IMA SDK every time.
Could you check if the second VAST is showing an error too when playing first? or only after destroying is it failing. In case it's failing only after destroy then share both VAST with us including your code snippet.
IMA SDK Team |
Hi,
We are facing difficulties to reproduces the issue in our Google basic example project. Can you please provide a sample project which replicates the issue to investigate further.
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, kindly provide requested information to us via reply to author option or using the steps below:
1. Navigate to
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.
Hi,
Thank you for getting back to us.
After executing the basic sample project by replacing files that you have provided, the issue can be replicated when the SwitchNewVideo button is clicked a second time, but not the first time. Having said that, I will raise this as a bug and our engineering team will look into this issue. Once I get an update, I'll keep you posted on the same. I would recommend you follow our Android release notes for the latest updates.
Hi,
I've checked this with the team and found that this is working as expected. Where multiple requests to the same ad tag like the app is doing will result in empty VAST, since Ad Manager won't return the same ad multiple time since this would be a bad user experience.
The ad tag included in the test app looks to be a test ad since it says "VMAP preroll test". You may reach out to the Ad Manager team to configure their production ad tags to have multiple ads that can be returned.
Thanks
The adsManager.destroy() function is adequate for loading a new ad request, but as I recommended in a prior discussion, the fundamental cause of this problem is test ads, which may appear blank in rapid succession. You may contact the Ad Manager team to set up production ad tags to contain multiple ads that can be returned.