Re: Pleas Help, My AdMob Ads Don't Appear When I'm Connected to My Own Wifi

140 views
Skip to first unread message
Message has been deleted

Joshua Lagonera (Mobile Ads SDK Team)

unread,
Jun 23, 2017, 4:22:26 AM6/23/17
to Google Mobile Ads SDK Developers
Hi there,

I tried your Ad Unit Id on our sample apps and I was able to successfully receive ads on my end. Can you provide us the following information for us to investigate the issue further?
  • Any warning/error logs, preferably by using Ad Events, to investigate if this is a device issue.
  • Logs from Charles' Proxy, with SSL Proxying enabled, to investigate the issue with your WiFi.
  • Verify if you can replicate the issue using our sample apps, to rule out any implementation issues.
Regards,
Joshua Lagonera
Mobile Ads SDK Team

On Friday, June 23, 2017 at 12:49:27 PM UTC+8, Mohak Dev wrote:
I noticed that when I'm connected to my own wifi, the ads don't work. It works perfectly when my iPhone is connected on different networks or LTE. My wifi does not block ads in any way since AdMob ads appear from different apps.
Here is my id:

    •    App ID: ca-app-pub-4177571765425647~2192405810
    •    Ad unit ID: ca-app-pub-4177571765425647/3669139017

-Please help and thank you so much!

Mohak Dev

unread,
Jun 23, 2017, 11:26:05 AM6/23/17
to Google Mobile Ads SDK Developers
I just discovered that my brother's iPhone connected to my wifi and the simulator connected to the wifi works, but my iPhone connected to the wifi still does not work. Here is what my console says on Xcode when I debugged with my iPhone with the Ad Events code as you linked me above:

17-06-23 11:22:23.887759-0400 Up[4460:930840] [DYMTLInitPlatform] platform initialization successful
2017-06-23 11:22:24.290883-0400 Up[4460:930672] Firebase automatic screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable automatic screen reporting, set the flag FirebaseAutomaticScreenReportingEnabled to NO in the Info.plist
2017-06-23 11:22:24.429866-0400  Up[4460:930816] <FIRAnalytics/INFO> Firebase Analytics v.3600000 started
2017-06-23 11:22:24.430 Up[4460:] <FIRAnalytics/INFO> Firebase Analytics v.3600000 started
2017-06-23 11:22:24.431876-0400  Up[4460:930816] <FIRAnalytics/INFO> To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/Y0Yjwu)
2017-06-23 11:22:24.432 Up[4460:] <FIRAnalytics/INFO> To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/Y0Yjwu)
2017-06-23 11:22:24.466: <FIRInstanceID/WARNING> FIRInstanceID AppDelegate proxy enabled, will swizzle app delegate remote notification handlers. To disable add "FirebaseAppDelegateProxyEnabled" to your Info.plist and set it to NO
2017-06-23 11:22:24.506366-0400 Up[4460:930815] <FIRAnalytics/INFO> Successfully created Firebase Analytics App Delegate Proxy automatically. To disable the proxy, set the flag FirebaseAppDelegateProxyEnabled to NO in the Info.plist
2017-06-23 11:22:24.507 Up[4460:] <FIRAnalytics/INFO> Successfully created Firebase Analytics App Delegate Proxy automatically. To disable the proxy, set the flag FirebaseAppDelegateProxyEnabled to NO in the Info.plist
2017-06-23 11:22:24.586442-0400 Up[4460:930672] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2017-06-23 11:22:24.588576-0400  Up[4460:930672] [MC] Reading from public effective user settings.
2017-06-23 11:22:25.097661-0400 Up[4460:930672] Metal GPU Frame Capture Enabled
2017-06-23 11:22:25.099737-0400 Up[4460:930672] Metal API Validation Enabled
2017-06-23 11:22:25.171762-0400 Up[4460:930672] libMobileGestalt MobileGestaltSupport.m:153: pid 4460 (Up) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled
2017-06-23 11:22:25.171887-0400  Up[4460:930672] libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see <rdar://problem/11744455>)
2017-06-23 11:22:25.268802-0400 Up[4460:930860] <Google> To get test ads on this device, call: request.testDevices = @[ @"d4b52fd8cee6929fec8fd303f6b8d213" ];
2017-06-23 11:22:25.553178-0400 Up[4460:930853] <FIRAnalytics/INFO> Firebase Analytics enabled
2017-06-23 11:22:25.553 Up[4460:] <FIRAnalytics/INFO> Firebase Analytics enabled
2017-06-23 11:22:27.011790-0400 Up[4460:930816] <Google:HTML> You are currently using version 7.16.0 of the SDK. Please consider updating your SDK to the most recent SDK version to get the latest features and bug fixes. The latest SDK can be downloaded from http://goo.gl/iGzfsP. A full list of release notes is available at https://developers.google.com/admob/ios/rel-notes.

I do not know what "libMobileGestalt MobileGestalt" means but I think it is irrelevant.
Thank you so much for your quick response! 


Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Jun 23, 2017, 2:31:04 PM6/23/17
to Google Mobile Ads SDK Developers
Hello, 

Thank you for reaching out. It looks like this is more of a device specific issue rather than an issue with the Mobile Ads SDK. You could follow this forum post for more information related to this.
Let me know if you have any other questions.

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

Mohak Dev

unread,
Jun 23, 2017, 4:19:22 PM6/23/17
to Google Mobile Ads SDK Developers
I figured out the issue! Turns out, my ip address had an HTTP proxy that blocked ads. I removed the link and now my ads are working perfectly!
Reply all
Reply to author
Forward
0 new messages