-
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
Native didPayRevenueForAd failing with timeout error for the Native Ads #396
Comments
@jesphinpt, -1001 errors mean that there was a timeout and an issue connecting to our server. Where are you testing from, and where did you experience this issue? Is this only happening for Native Ads? |
@applovinAsh Yes it is happening in the Native Ads alone. |
Can you provide the full, unfiltered or edited verbose logs from the start of a session so we can see what is going on? To enable verbose logs, see here: https://developers.applovin.com/en/max/faq/how-to-enable-verbose-logging-in-the-applovin-sdk |
@applovinAsh Kindly also let me know why the error messages are showing as the below and how can I make this to work. Why it showing bad request as a large number of counts.
|
@jesphinpt, thank you for providing the logs. Unfortunately, the provided logs did not show any issues with loading or showing the AppLovin test ad. While the issue with native ads is not present in the logs, I did see this error To help us understand why you are experiencing timeout issues, you will need to provide verbose logs from a session where you experienced the issue. |
This issue is stale because it has been open for 30 days with no activity. |
MAX SDK Version
13.0.0
Device/Platform Info
iOS
Current Behavior
When I am trying to send the details to my Analytics it fails with the below error
Expected Behavior
It not sending my data because it failed for the Natvie Ads. Need to send the correct data without any error.
How to Reproduce
Add the native ad and the callback for revenue failed in the app.
Reproducible in the demo app?
Not Tested
Additional Info
No response
The text was updated successfully, but these errors were encountered: