Build Failed with APK Ad Manager Error


Hi Kodular Support,

Please assist, I have been building my project for quite a while to almost completion, and I have come across this error as you see in the image above which I’m not sure how to resolve when I try to make a build of my app.
That said, I have searched the forums for a similar topic, and the only similar situation was for when there was not General Availability for Ad Manager, the solution was to sign up for an Ad Manager Account — which I do have currently. I have tried to re-import my app, same error. I currently have the 3 Kodular Ad units in my app (Banner Ad, Interstitial Ad and Reward Ad).

I’m only in testing phase and the ad units have been in my app in Test mode for quite a long time without any problem. They are also not placed in a way that they constantly fire off or annoy users — anything like that. This is an example block for an Ad failing to load:

blocks

This is my log for the app Build Fail:
Kodular is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________Creating provider_path xml
________Creating network_security_config xml
________Generating adaptive icon file
________Generating round adaptive icon file
________Generating adaptive icon background file
________Generating manifest file
.

I could be missing something obvious, but not sure what that is at this stage. Thanks for any assistance.

Is there already a solution to fix it?

1 Like

No, I’m still having the error. I was investigating to see if it’s a problem with my Google Developer account somehow, but I see now other users are having the same issue.

What I do know is that it only occurs if you use Kodular’s Banner, Interstitial or Reward units. I’m not sure why the error is occurring between Ad Manager and Kodular. I’m hoping to release my project soon using Kodular’s Monetization.

1 Like

Sorry, I have just pushed a hotfix for it. It should be working again.

7 Likes

Thanks Diego, after testing it’s working again.

@Diego please check my new app already approved by admanger i also need approvel from kodular? or not waiting for your replay

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Continuing the discussion from Build Failed with APK Ad Manager Error:

The same issue came again @Diego @Kodular please let us know what to do, are you working on this issue or this issue is from our side.

Any one got the solution of it @Diego , @Kodular, @Peter please help me to solve this problem

hello Diego,
Same Error is Appearing again. please check it at our side.

Hey, Even i have been experiencing the same Problem!

Same issue @Diego please fix it

Hi, can you please try again and see if the error persists?

1 Like

I’m unable to export with ad manager, without working fine.

Export stops here.

Kodular is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________Creating provider_path xml
________Creating network_security_config xml
________Generating adaptive icon file
________Generating round adaptive icon file
________Generating adaptive icon background file
________Generating manifest file
.

No @Diego still not working :expressionless:

Still facing same error. Mr @Diego please fix it.

I brought the premium just now and has same issue.

I have just updated the API version now, I believe it was already deprecated. Can you verify one more time?

It’s fixed now