Configure log level

By default, the Portal SDK emits no logs. You can enable logging at any verbosity level to help debug integration issues or monitor SDK behavior in development.

Log levels

The PortalLogLevel enum defines five levels. Each level includes all levels above it in severity.

Level	What is logged
`PortalLogLevel.NONE`	Nothing. This is the default.
`PortalLogLevel.ERROR`	Failures only — failed transactions, network errors, binary crashes.
`PortalLogLevel.WARN`	Unexpected but non-fatal conditions — deprecated usage, retries, slow responses.
`PortalLogLevel.INFO`	Normal operational milestones — signing started, share generated, connection opened.
`PortalLogLevel.DEBUG`	Everything, including internals — request/response payloads, timing, state transitions.

Set the log level

Call portal.setLogLevel() after initializing your Portal instance. The change takes effect immediately across all SDK components.

import io.portalhq.android.Portal
import io.portalhq.android.utils.PortalLogLevel

class MainActivity : AppCompatActivity() {
    lateinit var portal: Portal

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        portal = Portal("YOUR_CLIENT_API_KEY")

        // Enable debug logging during development
        portal.setLogLevel(PortalLogLevel.DEBUG)
    }
}

Set the log level before calling any other SDK methods to capture all output from the start.

Recommended levels by environment

Development: PortalLogLevel.DEBUG — see all SDK activity while building your integration.
QA / staging: PortalLogLevel.INFO or PortalLogLevel.WARN — surface operational milestones and anomalies without noise.
Production: PortalLogLevel.NONE (default) — no logs emitted. Use PortalLogLevel.ERROR if you want to forward failures to a crash reporter.

Do not use PortalLogLevel.DEBUG in production. Debug output includes request payloads and internal state that may contain sensitive data.

Credentials are redacted from debug output. The Authorization bearer is never logged — requests log authorized=true|false instead — and request payloads and response bodies have their credential-bearing fields masked by name: clientSessionToken, userJwt, token, code, secret, password and privateKey. This matters most under Client Auth, where the sign-in endpoints return an end user’s session token in the response body and take the single-use grant and the live TOTP code in the request payload.Redaction covers credentials, not everything sensitive — addresses, balances and transaction contents are still logged in full, which is why DEBUG remains a development-only setting. On versions before 10.0.0, debug logs did contain live credentials: treat any log capture taken from an app running DEBUG on an earlier version as containing a usable token.

Log output

Logs are written to Android’s standard logging system and appear in Logcat. You can filter them in Android Studio’s Logcat window or via adb logcat by searching for the PortalSDK tag:

tag:PortalSDK

Getting Started

SDKs

APIs

Integrations

Resources

Configure log level

Log levels

Set the log level

Recommended levels by environment

Log output

​Log levels

​Set the log level

​Recommended levels by environment

​Log output

Log levels

Set the log level

Recommended levels by environment

Log output