Error references

Initialization error enum cases

Error Case	Error Code	Description
requestFailed	1	The SDK’s initialization request failed.
reInit	2	The SDK had already been initialized.

Load error enum cases

Error Case	Error Code	Description
requestFailed	1	There was an error when trying to retrieve the placement’s waterfall configuration.
noFill	2	None of the waterfall instances managed to load an ad successfully.
alreadyUsed	3	This ad instance has already been used.
unexpected	4	Unexpected error.

Load errors are provided if an ad fails to load, on the failedToLoad callback. The recommended way to handle these errors is to dispose the failing ad instance, create a new one and call its load method.

In the case of a noFill error, you can additionally check the list of InstanceErrors provided on the failedToLoad’s LoadResult parameter.

Present error enum cases

Error Case	Error Code	Description
unexpected	1	Unexpected error.
notRequested	2	The ad can’t be presented because it was never requested.
noLongerAvailable	3	The underlying network’s ad has expired or is no longer available.
loading	4	The ad is still loading.
presentFailed	5	The underlying network failed to present the ad. We usually provide the error code of the network if available.
alreadyUsed	6	This ad instance has already been used.

Present errors can happen when trying to display an interstitial or rewarded ad.

In the case of a noLongerAvailable, presentFailed or alreadyUsed error you should create a new ad instance and call its load method.

Instance error enum cases

Error Case	Error Code	Description
loadFailed	1	The load request was not successful. We usually provide the error code of the underlying adapter if available.
timeout	2	The adapted network took too long to load an ad, which resulted in a timeout.
initializationFailed	3	The adapted network failed to initialize correctly.
invalidConfiguration	4	Invalid or missing configuration parameters passed to the adapted network.
invalidClassname	5	No network adapter with the specified classname was found.
unexpected	6	Unexpected error.
unsupportedType	7	The adapted network does not support the specified ad type.
skipped	8	The instance was skipped.
reinitializationUnsupported	9	The adapted network received new init parameters (for example a different app key) and was unable to perform a new init.

Instance errors are provided as part of the results of the didLoad and failedToLoad callbacks, and can give you insights on how your instances are performing.