Merge pull request #174 from HereLiesAz/claude/fix-mobileads-provider-launch-crash

Fix launch force-close: strip MobileAdsInitProvider from base manifest

Author: HereLiesAz

app/src/main/AndroidManifest.xml

@@ -40,6 +40,17 @@
             android:name="com.google.android.gms.fonts.API_KEY"
             android:value="${FONTS_API_KEY}" />
 
+        <!-- The Google Mobile Ads SDK lives in the on-demand :feature:ads split. AGP promotes its
+             auto-init MobileAdsInitProvider into the BASE manifest (tagged splitName="ads"), but some
+             devices still instantiate it at process start when the ads split isn't installed, hitting
+             a ClassNotFoundException and force-closing on launch. We initialize the SDK explicitly
+             (AdsFeatureImpl.initialize), so strip the auto-init provider from the base manifest. -->
+        <provider
+            android:name="com.google.android.gms.ads.MobileAdsInitProvider"
+            android:authorities="${applicationId}.mobileadsinitprovider"
+            tools:node="remove"
+            tools:ignore="MissingClass" />
+
         <!-- AdMob APPLICATION_ID meta-data now lives in the :feature:ads module manifest. -->
 
         <activity