Capturing a debug log is the most effective way to troubleshoot mobile SDK and push notification issues. This guide will help you generate debug logs for your iOS and Android app and share logs with our Support Team if needed.

​
Requirements

To capture a debug log, make sure you have:
  • A device that can reproduce the issue
  • Access to the app’s developer tools
  • OneSignal Mobile SDK version 5.0.0 or higher
If you’re using an earlier SDK version, refer to Version 9.0 docs for instructions.

​
Step-by-step instructions

​
1. Enable verbose logging

Add the VERBOSE log level call to your app before initializing the OneSignal SDK. This ensures detailed diagnostic information is captured for every OneSignal operation. 
// LogLevel: NONE | FATAL | ERROR | WARN | INFO | DEBUG | VERBOSE
OneSignal.getDebug().setLogLevel(OneSignal.LOG_LEVEL.VERBOSE);
Set the log level before calling OneSignal.init to ensure all SDK activity is logged.

​
2. Reproduce the issue

With verbose logging enabled, reproduce the issue on a physical device or emulator connected to Android Studio or Xcode.

Reproduce the issue

​
3. Capture and Share the Logs

Once the issue is reproduced, review the logs to see if it helps diagnose the issue. If you need assistance, copy-paste the entire log from start to end and send them to OneSignal Support as a .txt file. Include all relevant reproduction steps, screenshots, and other details.

Share the log

​
Platform-specific instructions

​
Android Studio

  1. Open the Run tab in the bottom panel. (If not visible, go to View > Tool Windows > Run)
  2. Run the app on a connected device or emulator.
  3. Reproduce the issue.
  4. Select all log output ( Ctrl + A or Cmd + A) and copy it.
  5. Paste it into a .txt file.
  6. Send the file to OneSignal Support with steps to reproduce.
📎 Sample Log (Google Drive)

How to run the app in Android Studio.