-
Notifications
You must be signed in to change notification settings - Fork 74
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
Clarification: How can I find how many autorefresh occurs for the Native and MREC ads views #394
Comments
@jesphinpt, can you provide the report showing a high number of ad fails compared to requests? Or can you provide the application package name and unit ID so we can look into the reports ourselves? as for these logs: |
@applovinAsh But I can see the real and test ads as well. Then how it showing this kind of logs? |
@applovinAsh I am getting an error as
|
I cannot identify why these errors could be thrown without the full verbose logs. It could happen because you made a native ad request before the view was ready, and by the time you show it, the view is available, so no issues are actually happening. I see that you opened a new github issue for the error you are seeing: #396. |
MAX SDK Version
13.0.0
Device/Platform Info
iOS
Current Behavior
I am getting a large number of adfailed error for Native and MREC ads. But the adRequest is low compared to the failed message. How can I find how many loading of ads happening in the app for Mative and MREC ads
Note: Test ad and real ads are showing as expected. but the adrequest is low and adfailed is too high.
I am using Native Manual Ads.
Clarify why this is showing like this
Loading ad 1 of 4 from APPLOVIN_NETWORK for NATIVE ad unit idddddddd
[AppLovinSdk] DEBUG [MANativeAdLoader] No custom view provided, checking template
[AppLovinSdk] DEBUG [MANativeAdLoader] No native ad view to render. Returning the native ad to be rendered later.
How to Reproduce
Add Native and MREC ads in the app, in the list page.
Reproducible in the demo app?
Not Tested
Additional Info
No response
The text was updated successfully, but these errors were encountered: