AdsLoader fails to load on slow network connection

[Gal Orlanczyk]

Hi,

I was testing the iOS SDK with slow connection.

I first received error code 1010, but on the second time I am receiving 1005 and from this point on I will always get this same error with 1005 code and message: "ERROR: Ads cannot be requested because this AdsLoader failed to load." so it keeps firing this error right away and the only way to solve it is to create the loader again or shutdown the app.

Is this a known issue? should I destroy the adsLoader when I receive this error code and create a new one? should I destroy when I receive 1010 before it?

Thanks,

Gal 

[Chris Feldman (IMA SDK Team)]

Hi Gal,

If you believe this is happening because of a slow network connection then I would suggest resuming content instead of trying to load your adsLoader again. It's likely that an error like this will happen repeatedly because the network connection will not have changed. However, this is not a common error and I'd like us to be sure that it is the network connection and not an issue with your implementation. Can you see if you get the same error in our sample app when you test with your ad tag and a slow network connection? I'd also like to test myself, if you're able to share your ad tag with me. 

Let me know if you continue to have issues.

Regards,

Chris Feldman

IMA SDK Team

[Gal Orlanczyk]

Hi Chris I used the advance sample ad tags with link conditioner on iOS device.

[Chris Feldman (IMA SDK Team)]

Hi Gal,

Thank you for following up. You're using our sample ad tags, are you also using our sample apps? I've throttled my connection to kbps, but I'm still not seeing your error when I test in the sample. If you're able to reproduce the "ERROR: Ads cannot be requested because this AdsLoader failed to load." in our sample apps, please provide me with detailed steps to for how to do so. I also need to know what kind of throttling you're using. 

If you're not using our sample apps, you can share with me the code that you're using.

Regards,

Chris Feldman

IMA SDK Team

[Gal Orlanczyk]

Hi Chris,

I am using the link conditioner with the default profile for Edge or 3G with lower rates. it sometimes happens and sometimes not.

But when I receive 1005 and 1010 I must create the loader again from scratch or it won't work anymore.

Could you approve that if this 2 error code appear I should recreate the AdsLoader?

I want to make the best handling for this cases. It might be rare but when I try it in slow connection for 10-20 times it will happen once for sure.

Thanks, 

Gal 

[Chris Feldman (IMA SDK Team)]

Hi Gal,

There's no issue with recreating the adsLoader. However, best practice in this situation would be to resume content immediately. If this is happening because of network latency then it's likely to happen on subsequent requests on the same network, which could cause a long delay and hurt the user experience.

Regards,

Chris Feldman

IMA SDK Team

[Gal Orlanczyk]

Ofcourse the content will be resume the question is, that if I am receiving this error codes: 1005 and 1010 should I recreate the ads loader? 

Because from what I have seen so far after receiving this errors there is no way to receive ads from this ads loader an error will always occur.

[Chris Feldman (IMA SDK Team)]

Hi Gal,

You can reload the adsLoader in order to make subsequent ads requests. However, I wouldn't suggest immediately requesting another ad as it can hurt the use experience to wait for multiple ads to load after an error.

Regards,

Chris Feldman

IMA SDK Team