Hi,
During integration Google IMA PiP based on this documentation, found some issues where ads loaded on background in PiP mode will have noticeable delay between next ads or resume content. This issue will disappear when PiP mode with the watch page visible. Issue can consistently be reproduced on both physical devices and simulators.
Are we missing something or is this an SDK issue and can be solved?
Please refer to the attachment for modified example source code to reproduce the current issue.
Also, for uncompressed demo video, can be download here
Technical Detail:
- Using latest Google IMA SDK version 3.16.3
- Using Xcode 13.4 (13F17a)
- Demo using simulator iPad 9th iOS 15.4
How to reproduce:
Open AdvancedExample.xcworkspace from attached project
Run on iPad simulator (PiP only available on this simulator, otherwise using real device)
Taps VMAP Pods
On Watch page, during ads playing, go to home device (cmd+shift+h)
Observe ads load behavior
Thank you.
- Joni Cong
Hello Joni,
Michael here from IMA SDK Team. Thank you for reaching out to us.
I do not see any attached sample project that can replicate the issue, perhaps you forgot to attached it on your post. Would you be able to share that so we can further investigate? Kindly also share a screen recording of the behavior for better illustration of the issue specially on step 4 of reproducing it.
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
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.
Regards,
|
||||||
Hello Joni,
Michael here from IMA SDK Team. Thank you for reaching out to us.
This appears to be same issue with the one you have recently opened with us with also same subject title. That being said, please refrain from opening multiple threads with same concern for better tracking of the issue. We recommend to continue our communication on the previous thread as investigation of the issue on that is already being conducted.
Regards,
|
||||||
Hello Joni,
Thank you for sharing the requested details. I have raised the issue now to the rest of our team. We will provide more information once we get the result of the investigation.
Hello Joni,
Thank you for your response.
Here is the forum thread link that you previously opened. However, the original post from that thread appears to be deleted already. Nonetheless, rest assured that our succeeding responses on that thread are still valid and going through our support channel. As a matter of fact, I have responded there already and raised the issue to the rest of our team for further investigation. You may disregard responding here to avoid confusion on your end and let us continue our communication on the active thread mentioned.
Regards,
Hello Joni,
Thank you for your response. I will try to update you on the other thread for this reason and let us know if it is still visible on your end. If you did not receive any or this is a problem on your end, feel free to get back on this thread and we will make it the main thread instead for your convenience.
Regards,
Hello Joni,
First, I would like to let you know that the issue here is still being investigated. Additionally, responding here also as an update to know if this main thread for your issue is still available on your end. If not, you may disregard this message if found in the future, and we will update you on the other thread instead that is visible for you for your convenience.
|
||||||
Hello Joni,
Thank you for responding back to us. However, we still does not have significant information from the investigation we can share to you. I have already followed up on the ticket raised for this to get an update, we will get back to you the soonest possible.
Regards,
|
||||||
|
||||||
Hello Joni,
Hope you are doing fine. I just want to get back here as we already received feedback from our team.
This is currently a problem with iOS thread handling, where backgrounded threads are severely throttled, thereby slowing the rate at which the IMA can fire events or update state. Our team have been collaborating with Apple to try to produce a workaround for this problem, but at the moment it has to be considered a platform limitation.