android: banner ad cropped when margin is large

[zipperdev]

Describe the bug
On Android, banner ad is cropped when the margin is bigger than (SCREEN_HEIGHT / 2) - BANNER_AD_HEIGHT, which is exceeding the center of the screen. This problem occurs at all sizes and all positions. (except BannerAdPosition.CENTER, because it does not apply any margin) On iOS, the ad is not cropped and the margin is applied properly.

To Reproduce
Steps to reproduce the behavior:

1. Show any size of banner ad
2. Set the ad margin to be bigger than (SCREEN_HEIGHT / 2) - BANNER_AD_HEIGHT
3. Ad is cropped on Android

Expected behavior
Banner ad should be moved properly without any cropping.

Screenshots

Normal behavior (iOS)

Bad behavior (Android)

when more margin is applied!

Smartphone (please complete the following information):

• Device: Samsung S24
• OS: Android 15 (One UI 7.0)
• Browser: Android System WebView 140.0.7339.51
• Version: SDK 35

Additional context (Reproduction code)

AdMob.showBanner({
    adId: "ca-app-pub-xxxxxx",
    adSize: BannerAdSize.MEDIUM_RECTANGLE, // any size
    position: BannerAdPosition.BOTTOM_CENTER, // any position
    margin: 250, // quite big margin
    isTesting: true,
});

[zipperdev]

By looking at the source code, it seems the Android margin implementation differs from the iOS.

Android margin implementation
iOS margin implementation

mAdViewLayoutParams.setMargins(sideMargin, densityMargin, sideMargin, densityMargin);

Android applies margins (densityMargin) to both the top and bottom regardless of the position,

rootViewController.view.addConstraints(
    [NSLayoutConstraint(item: bannerView,
            attribute: self.adPosition == "TOP_CENTER" ? .top : .bottom,
            relatedBy: .equal,
            toItem: rootViewController.view.safeAreaLayoutGuide,
            attribute: self.adPosition == "TOP_CENTER" ? .top : .bottom,
            multiplier: 1,
            constant: CGFloat(Int(self.Margin) * -1)),
        /// ...
    ])

whereas iOS applies a margin to only the top or bottom depending on the position property.

I don't think this is the intended behavior, but could anyone confirm if this is by design?