Guidelines for iOS SDK no filling or loading failure

1. No-fill issue

To troubleshoot common non-filling problems, you can refer to the following methods:

• Open the SDK log and request according to the SDK Log, check the specific reason why there is no filling;
• Check the specific reason why there is no filling through the log analysis page of TopOn developer background;

Common no-fill errors are as follows:

• The appId of TopOn does not match the placementId;
• The appId of the advertising platform does not match the placementId;
• The API called does not match the advertising form corresponding to the advertising space;
• The self-rendering and template configuration corresponding to the advertising platform does not match the TopOn backend;
• Network abnormalities prevent normal loading of advertising resources;

Common errors Code and error description, please refer to Error code description to troubleshoot and confirm the problem.

1.1 TopOn’s appId and placementId do not match

Please check when integrating. You can confirm whether it is a matching problem through the loading log printed by the SDK, and check whether the appId and placementId used by the incoming TopOn are correct.

1.2 The appId and placementId of the advertising source do not match

1. Check the configuration of the TopOn background advertising source (Open the SDK log, and see whether the TopOn background configured advertising source parameter is consistent with the background configuration of the advertising platform through the networkUnit field).
2. Check if there is logic in the code to initialize the AD platform SDK separately (initializing two different Appids in the project at the same time will cause problems, make sure you initialize the same appId).
3. Check whether the Debugging mode of the background AD space is enabled (because the appId of the mode mode is different from the appId of the developer AD source, the problem will occur when initializing two different Appids in the project at the same time, turn off the debug mode of the TopOn background and try again).
4. Check for apps and AD placement parameters that are passed in incorrectly using the default parameters for the open screen ads (passing in incorrectly causes the SDK of the AD platform to be initialized with the wrong id).

1.3 The API called does not match the advertising form corresponding to the advertising slot

Please confirm whether the API call is correct based on the actual requested advertising format.

1.4 Advertisement has no callback request result for a long time

Please check the configured waterfall list and confirm which advertising source has not returned for a long time through the SDK log

1.5 Meta ads without filling

To test Meta ads, you need to ensure that the mobile phone Have Facebook client installed and logged in. For testing of bidding ads, please configure debugging mode, see for details:

1.6 Advertisement display is not allowed Come out

1. Please turn on SDK’s logging function, check whether the ad is loaded successfully.
• Loaded successfully: next step
• Loading failed: Query TopOn error code, Third-party advertising platform error codes & FAQ
2. View Console log to check whether the problem is with a certain advertising platform or all advertising platforms.
3. In the developer backend, change this ad slot and only open the ad source of the problematic advertising platform. Then replace it with the developer's own ad slot on our demo to test whether it is normal. Then the ad slot will only Open the advertising source of another problematic advertising platform until all problematic advertising platforms have been tested.
• Our demo is normal: (Explain the advertisement There is no problem with the source) Next step
• Our demo is also not normal: provide us with information
4. Use other test machines to test and check whether the problem is with a certain model.
• All test machines have problems: (Explanation It is not a problem with the test model) Next step
• There is a problem with a certain test machine: provide us with information

1.7 The time from loading the ad to receiving the callback is too long

1. Check whether the network is normal;
2. Check whether the integration of each advertising source is normal;
3. There are too many advertising sources configured under the advertising slot and the ads The fill rate of the source is low, and the SDK will sequentially request ads from each advertising source configured under the advertising slot. This is a time-consuming process. If an advertising source can be loaded successfully quickly, the SDK will call back successfully. If all advertising sources fail, it will take a lot of time, and the SDK will eventually fail to call back. Please optimize the ad slot configuration

1.8 Lack of dependent libraries leads to ads Loading failure

There may be various factors that cause your application to fail to load ads, such as:

ATAdLogger(UA_6.2.30) Message:loadFail CallBack Fail::didFailToLoadADWithPlacementID:b62b420b0c5834 
error:Error Domain=com.anythink.ATADLoadingErrorDomain Code=1009 "Adapter(ATAdColonyRewardedVideoAdapter) initialization failed" 
UserInfo={NSLocalizedDescription=Adapter(ATAdColonyRewardedVideoAdapter) initialization failed, NSLocalizedFailureReason=The adapter not found} ?

ATRewardedVideoViewController::didFailToLoadADWithPlacementID:b62b420b0c5834 error:Error Domain=com.anythink.ATADLoadingErrorDomain 
Code=1009 "Adapter(ATAdColonyRewardedVideoAdapter) initialization failed" 
UserInfo={NSLocalizedDescription=Adapter(ATAdColonyRewardedVideoAdapter) initialization failed, NSLocalizedFailureReason=The adapter not found}

The ad loading error is because AdColonyAdapter and AdColony's SDK are not imported, so we need to add the Adapter of this platform and introduce their SDK into the project.