Mobile Troubleshooting

📘

Looking for website help?

If you only have a website and no mobile apps, see our Web Push Troubleshooting guide.

Troubleshooting Steps

1. Make sure you have the latest version of our SDK.

OneSignal regularly makes updates. If you are using our Mobile SDKs in your app and having an issue, chances are it was fixed in the most recent update.

You can find the most recent versions on Github > the SDK using > Releases.

2. Check Our Error Logs

If you see an error or warning you are unable to resolve, start by checking our known issues and solutions in the OneSignal ErrorLog.

3. See our Troubleshooting Guides

Here is a quick reference table of our SDK's Troubleshooting Docs:

4. Getting Mobile Crash Logs

If you could send these logs through a .txt file or Pastebin that would be much appreciated and help us better see what is happening in the app.

• How to get a crash log or error log from an Android device
• How to get a crash log from an iOS device

FAQ

What happens if I change my OneSignal app_id?

Changing the OneSignal app_id in your init code will create a brand new user and push subscription for the new app_id. If your iOS bundle id and your Android package id is the same, then the device will continue with the same push subscription status. The user data will be brand new i.e. you will need to add back your tags, email address, phone number on the new user record.

If the iOS bundle id or Android package id are different, you will have the Mismatched Bundle ID and Invalid Google Credentials errors.