-
-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testDevices should not be a prop #44
Comments
I think we can do it with a Native Module already present in the project and loading our configuration on app start. I will add this in the next release in a few days. |
This has been implemented for v0.3.0 |
@ammarahm-ed Thank. But I guess you haven't yet remove testDevices prop. The default value is an empty array which cancels out any previous calls to setRequestConfiguration. |
react-native-admob-native-ads/src/index.js Line 126 in c78aaea
|
fixed now. v0.3.1 |
As described in https://developers.google.com/admob/android/test-ads, the process of setting test device ids can be done only once, and after that all the ads, no matter if native, or banner, or other types, will be test ads. However, in this package the NativeAdView components have a testDevices prop, with the default of empty array. So I need to set the prop everywhere in the code I need an ad, instead of calling a function just once, e.g. in App.js or index.js. This is a bit inefficient and causes problems when using this package alongside other AdMob related react native packages.
I suggest to remove testDevices prop from NativeAdView and instead expose a function like the following, not only to fix the mentioned problems, but also to have full support of RequestConfiguration.Builder:
The text was updated successfully, but these errors were encountered: