Package 

Object CloudXErrorCode.Companion

    • Method Detail

      • getINTERNAL_ERROR

         final CloudXErrorCode getINTERNAL_ERROR()

        Unexpected exception during initialization, ad loading, or ad display. Also returned when an adapter fails to load but does not report a specific error code.

        Publisher action: Report to CloudX support with the full formattedMessage and stack trace.

      • getNETWORK_ERROR

         final CloudXErrorCode getNETWORK_ERROR()

        HTTP request failed with an I/O error (DNS failure, connection reset, SSL error, etc.).

        Publisher action: Check device connectivity. If persistent, check for proxy/firewall blocking CloudX endpoints.

      • getNETWORK_TIMEOUT

         final CloudXErrorCode getNETWORK_TIMEOUT()

        HTTP request timed out before receiving a response.

        Publisher action: Check network conditions. May indicate slow connectivity or server-side latency.

      • getNETWORK_SERVER_ERROR

         final CloudXErrorCode getNETWORK_SERVER_ERROR()

        CloudX server returned HTTP 5xx.

        Publisher action: Transient — retry happens automatically where applicable. If persistent, report to CloudX support.

      • getNETWORK_CLIENT_ERROR

         final CloudXErrorCode getNETWORK_CLIENT_ERROR()

        CloudX server returned HTTP 4xx (excluding 429). Typically unauthorized or malformed.

        Publisher action: Check the app key is correct. The SDK will not retry this request.

      • getNETWORK_TOO_MANY_REQUESTS

         final CloudXErrorCode getNETWORK_TOO_MANY_REQUESTS()

        CloudX server returned HTTP 429.

        Publisher action: App is being rate-limited. Reduce request frequency or contact CloudX support about limits.

      • getNETWORK_INVALID_RESPONSE

         final CloudXErrorCode getNETWORK_INVALID_RESPONSE()

        Server returned HTTP 200 but the body could not be parsed (malformed JSON in config or bid response, or empty geo response).

        Publisher action: Report to CloudX support — likely a server-side issue.

      • getNOT_INITIALIZED

         final CloudXErrorCode getNOT_INITIALIZED()

        load() or show() was called before CloudX.initialize() completed. Delivered via onAdLoadFailed() or onAdDisplayFailed(), notonInitializationFailed().

        Publisher action: Wait for the onInitialized() callback before creating or loading ads.

      • getNO_ADAPTERS_FOUND

         final CloudXErrorCode getNO_ADAPTERS_FOUND()

        No adapter modules found on the classpath via reflection.

        Publisher action: Add at least one adapter dependency (e.g., adapter-meta, adapter-vungle) to the app's build.

      • getNO_NETWORKS_CONFIGURED

         final CloudXErrorCode getNO_NETWORKS_CONFIGURED()

        The server returned no ad networks for this app key.

        Publisher action: Check the CloudX dashboard — no networks are configured for this app.

      • getINVALID_APP_KEY

         final CloudXErrorCode getINVALID_APP_KEY()

        The app key passed to CloudX.initialize() is blank or empty. Checked locally before any network call.

        Publisher action: Fix the app key. It must be non-blank.

      • getSDK_DISABLED

         final CloudXErrorCode getSDK_DISABLED()

        The server disabled the SDK via traffic control (HTTP 204 with X-CloudX-Status: SDK_DISABLED). No ads will be served this session.

        Publisher action: Intentional server-side behavior. Check traffic control settings in the CloudX dashboard.

      • getINVALID_AD_UNIT

         final CloudXErrorCode getINVALID_AD_UNIT()

        The ad unit ID doesn't exist in the server config, or exists but has the wrong type (e.g., loading a banner ad unit as interstitial). The error message lists available ad units of the expected type.

        Publisher action: Check the ad unit ID matches the dashboard and the correct create*() method is used.

      • getADS_DISABLED

         final CloudXErrorCode getADS_DISABLED()

        The bid server returned HTTP 204 with X-CloudX-Status: ADS_DISABLED. Ads are disabled for this specific ad unit.

        Publisher action: Check ad unit settings in the CloudX dashboard.

      • getNO_FILL

         final CloudXErrorCode getNO_FILL()

        No ad available. The most common loading error. Causes: (a) bid server returned no bids; (b) bids were returned but all adapters failed to load.

        Publisher action: Normal — not every request fills. If fill rate is unexpectedly low, check ad unit config and adapter setup.

      • getAD_NOT_READY

         final CloudXErrorCode getAD_NOT_READY()

        show() was called but no ad is loaded.

        Publisher action: Check isAdReady before calling show().

      • getAD_ALREADY_SHOWING

         final CloudXErrorCode getAD_ALREADY_SHOWING()

        show() was called while the same ad instance is already on screen.

        Publisher action: Wait for onAdHidden() before showing again.

      • getDONT_KEEP_ACTIVITIES_ENABLED

         final CloudXErrorCode getDONT_KEEP_ACTIVITIES_ENABLED()

        Android's "Don't keep activities" developer option is enabled, which destroys the host Activity during fullscreen ad display.

        Publisher action: Disable "Don't keep activities" in device developer options. Not an app issue.

      • getADAPTER_INTERNAL_ERROR

         final CloudXErrorCode getADAPTER_INTERNAL_ERROR()

        Catch-all for adapter errors with no more specific code.

        Publisher action: Check the error message for details. Report to CloudX support if persistent.

      • getADAPTER_INVALID_LOAD_STATE

         final CloudXErrorCode getADAPTER_INVALID_LOAD_STATE()

        The adapter was in a state that prevented loading (e.g., already loading or loaded).

        Publisher action: Avoid calling load() while a load is in progress.

      • getADAPTER_INVALID_CONFIGURATION

         final CloudXErrorCode getADAPTER_INVALID_CONFIGURATION()

        The ad network SDK is misconfigured (bad placement IDs, invalid app IDs, etc.).

        Publisher action: Verify ad network credentials and placement IDs in the CloudX dashboard.

      • getADAPTER_INVALID_SERVER_EXTRAS

         final CloudXErrorCode getADAPTER_INVALID_SERVER_EXTRAS()

        Server-side parameters for this adapter are invalid or missing (e.g., missing placement ID in bid response).

        Publisher action: Check adapter configuration in the CloudX dashboard.

      • getADAPTER_BAD_REQUEST

         final CloudXErrorCode getADAPTER_BAD_REQUEST()

        The ad network rejected the ad request as invalid.

        Publisher action: Check ad unit configuration. If persistent, report to CloudX support.

      • getADAPTER_NOT_INITIALIZED

         final CloudXErrorCode getADAPTER_NOT_INITIALIZED()

        The ad network SDK was not initialized when the adapter tried to load. Usually transient during app startup.

        Publisher action: If persistent, check adapter initialization logs.

      • getADAPTER_INITIALIZATION_ERROR

         final CloudXErrorCode getADAPTER_INITIALIZATION_ERROR()

        Exception thrown while creating the adapter object — a bug in the adapter code or incompatible SDK version.

        Publisher action: Check that adapter and ad network SDK versions are compatible. Report to CloudX support.

      • getADAPTER_AD_NOT_READY

         final CloudXErrorCode getADAPTER_AD_NOT_READY()

        The ad network SDK says the ad is not ready to show.

        Publisher action: Ensure the ad finished loading before displaying.

      • getADAPTER_LOAD_TIMEOUT

         final CloudXErrorCode getADAPTER_LOAD_TIMEOUT()

        The adapter did not finish loading within the SDK's configured timeout. This is CloudX's own timeout wrapping the adapter.

        Publisher action: May indicate slow network or unresponsive ad network SDK.

      • getADAPTER_TIMEOUT

         final CloudXErrorCode getADAPTER_TIMEOUT()

        The ad network SDK itself reported a timeout. Distinct from 609 — this is the network SDK's own timeout, not the CloudX wrapper.

        Publisher action: May indicate slow network or ad network server issues.

      • getADAPTER_SERVER_ERROR

         final CloudXErrorCode getADAPTER_SERVER_ERROR()

        The ad network's own server returned an error.

        Publisher action: Transient — the ad network may be experiencing issues.

      • getADAPTER_BID_TOKEN_TIMEOUT

         final CloudXErrorCode getADAPTER_BID_TOKEN_TIMEOUT()

        Collecting a bid token from the ad network SDK timed out during the pre-auction phase.

        Publisher action: May indicate a slow or unresponsive ad network SDK.

      • getADAPTER_WEBVIEW_ERROR

         final CloudXErrorCode getADAPTER_WEBVIEW_ERROR()

        The ad network's WebView-based creative failed to render.

        Publisher action: May indicate a device WebView issue or a bad creative. Report to CloudX support if persistent.

      • getADAPTER_AD_EXPIRED

         final CloudXErrorCode getADAPTER_AD_EXPIRED()

        The loaded ad expired before show() was called. Networks typically set 30–60 minute expiry windows.

        Publisher action: Call show() sooner after loading, or reload when the ad expires.

      • getADAPTER_AD_FREQUENCY_CAPPED

         final CloudXErrorCode getADAPTER_AD_FREQUENCY_CAPPED()

        The ad network is frequency-capping this placement.

        Publisher action: Normal — the network limits how often ads are shown. Wait before requesting again.

      • getADAPTER_REWARD_ERROR

         final CloudXErrorCode getADAPTER_REWARD_ERROR()

        A rewarded ad failed to deliver the reward callback.

        Publisher action: The user may not have completed the reward interaction. Check rewarded ad flow.

      • getADAPTER_MISSING_ACTIVITY

         final CloudXErrorCode getADAPTER_MISSING_ACTIVITY()

        The adapter requires an Activity context but didn't receive one.

        Publisher action: Ensure show() is called with a valid, non-finishing Activity.

      • getADAPTER_DISPLAY_FAILED

         final CloudXErrorCode getADAPTER_DISPLAY_FAILED()

        The ad network SDK failed to display the ad after loading.

        Publisher action: Check that the Activity is in the foreground and not finishing. If persistent, report to CloudX support.

      • getADAPTER_INITIALIZATION_TIMEOUT

         final CloudXErrorCode getADAPTER_INITIALIZATION_TIMEOUT()

        The ad network SDK did not complete initialization within the configured timeout.

        Publisher action: May indicate a slow network or unresponsive ad network SDK. Check device connectivity and adapter logs.