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.Documentation Index
Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt
Use this file to discover all available pages before exploring further.
Log levels
ThePortalLogLevel 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
Callportal.setLogLevel() after initializing your Portal instance. The change takes effect immediately across all SDK components.
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.INFOorPortalLogLevel.WARN— surface operational milestones and anomalies without noise. - Production:
PortalLogLevel.NONE(default) — no logs emitted. UsePortalLogLevel.ERRORif you want to forward failures to a crash reporter.
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 viaadb logcat by searching for the PortalSDK tag: