Reading Device Logs

 

Reading your test device logs can be a helpful way to troubleshoot your integration.  Device logs can be pulled by using a developer tool like Android Studio or Xcode.  If you aren’t sure how to pull device logs, we recommend connecting with your developer.


iOS

Set Up Verbose Logging

Change this static variable to one of the possible log levels:

https://github.com/mopub/mopub-ios-sdk/blob/master/MoPubSDK/Internal/Utility/MPLogging.m#L16


static MPLogLevel systemLogLevel = MPLogLevelInfo;

Available Levels:

  • MPLogLevelTrace

  • MPLogLevelDebug

  • MPLogLevelWarn

  • MPLogLevelInfo

  • MPLogLevelError

  • MPLogLevelFatal


Could not find custom event class named

The adapter/Custom Event is missing or in the wrong location (see Github documentation) or there is a mismatch between the actual custom event name and what is entered in the Networks tab of the MoPub UI.


Adunit is currently warming up

This is an old message, check to make sure that the MoPub AdUnit ID is the same as the ID from the UI. Using a wrong value will result in this error.


No ads found for ad unit

This log indicates that there was no fill for your ad unit.  It does not indicate that there is a problem with your integration, but you may see it in combination with another error log, such as “Could not find custom event class named” so be sure to review the logs thoroughly.  


Make sure to review the ad source breakdown associated with your ad unit to ensure your ad sources are active.  


Could not find renderer configuration for custom event class

Need to add the 3rd party Custom Event to the supportedCustomEvents by default. The publisher can add the 3rd party network here:https://github.com/mopub/mopub-ios-sdk/blob/master/MoPubSDK/Native%20Ads/MPStaticNativeAdRenderer.m#L49


Third-party network timed out.

For banners, mopub time-out limit is 10 seconds and for interstitial it’s 30 seconds. After we pinged the network, if the network does not respond within that timeout period, you will see the error below. This is a network driven issue – please reach out to your network partner.

**Disclaimer – For additional questions or concerns please reach out to your MoPub account team or to support@mopub.com with your account username, ad unit ID, MoPub SDK version, partner SDK

 
Android

Set Up Verbose Logging

Android Verbose logging can be set here:

https://github.com/mopub/mopub-android-sdk/blob/940eee70fe1980b4869d61cb5d668ccbab75c0ee/mopub-sdk/mopub-sdk-base/src/main/java/com/mopub/common/logging/MoPubLog.java#L30-L31

  LOGGER.setLevel(Level.ALL);
       LOG_HANDLER.setLevel(Level.ALL);


Failed to load Custom Event class

The adapter/Custom Event is missing or in the wrong location (see Github documentation) or there is a mismatch between the actual custom event name and what is entered in the Networks tab of the MoPub UI.


Adunit is currently warming up

This is an old message, check to make sure that the MoPub AdUnit ID is the same as the ID from the UI. Using a wrong value will result in this error.


Ad failed to load

No ads found

This log indicates that there was no fill for your ad unit.  It does not indicate that there is a problem with your integration, but you may see it in combination with another error log, such as “Could not find custom event class named” so be sure to review the logs thoroughly.  


Make sure to review the ad source breakdown associated with your ad unit to ensure your ad sources are active.  


Third-party network failed due to invalid internal state.

Double check that the App ID and network provided Adunit IDs entered in the UI are correct and entered in the right place. If not, Mopub SDK will be able to initiate the network, but you will not get fill.


Third-party network timed out.

For banners, mopub time-out limit is 10 seconds and for interstitial it’s 30 seconds. After we pinged the network, if the network does not respond within that timeout period, you will see the error below. This is a network driven issue – please reach out to your network partner.

**Disclaimer – For additional questions or concerns please reach out to your MoPub account team or to support@mopub.com with your account username, ad unit ID, MoPub SDK version, partner SDK version and full device logs. The Support Team will help you review your integration.

 

Updated: May 2017