Hi Team,
We are currently working on an iOS application built using SwiftUI, and we’ve integrated multiple Google Ads within a ScrollView. However, we’ve observed that the app becomes noticeably laggy or hangs while scrolling, particularly in views with embedded ad units.
After profiling, it appears that this issue stems from Google Mobile Ads SDK operations occurring on the main thread, which blocks UI updates and negatively impacts the scrolling performance.
We’ve tried optimizing the task execution using background threads (Task, Task.detached, and Task(priority: .background)), but since the SDK is largely main-thread-bound, the issue persists.
Could you please advise on the following:
Are there best practices for integrating multiple Google Ads in SwiftUI that minimize main-thread usage?
Is there any official guidance or configuration to offload ad processing from the main thread?
Are there any plans for improving SwiftUI performance support in upcoming SDK releases?
Any support or insights to improve the scrolling performance while using Google Ads in a SwiftUI-based app would be greatly appreciated.
Hi Puneeth,
Thank you for contacting the Mobile Ads SDK Support team.
I will check with our team regarding your queries and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.
![]() |
Mobile Ads SDK Team |
[2025-05-30 06:01:37Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rdn3F:ref" (ADR-00309111)
You can provide the following details via reply privately to the author option or below link.
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 follow using the steps below:
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.![]() |
Mobile Ads SDK Team |
[2025-06-06 21:28:50Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rdn3F:ref" (ADR-00309111)