Android应用AdMob广告Activity切换时加载延迟问题解决方案咨询
解决AdMob切换Activity时广告重新加载的空白问题
方案一:用弱引用预加载并复用AdView
通过全局弱引用管理AdView实例,既避免内存泄漏,又能复用已加载的广告,无需重构现有Activity架构:
object AdCache { private var cachedAdView: WeakReference<AdView>? = null // 预加载广告,建议在Application初始化或首个启动的Activity中调用 fun preloadAd(context: Context) { if (cachedAdView?.get() == null) { val adView = AdView(context.applicationContext).apply { adUnitId = "你的AD UNIT ID" adSize = getAdSize(context) loadAd(prepareAdRequest()) } cachedAdView = WeakReference(adView) } } // 获取缓存的AdView,若已被回收则重新创建并加载 fun getOrCreateAdView(context: Context): AdView { return cachedAdView?.get()?.apply { // 重新适配当前Activity的AdSize adSize = getAdSize(context) } ?: run { val adView = AdView(context).apply { adUnitId = "你的AD UNIT ID" adSize = getAdSize(context) loadAd(prepareAdRequest()) } cachedAdView = WeakReference(adView) adView } } private fun prepareAdRequest(): AdRequest { return AdRequest.Builder().build() } private fun getAdSize(context: Context): AdSize { // 保留你原有的AdSize计算逻辑 val display = (context as Activity).windowManager.defaultDisplay val outMetrics = DisplayMetrics() display.getMetrics(outMetrics) val widthPixels = outMetrics.widthPixels.toFloat() val density = outMetrics.density val adWidth = (widthPixels / density).toInt() return AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize(context, adWidth) } }
在Application的onCreate中触发预加载:
class MyApp : Application() { override fun onCreate() { super.onCreate() AdCache.preloadAd(this) } }
修改原有的initAds方法,直接复用缓存实例:
override fun initAds(activity: Activity, adLayout: LinearLayout) { adLayout.removeAllViews() val adView = AdCache.getOrCreateAdView(activity) // 移除之前的父布局(如果存在) (adView.parent as? ViewGroup)?.removeView(adView) adLayout.addView(adView) }
方案二:用保留实例的Fragment承载广告
创建带实例保留属性的广告Fragment,让AdView在Activity切换时不被销毁:
class AdBannerFragment : Fragment() { private lateinit var adView: AdView override fun onCreate(savedInstanceState: Bundle?) { super.onCreate(savedInstanceState) retainInstance = true // 核心:保留Fragment实例 adView = AdView(requireContext()).apply { adUnitId = "你的AD UNIT ID" adSize = getAdSize(requireContext()) loadAd(prepareAdRequest()) } } override fun onCreateView( inflater: LayoutInflater, container: ViewGroup?, savedInstanceState: Bundle? ): View? { return adView } private fun prepareAdRequest(): AdRequest { return AdRequest.Builder().build() } private fun getAdSize(context: Context): AdSize { // 同原有尺寸计算逻辑 val display = (context as Activity).windowManager.defaultDisplay val outMetrics = DisplayMetrics() display.getMetrics(outMetrics) val widthPixels = outMetrics.widthPixels.toFloat() val density = outMetrics.density val adWidth = (widthPixels / density).toInt() return AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize(context, adWidth) } }
在需要展示广告的Activity中,复用该Fragment:
override fun initAds(activity: Activity, adLayout: LinearLayout) { adLayout.removeAllViews() val fragmentManager = (activity as AppCompatActivity).supportFragmentManager var adFragment = fragmentManager.findFragmentByTag("AD_BANNER") as? AdBannerFragment if (adFragment == null) { adFragment = AdBannerFragment() fragmentManager.beginTransaction() .add(adLayout.id, adFragment, "AD_BANNER") .commit() } else { fragmentManager.beginTransaction() .replace(adLayout.id, adFragment, "AD_BANNER") .commit() } }
注意事项
- 弱引用方案:内存紧张时缓存的AdView可能被GC回收,此时会自动重新加载,但空白概率远低于每次重建。
- Fragment方案:需确保Fragment不持有Activity强引用,避免内存泄漏。
- 两种方案都要测试不同屏幕尺寸的适配,保证AdSize正确。
内容的提问来源于stack exchange,提问作者Tom11
相关产品推荐
相关产品推荐

