-
Notifications
You must be signed in to change notification settings - Fork 8
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
-adViewDidFailLoading:error: not called! #12
Comments
Hi! |
Hello! Thanks for fast reply! Log for unsuccessful session: Charles session: |
Sorry, still can't reproduce the issue, even after pasting your code, running it on iOS 8, 9, 10.3 Simulator, iOS 10.3.2 device, replacing response with one you provided. The Do you experience same issue on other iOS versions, devices or simulators? |
Ok, I continue to research this issue on my side. I reproduce it on iOS 10 on simulator and device (iPhone 7). This reproduce also with older versions of SDK. |
We tried getting real 204 from backend (by using high CPM floor) and replacing server response with Charles. In both cases delegate method was called. |
I firstly integrate YandexMobileAds. In response that SDK received from ad exchange returned 204 code, but response also contains headers fields And it's strange |
I tried different versions of Charles. Indeed, when using Charles 3 connection hangs forever in case of 204 response. But with Charles 4 everything is fine. It's also fine with no proxy connected. |
Thanks! I update Charles to 4 version and everything works fine! |
Method from YMAAdViewDelegate protocol adViewDidFailLoading: error: never called. I double check my integration. If banner is successfully loaded i get callback adViewDidLoad:, but if ad server return no content (see it in Charles) nothing happened.
Also I reproduce it on your demo app (from this repository)
The text was updated successfully, but these errors were encountered: