NAM Error Codes
Before Inquiring the Manager
If there are any questions, please attach the device log and reproduction steps (a reproduction video or debuggable app if possible) for quicker cause identification.
GFP Error Codes
Error Code | Sub type code | Desc | Initial Response |
---|---|---|---|
1000 | GFP_INTERNAL_ERROR | No web view in the banner ad or an error during the rendering process | Check for available webviews |
GFP_NOT_REGISTERED_PROVIDER | No advertising adapter is to be processed | Check the status of the added library | |
GFP_RECEIVED_INVALID_PROPERTY | Invalid advertisement response | Check unit settings | |
GFP_NOT_FOUND_***_ADAPTER | No advertising adapter is to be processed | Check the status of the added library | |
2000 | GFP_RECEIVED_INVALID_PROPERTY | No advertisements are responded to from the ad server | |
3000 | GFP_THIRD_PARTY_INIT_ERROR | Error during the DSP initialization process | Check the publisher code |
3000 | Other message | Error during the ad request | |
3100 | GFP_RECEIVED_INVALID_PROPERTY | Parameters required to process the ad does not exist in the response received from the ad server | |
3210 | NETWORK/SERVER/INTERNAL ERROR | Ad request fails due to network issues, etc. | Check network status |
3220 | GFP_INTERNAL_ERROR | Issue with the ad server response data | |
3310 | GFP_NO_FILL or other message | Error when loading the advertisement due to a NO_FILL (no advertisement) error sent by the DSP | |
3320 | GFP_INMOBI_NOT_SUPPORTED_NATIVE_AD_TYPE | InMobi native ad rendering error | |
3400 | GFP_REQUEST_TIMEOUT | Expiration of ad processing time - timeout | Check the network status and timeout settings |
4000 | GFP_INTERNAL_ERROR | IMA video controller creation error | |
4100 | Other message | Error playing video ad | |
5100 | GFP_FAILED_TO_RENDER_NATIVE_AD | Error when rendering a NAVER native ad | |
GFP_FAILED_TO_UNTRACK | Error when disabling a NAVER native ad | ||
6100 | GFP_FAILED_TO_RENDER_REWARDED_AD or Other message | Error when rendering a reward-type ad | |
7100 | GFP_FAILED_TO_RENDER_INTERSTITIAL_AD or Other message | Error when rendering an interstitial ad | |
9110 | GFP_MISSING_PARAM | Advertising schedule ID not set | Advertising schedule ID verification required |
9210 | GFP_AD_SCHEDULE_EMPTY or Other message | Error when processing ad schedule | Check VideoAdScheduleParam, including content length, etc. |
FAQ
-
Error message: Empty render type
In most cases, this is not an error.
-
When the ad is not elected by the AD server
Please check with the Admin or AD manager whether advertisements are set up for the relevant ad unit.
-
When an empty ad has been processed for data measurement after an error occurred in the selected ad
In this case, please refer to the previously generated error message.
-
-
Error message:
There is no adapter available
ORNot found adapter: UNITY, BANNER, INTERSTITIAL
(names in capital letters are variable)Internally, NAM SDK uses the adapter pattern.
This message occurs in two cases:
-
When an ad type not set in AdLoader has been received as a response
ex) If a banner comes down in response to the requested ad unit when it is set to a native advertisement with
GfpAdLoader
:Please check the Unit ID through the NAM Admin manager and check the ad type that needs to be set.
-
When Dependency is missing
Please check if any of the DSP dependencies discussed with the NAM representative are missing.
Also, check whether the configuration of the corresponding DSP has been set.
-
-
Error message for META(FAN):
Bid 421...586 for template 200 being used on template NATIVE_BANNER
If the above message occurred when using the Native or Native Banner ad of META, please check whether the unit type set in META Admin is Native Banner.
Also, check whether Native Banner has been enabled in GfpNativeAdOptions (setHasMediaView(false)).
-
Error message for DFP (Google):
No ad config
This error usually occurs when there is a problem with the test ad settings.
Please check the ad settings through the Admin or AD manager.
-
What happens if the ad is requested twice? (Multiple requests with a single GfpAdLoader)
The previous ad requests will be ignored. Only the last ad request will be processed.
(The last ad will be displayed)
-
Is initialization necessary?
Although not mandatory, initialization is required.
In the initialization process, adid to be used for targeting, etc. will be imported. It will each go through the DSP initialization process.
In addition, since certain DSPs require application context, it is recommended to perform this at the application level.