Maybe we have the same problems. Unfortunately I did not get a normal answer, I’m a semi developer of construct android ok, but construct ios problems((

construct.net/en/forum/construct-3/how-do-i-8/error-when-publishing-xcoda-ap-139131

github.com/Scirra/Construct-3-bugs/issues/2296

Does anyone import xcode on the App Store? Via the basic construct 3 Converter?

Scirra HELP!

yadi.sk/i/uXWuNaduLWRr8Q

The screenshot did not load, look at the screenshot on the link please

Conversion through construct 3 in xcode.

After trying to download, error.

How to fix?

Thanks guys! Admob plugin earned. In test mode for sure.

shortercode commented 12 hours ago

Okay I have released construct-mobile-advertssz@1.2.6 which is used by the C3 plugin Mobile Advert. As a point release it will be automatically available now.

The only change is to use version 16.0.0 of the admob SDK instead of the latest. This should work correctly, so you won't see the crash anymore.

If you do experience a crash or a build error please post it here and I will see if I can resolve it.

Thanks guys! Admob plugin earned. In test mode for sure.

construct.net/out

Bugs should be reported there.

Sent. But there are tickets already there, what could be wrong?

Yes. This problem also appeared. Today. Previously, this was not.

Who solved this problem?

Yes, I repead...Applications work fine, but if you add a plug-in Advertising, they stop working.

Applications work fine, but if you add a plug-in Advertising, they stop working.

I worked for many hours, I bought a subscription to construction 3, BUT applications do not work with AdMob.

SKIRRA, HELP?

java.lang.RuntimeException: Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException:

******************************************************************************

* The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers *

* should follow the instructions here: goo.gl/fQ2neu to add a valid *

* App ID inside the AndroidManifest. Google Ad Manager publishers should *

* follow instructions here: goo.gl/h17b6x. *

******************************************************************************

at android.app.ActivityThread.installProvider(ActivityThread.java:6084)

at android.app.ActivityThread.installContentProviders(ActivityThread.java:5560)

at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5499)

at android.app.ActivityThread.-wrap2(ActivityThread.java)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1608)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:165)

at android.app.ActivityThread.main(ActivityThread.java:6354)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:883)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:773)

Caused by: java.lang.IllegalStateException:

******************************************************************************

* The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers *

* should follow the instructions here: goo.gl/fQ2neu to add a valid *

* App ID inside the AndroidManifest. Google Ad Manager publishers should *

* follow instructions here: goo.gl/h17b6x. *

******************************************************************************

at com.google.android.gms.internal.ads.zzmn.attachInfo(Unknown Source)

at com.google.android.gms.ads.MobileAdsInitProvider.attachInfo(Unknown Source)

at android.app.ActivityThread.installProvider(ActivityThread.java:6081)

... 10 more