I am noticing a strange behaviour on my video playable (Applovin version) where the timeline restarts after the End Screen. It usually triggers if the app playing the video (in this case the Applovin Playable Preview App) goes in background and gets focused again.
On the screenshot you can see the EndScreen is showing but the timeline has restarted and I can interact with the first break again.
Some Applovin templates forces the app to go in the background so this means this issue would trigger most of the time my playable is shown.
I first thought this could be a bug on Applovin’s side but after testing with other Playables created from other services, only the PlayableMaker one showed this issue.
Hello, we just tested your last 5 builds on applovin preview on pc, android and apple and we cannot replicate this, can you share more information please? For example what broweser, what device etc, anything that might help us see the issue.
this issue happens with all of my builds. To test it, export one of the videos as an Applovin playable, then upload it to AppLovin Playable Preview . Then grab an Android or iPhone (the issue triggers on both), download the Applovin Playable Preview app and scan the QR code to test the playable there.
Any time while the ad is playing, send the app to the background and open it again. You’re going to see weird glitches (like two texts overlapping as if two Breaks were playing at the same time). It’s even more obvious if we you wait for the End Screen because it’s going to show the same thing as in my screen shot (End Screen + Break overlay at the same time).
thank you again for the input, your feedback is really helping out!
We have reviewed the issue, and found out that AppLovin calls twice the mraid.ready event, which is not right, nor correct, but we have to adapt to them, not the other way around:) .
The documented behavior is:
- We start the game on mraid.ready event
- Pause the game on mraid.viewableChange(viewable = false) event
- Resume the game on mraid.viewableChange(viewable = true) event.
After the Ad is shown again, they call the viewableChanged(viewable = true) event, but they eventually call the mraid,.ready event too.
This is the reason we start showing the overlays again. We have added and released a workaround to prevent initializing the event twice, we have now tested it on more than 20 builds and can confirm that your behavior is no longer happening.
We have triggered re-build for all your applovin playables, which means you can just download the packages from recent builds and get already working builds without spending more.
