Request: for Admob, have a way to set a timeout ourselves when loading ads

[Liran Barsisa]

According to my tests, loading a native ad will fail after a very long time of 1 minute before we get a callback that it failed.

To test it, I used a firewall app to block all Internet access:
https://apkpure.com/noroot-firewall/app.greyshirts.firewall/amp

That's a very long time.

Please offer some way to overcome this, so that it won't take this long. 

[Subhan Usman]

I'm request to Liran & all ads employee's plz help me some money plz my child 3 babies & 1 boy not a my job at least 2 year my accident on bike to going job my right leg demage right shoulder & left foot so plz plz

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-admob-ads-sdk/ebcefe5e-2ffe-4afa-b5fc-bc4ce56663c4n%40googlegroups.com.

[Mobile Ads SDK Forum Advisor]

Hi Liran,

Thank you for contacting the Mobile Ads SDK support team.

Can you please confirm if the mentioned issue is replicating in our Google NativeAdvanced example?

Follow these rules when loading ads.

• Apps that use native ads in a list should precache the list of ads.
• When precaching ads, clear your cache and reload after one hour.
• Don't call loadAd() or loadAds() on an AdLoader until the first request finishes loading.
• Limit native ad caching to only what is needed. For example when precaching, only cache the ads that are immediately visible on the screen. Native ads have a large memory footprint, and caching native ads without destroying them results in excessive memory use.
• Destroy native ads when no longer in use.

If the above best practices doesn’t work kindly share us with the below information privately for further investigation:

• app ID
• ad unit ID
• Video recording that illustrates the issue
• Sample project that reproduces the issue

You can provide the following details via reply privately to the author option or directly provide it to this link.

 

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

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[Liran Barsisa]

Guys you really need to fix the email notifications of this website. I didn't get a link to the forum here. I had to reach the forum and find this thread again, manually...

Your link to upload files doesn't work properly, as it doesn't auto-fill the fields that say not to edit. 

As for the example of Google-Admob, of course it occurs there too, as I used the same ad-units on my own app. It will occur on all ad-unit IDs. Also not related specifically to native ads. Will occur for all kinds of ads.

You can use it yourself too. 

Your suggestions don't help as they are irrelevant to the issue I've explained. 

I wanted to attach the sample from the link you've provided, with logs on the important callbacks, and video to prove the issue occurs there, but the current website constantly says the message is too long. Then it complains I can't attach the ZIP file of the project! How can I reply you properly here? Not a ZIP file, and not MP4 of the video...

This website has too many bugs.

I had to upload now to a temporary file service instead:

https://file.io/Ki0u4PcBIeEt

[Liran Barsisa]

OK here, reported on Github, as it's much better place to communicate:
https://github.com/googleads/googleads-mobile-android-examples/issues/776

[Mobile Ads SDK Forum Advisor]

Hi Liran,

Kindly use setHttpTimeoutMillis to set a custom timeout for HTTPS calls made by the Google Mobile Ads SDK during an ad request. This accepts integers specifying the HTTPS timeout in milliseconds. Any values lower than 5000 (5 seconds) will be ignored. The default value is 60000 (60 seconds

If your app uses mediation, this timeout does not apply to network calls made by third-party ad network SDKs.

Please reach out to us, if you need any further assistance.

[Liran Barsisa]

I see. I have some questions about this:

1. Why is it 60 seconds though? 

2. Isn't there a better way to detect this case?

3. Are there other cases that would cause it to reach 60 seconds? I've noticed it by chance. If it can occur on other cases, maybe you should have something done...