AppLovin / AppLovin-MAX-SDK-Android

Other
233 stars 104 forks source link

Why is the medium-sized native ad I created from the Applovin panel behaving like match_parent? #674

Closed omeratesss closed 2 weeks ago

omeratesss commented 5 months ago

MAX SDK Version

12.5.0

Device/Platform Info

Xiaomi 13 lite - android 14

Current Behavior

I created a medium-sized native ad from the Applovin panel. Then, I integrated this native ad into my project using Jetpack Compose. I saw the test ads, but I couldn't see them in the desired size. I couldn't see them in the 300x250 size as specified in the documentation.

Note: I previously suspected the AndroidView object, but I tested it with two different scenarios. 1 - I displayed native ads of the same size with Admost and Admob and got the correct result. 2- I created the TextView object found in the Android XML within the AndroidView and saw it on the screen as wrap_content.

Expected Behavior

The native ad object should come from the Applovin SDK in a 300x250 size. I shouldn't have to hard code and restrict it to my view with the size.

How to Reproduce

-Medium native ad was created in Applovin Panel.

Additional Info

Example of image with bug-> AndroidView( modifier = Modifier .fillMaxWidth() .wrapContentHeight(), factory = { nativeAd!! }, )

applovin-bug ` Must-have image-> AndroidView( modifier = Modifier .fillMaxWidth() .height(250.sdp), factory = { nativeAd!! }, )`

hardcoded

I will attach the relevant files below. I didn't create a sample project because I didn't write any additional code. ResultActivity.kt.zip

github-actions[bot] commented 3 weeks ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 2 weeks ago

This issue was closed because it has been inactive for 5 days since being marked as stale.