The methods below require the OneSignal SDK versions 3 & 4.It is recommended to upgrade to our latest version 5 SDKs for User Model APIs.See Update to User Model for migration steps.
Requirements
- A device able to reproduce the issue
- Access to the mobile app’s dev tools.
Step 1. Add Verbose Logging To Your App
OneSignal.setLogLevel
allows you to get extra logging related to OneSignal’s API requests. Call this method with the verbose
option before OneSignal.init
.
Step 2. Reproduce the Issue
Plug the device into your dev tools and reproduce the issue while capturing the log. This will help trace any events and will likely help uncover any errors that might be happening.
Step 3. Share
If the log didn’t help solve the issue and you need further assistance, please share the entire log from app start to end of reproduction as a .txt file.
Android Studio
- Select Run from the bottom of the window. ------If you don’t see this select it from View > Tool Windows > Run

- Run your application on your emulator or device
- Select all lines in the log that appear within your Run console by pressing Control + A and then copy them.
- Paste them into a .txt file and send this to support.
Xcode
NOTE: For your crash to show in the following steps the crash must happen when your device is not connected to your Mac. Connect it after you reproduce the crash.- In Xcode go to
Window
>Devices & Simulators
. - Select your device on the left and press the “Open Console” button.
- Select “All Messages” (top left)
- Reproduce issue with the connected device.
- Press
Command + A
to select all, thenCommand + C
to copy log - Send it to OneSignal support along with details on reproducing the crash.
