Hi Joshua,
Thank you for bringing this issue to our attention.
Could you tell us what IMA SDK for iOS version you are using here? I saw cases reported to us related to audio ads issues while in the background. Thus, just to verify if this is similar to those cases, could you also share a screen recording of the behavior that you are seeing for our reference?
Regards,
|
||||||
|
||||||
|
||||||
Hi Joshua,
Thank you for reaching back to us. I’ve been looking for feedback on our team and it appears that they are still extensively working for the best solution to apply for this behaviour. For other solutions you’re requesting, let me bring this up to my team to talk about it and I will get back to you once I have their response.
Regards,
|
||||||
Hi Joshua,
I work with Sherwin.
It seems like we have not received feedback from the team regarding this issue but I already asked for an update on your behalf. For the meantime, keep an eye on our latest releases for possible updates.
Regards,
|
||||||
After getting these success messages, the IMAManager does not begin ad playback and outputs the following:
2. When an ad begins in the foreground and the app is put into the background, ____ tend to get delivered more slowly than usual. Non-ad content does not begin afterwards because the "complete" is never sent. This prevents the IMA SDK from triggering adsManager(didReceive event). The logs appear as follows:
No other output is received until the app is brought back to foreground.
Additional information:
IMAAdsRequest configuration:
Thanks,
Joshua Moore
Hi Joshua,
Thank you for getting back to us.
For your first scenario, this doesn't work because the content must already be playing before the app is backgrounded, not after. It's just that when you move to the background, iOS will pause the player, so you must manually call play on it again when that happens, to avoid a pause.
For the other query, I have raised this to the rest of the team and we will update you once they have responded.
Regards,
Hi Joshua,
To clarify, it is recommended that your content is already playing before requesting ads in the background, since otherwise iOS will most likely not let new video playback start in the BG if there currently is none. If the content is paused, and you try to request ads in the background, it will most likely fail.
On the other hand, for your other query before regarding if there is still a fix in the pipeline to handle ad playback on the iOS SDK in a background state, a fix for that is now live.
Please let us know if you still encounter any issues.
Regards,
Hi Joshua,
Thank you for your response.
Are you seeing the same current behavior using our sample apps? I believe as long as you have followed the guide on background audio playback, there are no others needed to be modified. It would be a lot of help if you could send us a sample project implementation where we could replicate the issue and/or a screen recording of the current behavior.
Regards,
|
||||||