Push Notification is not working after following Android Tutorial

[venkateshcm]

I followed the tutorial
https://parse.com/apps/quickstart?app_id=zwibe--3#parse_push/android/native/existing

Don't see any notification on device when sending notifications through parse webapp or from the tutorial test button.

In Webapp, I can see notofications with Pushes Sent as 0 and In delivery report it shows
1 for PPNS - outdated device

[parse-github-bot]

Thank you for your feedback. We use the issue tracker here to track valid bugs in our SDK. Your question seems to be more about how to use Parse. Could you check out the following resources?

• Documentation: https://www.parse.com/docs
• Google Groups: https://groups.google.com/forum/#!forum/parse-developers
• Stack Overflow: http://stackoverflow.com/tags/parse.com

[parse-github-bot]

This issue has not been updated for 7 days. If you have additional information to help pinpoint this issue as an SDK bug, please comment on this issue. We will close this issue in 7 days if no additional information is provided. Thank you for your feedback.

[alex-maltsev]

I am experiencing the same issue. I simply followed Quick Start instructions here https://parse.com/apps/quickstart#parse_push/android/native/existing, to add some basic ability to receive pushes. After that I spent some of the most frustrating several hours of my life double- and triple-checking that I did everything right. Tested on two devices (both running Lollipop), and I am not getting pushes. Pushes appear in the log on the web. But their delivery reports lists: 0 "Successful deliveries" and 2 "PPNS - outdated device". The app is brand new, and is obviously installed on both devices. I can see Installation objects for both devices, and can selectively target them via a deviceID field that I added onto the Installation object (i.e. when I supply deviceID in web API it tells me that it found the matching Installation). I have Parse version 1.9.3 showing on those Installations. I went through the troubleshooting guide here https://parse.com/docs/android/guide#push-notifications-troubleshooting and I can't find anything wrong with my app.
What can I do?? Why does Parse decide that my Installations are outdated? Can it be because I am adding extra fields to Installations, and somehow Parse decides that something is out of sync??

[justintuchek]

I was having issues with this as well. Only on initial installations though.

I would follow through with the normal ceremony of setting up all of the Parse required items in my manifest and initialization. Out of curiousity I registered for a save callback to figure out when my device info was getting inserted into the installation table (to trigger a push event.)

Parse.initialize(context, BuildConfig.PUSH_APPLICATION_ID, BuildConfig.PUSH_CLIENT_KEY);
ParseInstallation.getCurrentInstallation().saveInBackground(new SaveCallback() {
    @Override
    public void done(ParseException e) {
    }
});

There seems to be a short instance in which a device can register and become a valid target for push notifications, but they will be undeliverable and consistently yield PPNS errors on delivery reports.

Forcing the application closed and re-opening it (which would invoke the initialization process again) seems to do the trick for overcoming this PPNS issue. Without closing the app it took about 5 minutes or so before it would get notifications (not a predictable amount of time - varying with experimentation)

After testing this I went and inspected 3 of our other projects using bolts 1.2.0 and 1.2.1 as well as Parse v1.9.3

Here's enough of my Manifest + Build info to get a glimpse

Gradle

def final PARSE_APPLICATION_ID = "********************"
def final PARSE_CLIENT_KEY = "**************************"

android {
    compileSdkVersion 22
    buildToolsVersion '22.0.1'

    defaultConfig {
        applicationId "**************************"
        minSdkVersion 15
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
        buildConfigField "String", "BUILD_TIME", "\"${buildTime}\""
        buildConfigField "String", "GIT_SHA", "\"${gitSha()}\""
        buildConfigField "String", "REPORTING_KEY", "\"${CRASH_REPORTING_KEY}\""
        buildConfigField "String", "PUSH_APPLICATION_ID", "\"${PARSE_APPLICATION_ID}\""
        buildConfigField "String", "PUSH_CLIENT_KEY", "\"${PARSE_CLIENT_KEY}\""
    }
}

Manifest

    <permission android:protectionLevel="signature"
        android:name="${applicationId}.permission.C2D_MESSAGE" />
    <uses-permission android:name="${applicationId}.permission.C2D_MESSAGE" />

        <service android:name="com.parse.PushService" />
        <receiver android:name="com.parse.ParseBroadcastReceiver">
            <intent-filter>
                <action android:name="android.intent.action.BOOT_COMPLETED" />
                <action android:name="android.intent.action.USER_PRESENT" />
            </intent-filter>
        </receiver>
        <receiver android:name="com.parse.ParsePushBroadcastReceiver"
            android:exported="false">
            <intent-filter>
                <action android:name="com.parse.push.intent.RECEIVE" />
                <action android:name="com.parse.push.intent.DELETE" />
                <action android:name="com.parse.push.intent.OPEN" />
            </intent-filter>
        </receiver>
        <receiver android:name="com.parse.GcmBroadcastReceiver"
            android:permission="com.google.android.c2dm.permission.SEND">
            <intent-filter>
                <action android:name="com.google.android.c2dm.intent.RECEIVE" />
                <action android:name="com.google.android.c2dm.intent.REGISTRATION" />
                <category android:name="${applicationId}" />
            </intent-filter>
        </receiver>

