Fixing Common Errors
Here are some troubleshooting tips for using AirBop in your app.
Test before you release
Your app does not need to be in Google Play in order for you to test the AirBop integration. The best practice is to test your app locally on your device and ensure that your AirBop account is receiving notifications properly.
If you have a problem
If you are not receiving registrations or receiving errors when sending messages to your devices here are the first things to check:
Check your IDs
The first thing to do is ensure that all of your ID values you have specified are correct. Double check the following values:
- Google API Key
- AirBop App Key
- AirBop App Secret
- Google Project Number
After ensuring that your IDs are correct in AirBop and your app you will need to re-build your app app and verify that the app registers properly now.
For Andromo Users
A good check for Andromo users is to make sure that your app has AirBop integrated. You can do this by examining the app’s preferences and verifying that they have an "App Notification Messages" section in them.
Ensure GCM is enabled
You also need to verify that you have enabled the "Google Cloud Messaging for Android" service in your Google API project as described here in Step 3: http://airbop.com/tutorials/getting-started-with-airbop-gcm#creatin...
Verify That Your Device is Supported
AirBop and Google Cloud Messaging (GCM) have the following device requirements, as explained in the GCM Architectural Overview
It requires devices running Android 2.2 or higher that also have the Google Play Store application installed, or or an emulator running Android 2.2 with Google APIs. However, you are not limited to deploying your Android applications through Google Play Store.
It uses an existing connection for Google services. For pre-3.0 devices, this requires users to set up their Google account on their mobile devices. A Google account is not a requirement on devices running Android 4.0.4 or higher.