I've replaced your manifest editor snippet with:
CreateResourceFromFile(Macro, FirebaseAnalytics.GooglePlayBase)
CreateResourceFromFile (Macro, FirebaseAdMob2.FirebaseAds)
AddReplacement($ADMOB_APP_ID$, ca-app-pub-1267570815929340~6761974519)
It now works. Note that it is better to use the updated macro in FirebaseAdMob2 instead of FirebaseAdMob, though it isn't the cause of the crash.
If you check the unfiltered logs carefully (it will be simpler in the next update of B4A) then you will find this:
09-21 09:27:26.038 16242 16242 E AndroidRuntime: FATAL EXCEPTION: main
09-21 09:27:26.038 16242 16242 E AndroidRuntime: Process: b4a.example, PID: 16242
09-21 09:27:26.038 16242 16242 E AndroidRuntime: java.lang.RuntimeException: Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException:
09-21 09:27:26.038 16242 16242 E AndroidRuntime:
09-21 09:27:26.038 16242 16242 E AndroidRuntime: ******************************************************************************
09-21 09:27:26.038 16242 16242 E AndroidRuntime: * Invalid application ID. Follow instructions here: *
09-21 09:27:26.038 16242 16242 E AndroidRuntime: *
https://goo.gle/admob-android-update-manifest *
09-21 09:27:26.038 16242 16242 E AndroidRuntime: * to find your app ID. *
09-21 09:27:26.038 16242 16242 E AndroidRuntime: * Google Ad Manager publishers should follow instructions here: *
09-21 09:27:26.038 16242 16242 E AndroidRuntime: *
https://goo.gle/ad-manager-android-update-manifest. *
09-21 09:27:26.038 16242 16242 E AndroidRuntime: ******************************************************************************