We run multiple build flavors but manifest permissions and categories are templated w/ our applicationId property. Verified correctness of the by checking against artifacts in build > intermediates > manifests for all possible variations.

[grantland]

First, we'll need to determine if this is a SDK/backend bug or a set up issue:

• Enable logging and paste the output from logcat so we can see if GCM was set up properly: Parse.setLogLevel(Parse.LOG_LEVEL_VERBOSE)
• Do your ParseInstallations have a proper deviceToken on the backend?
• Does pushing to all your devices as opposed to individual installations instead of individual devices work?

[alex-maltsev]

One of my colleagues found that putting the following line: PushService.startServiceIfRequired(this); after Parse.initialize in our Application's onCreate made everything work. But that line isn't described as necessary in the quick-start. So apparently the push service wasn't starting for some reason.
To answer your questions, @grantland.

• When I tried adding Parse.setLogLevel(Parse.LOG_LEVEL_VERBOSE), I didn't see any complaints in logcat
• deviceToken looked reasonable
• pushing to all Android devices didn't work either

[adolfdsilva]

Having the same problem, please post a solution soon.

Sorry it was my mistake, I was missing the ".permissions" from the permission name tag.

[grantland]

@alex-maltsev Could you clarify if logcat states you're using GCM or PPNS? If you're using GCM this method shouldn't affect the outcome as it's only relevant to PPNS and if you're using PPNS you should update your code to use GCM.

Also, PushService.startServiceIfRequired(Context) is a private API and not recommended to use outside of the Parse SDK as they are subject to breaking changes.

[majornuts]

okay, same problem here, im working on a new app, with no prior installation of parse push, and followed the 2 minuts minimum imp. tutorial.

 Parse.setLogLevel(Parse.LOG_LEVEL_VERBOSE);
 Parse.initialize(context, AppController.applicationId, AppController.clientKey);
 ParseInstallation.getCurrentInstallation().saveInBackground(new SaveCallback() {
            @Override
            public void done(ParseException e) {
                Log.e("com.parse.push", "done", e);
            }
        });

the above code can registere a user and its shows up as "ppns outdated" on parse.com.

the verbose log gives the results below.
V/com.parse.ManifestInfo: Push is currently disabled. This is probably because you migrated from an older version of Parse. This version of Parse requires your app to have a BroadcastReceiver that handles com.parse.push.intent.RECEIVE, com.parse.push.intent.OPEN, and com.parse.push.intent.DELETE. You can do this by adding these lines to your AndroidManifest.xml:
V/com.parse.ManifestInfo: Cannot use GCM for push because the app manifest is missing some required declarations. Please make sure that these permissions are declared as children of the root element:
V/com.parse.ManifestInfo: Using none for push.

<uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="android.permission.WAKE_LOCK" />
    <uses-permission android:name="android.permission.VIBRATE" />
    <uses-permission android:name="android.permission.GET_ACCOUNTS" />
    <uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />

<service android:name="com.parse.PushService" />
    <receiver android:name="com.parse.ParsePushBroadcastReceiver"
        android:exported="false">
        <intent-filter>
            <action android:name="com.parse.push.intent.RECEIVE" />
            <action android:name="com.parse.push.intent.DELETE" />
            <action android:name="com.parse.push.intent.OPEN" />
        </intent-filter>
    </receiver>
    <receiver android:name="com.parse.GcmBroadcastReceiver"
        android:permission="com.google.android.c2dm.permission.SEND">
        <intent-filter>
            <action android:name="com.google.android.c2dm.intent.RECEIVE" />
            <action android:name="com.google.android.c2dm.intent.REGISTRATION" />

            <!--
              IMPORTANT: Change "com.parse.starter" to match your app's package name.
            -->
            <category android:name="${package.name}.starter" />
        </intent-filter>
    </receiver>


    <permission android:protectionLevel="signature"
        android:name="${package.name}.permission.C2D_MESSAGE" />
    <uses-permission android:name="${package.name}.permission.C2D_MESSAGE" />

compile 'com.parse:parse-android:1.10.3'

The result is PPNS - outdated result from parse.com. and no push notifications delivered.
BUT, why is it saying im missing the permissions in the manifest file?

[adolfdsilva]

Dude you need to replace ${package.name}.starter with your package name.

[majornuts]

@adolfdsilva ahh yes that was a mistake,
now the device shows up on parse.com, BUT only when building a signed release of the project.
that solved the "PPNS outdated".
think ill have to change the build setting to build signed debug, and see where that gets me.

[alex-maltsev]

@grantland I tried again to enable verbose logging, without doing PushService.startServiceIfRequired(this). All I can see in my log related to Parse is this:

10-20 23:43:44.348 18975-18975/com.* V/com.parse.ParseHttpClient: Using net.java.URLConnection library for networking communication.
10-20 23:43:44.450 18975-18975/com.* V/com.parse.ManifestInfo: Using gcm for push.
10-20 23:43:44.783 18975-19014/com.**** V/com.parse.ParseInstallation: Successfully deserialized Installation object

Again confirmed that push is not working without PushService.startServiceIfRequired(this).