joshzegers
joshzegers
@Shin-NiL I'm having this same issue for some users. I have never gotten one of these big banner ads on MY phone, but my friend (who has the same phone...
The update is not working for me as it is intended. So I switched to smart banners and, on the affected phones, it continued to display 320x100 banners. Next I...
I think there are plenty of ads in that size because that is typically all I see on my phone, it's just some random users only get the big ones....
UPDATE: Having issues now just in general displaying normal ads in release. Test ads always show up no matter the banner size, no matter if debug or release. Real ads...
Update 2: I upgraded the version of the google play services in the .gdap file which helped somewhat. The errors persist still when in release mode or when I have...
4.0.0 worked, yes. That's what I had been using for a while and it worked. This newest update has just had some weird effects. I'm doing both internal testing and...
Internal test is not debug mode, but it's signed differently; I couldn't find info on it being an issue for ads. In 4.0.0 I didn't try to show real ads...
The 12 errors I described: > In the default admob.gd, there are 12 signal connects that produce 12 errors if I leave them there, saying something like "signal X has...
Another update: The smart banners were working for a short time and are now back to showing the big 320x100 ads on affected devices. Also, I've been using Godot 3.2.2.