-
Notifications
You must be signed in to change notification settings - Fork 28
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
QtFirebaseExample not showing ads #22
Comments
Hey @paoletto! Welcome to the project! 🙂 That's very much expected behaviour in the example app. This is all part of the way Google protect the ad-system against fraud. If you have added your device id to the test devices list this is pretty much what you get. However everything should work as expected if you do a release build via Google Play. I haven't been able to get video test ads on any of my development devices while in test mode - for unknown reasons. |
@larpon thanks for clarifying this aspect! i wish it was documented :-) |
@paoletto no problem :)
Yeah I understand your frustration. Unfortunately we can't keep up with documenting all the quirks of Firebase and AdMob as we support this in our spare time. Part of the problem is that both are (mostly) closed platforms hidden at some Google servers somewhere. So we only have Google's official channels and StackOverflow to figure out things if no one in our small user base has any suggestions. This specific issue you're having seem to be only present on some devices, configurations and Firebase SDK versions. (And in my personal setup as well!) Anyway - I hope everything works out for you and your project! |
Tried to throw in some guards against this in the README :) |
Qt 5.12.3
Device: F5122 w. Android 7.1.1
QtFirebase: latest
QtFirebaseExample: latest
firebase: 6.1.0
I followed the instructions, and succesfully built and deployed the app to an android device using a Qt 5.12.3.
However, the app only shows test ads, and the console permanently reports No Fill error (see attachments), even after tapping the reload buttons.
It would be good to at least know if the author can reproduce this problem locally.
The text was updated successfully, but these errors were encountered: