Logging Configuration

The Portal SDK for React Native provides built-in logging capabilities to help you debug and monitor SDK operations during development and production.

Quick Start

Enable logging by setting the logLevel parameter when initializing Portal:

import { Portal } from '@portal-hq/core'

const portal = new Portal({
  apiKey: 'YOUR_PORTAL_CLIENT_API_KEY',
  logLevel: 'debug', // Enable debug-level logging
  backup: { /* ... */ },
  gatewayConfig: { /* ... */ },
})

Log Levels

The SDK supports five log levels, ordered by verbosity:

Level	Description	Use Case
`'none'`	No logging output (default)	Production environments
`'error'`	Only errors and critical failures	Production with minimal logging
`'warn'`	Errors and warnings	Staging and production
`'info'`	Errors, warnings, and informational messages	Development and staging
`'debug'`	All log messages including detailed debugging information	Local development only

Default: 'none' - No logs are emitted unless you explicitly configure logging.

Logger Interface

Your custom logger must implement these four methods:

interface Logger {
  error: (...args: unknown[]) => void
  warn: (...args: unknown[]) => void
  info: (...args: unknown[]) => void
  debug: (...args: unknown[]) => void
}

Production Logger with Timestamps

For better observability, add timestamps to your logs:

const portalLogger = {
  error: (...args: unknown[]) => {
    const timestamp = new Date().toISOString()
    console.error(`[${timestamp}] [PORTAL ERROR]`, ...args)
  },
  warn: (...args: unknown[]) => {
    const timestamp = new Date().toISOString()
    console.warn(`[${timestamp}] [PORTAL WARN]`, ...args)
  },
  info: (...args: unknown[]) => {
    const timestamp = new Date().toISOString()
    console.info(`[${timestamp}] [PORTAL INFO]`, ...args)
  },
  debug: (...args: unknown[]) => {
    const timestamp = new Date().toISOString()
    console.debug(`[${timestamp}] [PORTAL DEBUG]`, ...args)
  },
}

const portal = new Portal({
  apiKey: 'YOUR_PORTAL_CLIENT_API_KEY',
  logLevel: 'info',
  logger: portalLogger,
  backup: { /* ... */ },
  gatewayConfig: { /* ... */ },
})

How Logging Works

SDK handles level filtering - The SDK filters messages based on your logLevel setting before calling your logger methods
Logger handles output - Your logger is responsible only for formatting and outputting the messages
No performance impact when disabled - When logLevel is 'none', log messages are not generated

Next Steps

MPC Progress Callbacks - Monitor MPC operation progress
Portal API Methods - Learn about available SDK methods
Error Codes - Understand Portal error codes

Getting Started

SDKs

APIs

Integrations

Resources

Logging Configuration

Quick Start

Log Levels

Logger Interface

Production Logger with Timestamps

How Logging Works

Next Steps

​Quick Start

​Log Levels

​Logger Interface

​Production Logger with Timestamps

​How Logging Works

​Next Steps

Quick Start

Log Levels

Logger Interface

Production Logger with Timestamps

How Logging Works

Next Steps