Hi Teejay, thanks for your reply!
Yes the issue occurs even after the ads have been loaded.
Let me provide more details:
In our app we notice the issue in:
- a screen containing a scrollview with 3 banners
- a screen with a UIPageViewController with a scrollview per tab, each scrollview containing a banner
We noticed only the upgrade of the AdMob sdk from 7.27 to 7.66 was triggering some frame drop when scrolling, even after the ads have been loaded, mainly on real devices like Iphone 7 or 8. Memory usage is however massively better (and congrats on that!)
To pinpoint the exact cause of the issue, I've created a dummy project with a scrollview containing 50 ads (this is quite silly of course, but it was to be able to easily reproduce the issue on the iOS simulator, and it provides similar results to what we were noticing on the production app)
I've provided 2 screen recording of the simulator and FPS profiling using Detox instruments (
https://github.com/wix/DetoxInstruments). In both scenarios:
- before the recording, I've made sure all the ads are loaded (scrolled to the bottom and back up to make sure they were)
- during the recording, I just make simple scroll gestures.
The "admob new version" recording is using version 7.66.0, you can see on the purple graph that whenever I scroll I consistently experience frame drops.
The "admob old version" recording is using version 7.29.0, there are consistenly no frame drop when scrolling.
With 7.66, memory usage is however 4 times better than with 7.29 (~150MB vs ~550MB for the 50ads)
I've also run a dichotomy to check what was the first admob version impacting the performance and surprisingly I've found 7.35 to be the first one (so long before the shift to WKWebView), by which I mean:
- I consistently experience no frame drops in 7.34
- I consistently experience frame drops in 7.35
Let me know if you need any additional information!
Thanks,
Alex