Bug: ad-inspector fails to show test-ad of IronSource

[Liran Barsisa]

 When I try via the button of "request test ad", it gives me the error:

"IronSource requires an Activity context to load ads."

dependencies:

    implementation("com.google.android.gms:play-services-ads:23.6.0")
    implementation("com.google.ads.mediation:ironsource:8.6.0.0")

[Mobile Ads SDK Forum Advisor]

Hi Liran,

Thank for you contacting Mobile Ads SDK Support Team.

Kindly provide your app ID and adUnit ID by utilizing reply to author option for further investigation.
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGvLr:ref" (ADR-00284067)

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[Liran Barsisa]

I've sent you via "reply to author".

Also included information about other ad-sources and ad-types combinations that don't work and those that do work.

[Mobile Ads SDK Forum Advisor]

Hi Liran,

Thank you for providing us with the requested information.

What is the adapter error showing when you stated it does not work fine? If the problem is Adapter not found then check that you have installed the SDK adapter correctly. Learn more about  Android, If the problem is Initialization not completed then check that you have followed the integration instructions correctly. Learn more about  Android.  Check the documentation for your third-party ad source for specific initialization errors. Refer to the help center article on Issues with bidding ad sources for AdInspector do not work fine. No fill error means that the ad request was successful, but no ad was returned due to a lack of ad inventory. 

[Liran Barsisa]

It shows it started fine. The adapter is there, and it shows it got initialized, too. 

Otherwise it wouldn't have let me reach it and request a test ad.

And it wouldn't have shown an error that isn't about being initialized, but about not starting from an Activity when used via the ad-inspector.

Check the attached images. Your claims don't match what I've reported about.

Why would there be no ad available if it's a test ad? It should always return an ad, unless I request invalid ID or something else to force it to be an error.

Please check it better.

[Liran Barsisa]

Also I tried it today (with the screenshots I've provided) on an app that its optimization phase is over, and yet on the Admob website it says "no requests".

[Mobile Ads SDK Forum Advisor]

Hi Liran,

Thank you for sharing the screenshot of the issue.

No requests were made to this instance of the ad source. This could be due to:

• The mediation group priority is too low.
• This ad source instance is ordered too low in the mediation waterfall.

Requests are likely to be filled by higher priority mediation groups and ad sources that are higher in the mediation waterfall.  

[Liran Barsisa]

Please don't use AI to auto-generate responses to me. It didn't check the screenshot at all, and not even the title. It just copied from the docs:

https://support.google.com/admob/answer/3379773#status:~:text=this%20ad%20source.-,No%20requests.%C2%A0,-No%20requests%20were

From the title, you should know I demonstrated it via ad-inspector, which means it should force using this ad-source, and so it can't be related to priority/order, as it's what should be chosen.

From the screenshot, you should know the error isn't related to what you wrote, but about the ad-inspector not using Activity to request the ad.

Why would order or priority matter if it was manually requested by the ad inspector tool ? What's the point in using the ad inspector to force using an ad sources if it's not forced at all ?

And why would the adapter return an error related to Activity if you think it's something else ?