Troubleshooting with AIDE
When the SDK is behaving in a way the in-app logs can't explain, the AIDE Developer Portal is where you can see what the backend actually received and how it responded. AIDE owns the log UI and the support-ticket flow.
This page is a short pointer for AFCore consumers — the AIDE portal has its own troubleshooting docs and ticket flow.
The diagnostic playbook
- Reproduce in the app with SDK logging on (
AFCoreConfig.enableLogging(true)→AFLogLevel.DEBUG). - Note the timestamp, member id, and environment (QA vs Production).
- Open AIDE and find the member's delivery log entry around that timestamp.
- Compare what the SDK says it sent (client logs) against what AIDE says it received.
Common gap classes
| You see in the app | What AIDE will show | Likely cause |
|---|---|---|
| SDK logs the request, AIDE shows nothing | No entry | Network never reached server; check result.queued for Event Outbox deferral |
| AIDE shows the request, unexpected member | Different member id | Wrong externalUserId mapping, or QA/Prod key crossed |
AIDE shows the request, 403 | 403 in log row | Member disabled in AIDE, or key revoked |
AIDE shows the request, 4xx | Validation error payload | Request shape mismatch — see the log row detail |
SDK reports SESSION_EXPIRED repeatedly | Repeated 401s | Token refresh failing; usually clock skew or revoked key |
When to open a ticket
For AIDE-visible issues (anything that touches the backend), open the ticket from AIDE — it pre-attaches the environment, member id, recent events, and SDK version, which is enough for first-response triage.
For SDK-only issues (compile errors, build setup, sample-app questions, in-app logic that never hits the network), use the SDK Troubleshooting and FAQ pages, or email support@advantahealth.com directly.