I’ve noticed an issue with the AdMob Native Ads component in Kodular.
I'm not sure It's bug or my mistake (Please confirm to me). As I understand It's bug for now.
So issue is, When an ad served from AdMob is image-based (non-video ads), everything displays correctly — including the heading, body text, call-to-action button, and icon - with image component.
However, when AdMob serves a video-format native ad, the component shows an error View Issue button.
It seems this happens because the current implementation only supports linking an Image component for the ad’s media asset (icon or image). When a video ad is returned, AdMob tries to send a MediaView instead of an image, which the Kodular component cannot handle — leading to the error.
So in short:
Image-based ads (non-video ads): Display perfectly (heading, button, icon, and body text).
Video-based ads: Show an error because the component expects an image instead of a MediaView.
It would be great if you could update the Native Ads component to support MediaView & Image (Both) or handle video ads gracefully without showing an error.
You’re partially correct but according to Google’s AdMob Native Ads, native ads can include videos — not just static images.
Google’s SDK provides a special view called MediaView, which automatically handles both image and video creatives.
So yes — Native Ads do support videos at the SDK level.
Was created to support AdMob Native Ads, it should handle all native ad formats as intended by AdMob’s SDK, instead of working only partially.
So, I kindly request @Diego to keep this issue as a bug or enhancement request in your Bug tracker, so that in future updates, the component can fully support both image and video native ads.
It might directly handle inside any view component instaed of just image component, It can use components like (Arrangements/Cards) which can handle any image and video inside OR Write code to handle internally as Google SDK provide MediaView