Closed Deroido closed 3 years ago
here are more details. unmodified log, also with initialization
here's full verbose log
I repeat. I'm not using TEST mode yet. For now I can't share the build, but maybe this will be the case if we struggle to solve this.
@Deroido , In the logs I could see any calls our show methods. Could you double check that our ShowInterstitial
is being called.
We would also strongly recommend testing with Test ads first, to ensure that the integration is working correctly and then move to live ads if you would like.
I'm sorry. this was my mistake. I was checking rewarded ad availability by placement, and not adUnit ad it should be. Also the log still wasn't verbose. Now I can see ads. So lets forget about this.
But there are few things noticed. I'm not gonna create new thread yet.
With this (a little outdated) configuration everything works fine:
if I clock all UPDATE buttons Unity builds fine, but Xcode won't build with 1 unexpected error
please re-check that.
In some other configurations I could build but the app crashes right after MAX initialization: MAX CRASH.txt
As for now I'm gonna rollback some mediation versions and check stability with each one. We use Applovin, Adcolony, Facebook, TapJoy, Inmobi, Admob, UnityADS. I can confirm that it's not Applovin and not Admob. Others are questionable. Could you comment on that behavior? If I found exact module causing this I will post it there.
It's unity ads causing crash on real device. Please check update from 3.4.6.0 to 3.4.6.2 Adcolony, Inmobi or TapJoy won't even let me build with unexpected failure. I don't have more time to check exact mediator causing this.
right now using this configuration which seems to work fine:
Hey @Deroido - you're right on that - we pushed out new adapters that fixes it, could you try again?
Hey @Deroido - you're right on that - we pushed out new adapters that fixes it, could you try again?
with all the latest adapters this unknown error still persists.
I will try to remove adapters one by one
this error was related to TapJoy Adapter.
previous version causes crashes in runtime *(on initialization) the latest version won't let me build in xcode.
@Deroido Good to know that you were able to narrow down on TapJoy Adapter.
Can you try the following:
@Deroido - Do you have any updates on your issue?
@Deroido - Do you have any updates on your issue?
Im sorry for long response. We've decided to exclude TapJoy from our iOS build. So no updates on that
Greetings. I've already implemented AppLovin MAX on Android, everything works fine. It's time for iOS, and as for now not a single ad was shown.
Here are details: Unity 2019.3.14f1, Xcode 11.5 iPhone SE (iOS 13.4.1) using latest MAX with latest adapters (Applovin, Adcolony, Facebook, TapJoy, Inmobi, Admob, UnityADS)
it looks like ad successful loaded but never shown.
this really doesn't look right
I'm not using this device in MAX Test Mode yet. Would Like to see any real ad 1st (not exact network).
So as far ad I can judge there's a problem with WebView and so UnityAds url looks like 'about:blank'. There are some guides in the internet corresponding to this problem, but they all require native code adaptation which is impossible with unity plugin.
Could you please help? I can share more info with real (not 'namespace') entries.