From 6b2d3f622e69c4082eaf215fd95c84e045e0caba Mon Sep 17 00:00:00 2001
From: Anton Urankar <124867229+antonurankar-moloco@users.noreply.github.com>
Date: Mon, 7 Sep 2026 16:13:00 +0200
Subject: [PATCH] Note that CloudX banner refresh can also be disabled
 server-side

StopBannerAutoRefresh was presented as the only way to keep the SDK's
refresh timer out of the pass cycle. A banner or MREC ad unit whose
refresh rate is 0 in the CloudX dashboard also reaches the SDK as
refresh-disabled at init, so say so, and say why the call stays: it makes
the cycle independent of how the unit happens to be configured.
---
 Assets/Scripts/FirstLook/FirstLookBannerController.cs | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Assets/Scripts/FirstLook/FirstLookBannerController.cs b/Assets/Scripts/FirstLook/FirstLookBannerController.cs
index a361fde..00532fc 100644
--- a/Assets/Scripts/FirstLook/FirstLookBannerController.cs
+++ b/Assets/Scripts/FirstLook/FirstLookBannerController.cs
@@ -382,6 +382,12 @@ private void CloudXCreateAndLoad()
          * native layer registers the ad unit as refresh-disabled even with no
          * view yet, then creates the view with refresh already off, so no timer
          * ever runs. (Destroy clears that registration, hence this order.)
+         *
+         * The ad unit can also be shipped refresh-off from the CloudX
+         * dashboard, which sends the SDK a per-unit flag at init. Keep this
+         * call anyway: it is what makes the cycle independent of the unit's
+         * configuration, and on a unit that already has refresh off it does
+         * nothing.
          */
         CloudXSdk.StopBannerAutoRefresh(_cloudXAdUnitId);