Errors

In 2.0 the SDK reports failures as values, not rejected promises. show() never rejects, and the bridge methods resolve with { success: false } rather than throwing, so a missing catch can no longer wedge an integration.

EncoreErrorInfo

A native failure, flattened for the bridge.

interface EncoreErrorInfo {
  type: string;      // frozen error-type vocabulary
  message: string;   // human-readable description
}

type is the stable identifier string. The two native EncoreError hierarchies differ in shape, so the bridge sends the identifier rather than reconstructing a JavaScript class from it.

`type`	Cause
`not_configured`	A method was called before `configure()`
`invalid_api_key`	Empty or malformed API key
`invalid_url`	Internal URL construction failure
`http_error`	Non-2xx HTTP response
`api_error`	The API returned a structured error
`decoding_error`	A response failed to decode
`network_error`	Connectivity issue: timeout, DNS, and so on
`persistence_error`	Local storage read or write failure
`domain_error`	A business rule was violated
`bridge_error`	The native bridge did not return a result. React Native only

Where errors arrive

Presentation failures

A failure that stopped the sheet appearing lands on the PresentationResult as not_presented with reason.type === 'error':

const result = await Encore.placement('cancel_flow').show();

if (result.status === 'not_presented') {
  if (result.reason.type === 'error') {
    console.warn('Encore:', result.reason.error.type, result.reason.error.message);
  }
  proceedWithCancellation();   // run your fallback either way
}

Do not gate your fallback on the error branch. not_presented also covers no_offer_available, experiment_control, and use_case_unavailable, none of which are failures, and all of which still need your original flow to continue.

Claim failures

A claim that errored after the sheet appeared surfaces on the advertiser axis instead, as advertiser: { type: 'failed', error }. The user never saw it.

Purchase failures

Throwing from your purchase controller records publisher: 'failed' with your error message, and the flow continues. Return 'cancelled' for a user cancellation and 'pending' for a deferred purchase rather than throwing either.

Bridge-level failures

Every bridge method is wrapped: a native call that fails logs a [Encore] warning and resolves with a fallback rather than rejecting, so a bridge fault can never crash the host app.

const { success } = await Encore.setPurchaseController(replacementController);
if (!success) {
  // configure() ran without a purchase path, so there is no controller to
  // replace, or the native module rejected the call.
}

For show(), that fallback is a not_presented result carrying error.type === 'bridge_error'.

PresentationResult, where presentation and claim failures land.
PurchaseController for purchase-side failures.
Platform detail: iOS errors and Android errors.

iOS

Android

Web

Bridges

EncoreErrorInfo

Where errors arrive

Presentation failures

Claim failures

Purchase failures

Bridge-level failures

​EncoreErrorInfo

​Where errors arrive

​Presentation failures

​Claim failures

​Purchase failures

​Bridge-level failures

​Related

EncoreErrorInfo

Where errors arrive

Presentation failures

Claim failures

Purchase failures

Bridge-level failures

Related