Troubleshooting
Common issues and solutions when integrating WormaCeptor.
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| No network logs | Missing implementation module | Add debugImplementation for api-impl-persistence or api-impl-imdb |
| Release build crash | Implementation in implementation | Change to debugImplementation |
| Shake gesture not working | No implementation module | Shake requires api-impl-persistence or api-impl-imdb |
| Overlay not appearing | Missing permission | Grant SYSTEM_ALERT_WINDOW via system settings |
| Ktor requests missing | Init order | Call WormaCeptorApi.init() before creating the HttpClient |
| WebView traffic not captured | Wrong WebViewClient | Use WormaCeptorWebView.createMonitoringClient() |
| WebSocket messages missing outgoing | Manual recording required | Call monitor.recordSentMessage() after each webSocket.send() |
| Features disabled | Init config | Check the features parameter in init() |
| Redaction not working for Ktor | Shared config | Ktor redaction methods delegate to WormaCeptorApi.redactionConfig |
| Large responses truncated | Content length limit | Increase maxContentLength (default: 250KB) |