Placement ids aren't registered for Android about react-native-appodeal

[staskochkin]

Hello @zoftify. I've checked that plugin is sent placement from JS to Android native SDK. I think that this issue is not related to plugin logic. Please contact our support team via intercom or email [email protected]. It should be a more convenient way to solve it.

@staskochkin what I can see from the logs that we're always sending default placement:

2020-08-21 23:54:36.655 8761-8761/XXX D/Appodeal: Banner [Show]: isDebug: false, isLoaded: false, isLoading: true, placement: 'default', inPopup: false
2020-08-21 23:54:36.661 8761-8761/XXX D/Appodeal: SDK-Public [Appodeal]: show. Banner, result: true
2020-08-21 23:54:36.842 8761-8761/XXX D/Appodeal: Banner [Loaded]: Applovin - eCPM: 0.00, precache: false, expTime: 0, id: N2lWR...
2020-08-21 23:54:36.842 8761-8761/XXX D/Appodeal: Banner [Cancel]: Appodealx - eCPM: 10000.00, precache: false, expTime: 1680, id: NGZNW...
2020-08-21 23:54:36.843 8761-8761/XXX D/Appodeal: Banner [Notify Loaded]: height: 50dp, isPrecache: false
2020-08-21 23:54:36.843 8761-8761/XXX D/Appodeal: Banner [Show]: isDebug: false, isLoaded: true, isLoading: false, placement: 'default', inPopup: false
2020-08-21 23:54:36.880 8761-8761/XXX D/Appodeal: Banner [Network Error]: Appodealx - AdError: No fill

Here is my component:

<AppodealBanner
          placement={'home_screen_bottom'}
          style={{
            width: '100%',
            alignContent: 'stretch',
          }}
          onAdLoaded={() => {
            // LayoutAnimation.configureNext(LayoutAnimation.Presets.easeInEaseOut)
            setAdLoaded(true)
          }}
          onAdFailedToLoad={() => {
            // LayoutAnimation.configureNext(LayoutAnimation.Presets.easeInEaseOut)
            // setAdLoaded(false)
          }}
          adSize={size}
        />

As I said, iOS is perfect, the issue is only for Android...

[staskochkin]

@zoftify Thanks for log and code snippet. Looks like we missed placement for the AppodealBanner component on the Android platform. We will fix it in the next release.

[staskochkin]

Fix has been released in 2.7.4