[Aerogear-users] Trouble sending Android Push Notifications

[Sebastien Blanc]

On Thu, Nov 26, 2015 at 4:36 PM, Rob Willett <rob.aerogear at robertwillett.com
> wrote:

> Sebastien,
>
> We’ve checked and Google Cloud Messaging is enabled
>
> We’ve created a whole new Google project and started again. We’ve created
> the Google GCM Server API key again, we’ve deleted the old variant and
> created a new one with the new server API key and the new Google project
> number. I’m going to start publishing the keys and the secrets as it makes
> it difficult to follow exactly what has been done and where. Once we have
> it working, I’ll remove the old Google project and start again.
>
> We’ve updated our Cordova project with the new variant information and
> restarted up our Cordova app. We can see the Alias we created in our
> Android version in the Android Push variant along with a Device Token. The
> alias matches our Android alias that we uploaded.
>
> We fire up android and look at the logcat output. Rather scary…
>
> We send a new Push from the UPS console with the app in foreground,
> background and not fired up.
>
> E/WifiStateMachine(  740): WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=2.06 rxSuccessRate=2.05 targetRoamBSSID=30:85:a9:6d:dc:fc RSSI=-78
> E/WifiStateMachine(  740): WifiStateMachine starting scan for “XXXX”WPA_PSK with 5240
> I/wpa_supplicant(  939): wlan0: CTRL-EVENT-SCAN-STARTED
> I/art     (  740): Explicit concurrent mark sweep GC freed 159875(7MB) AllocSpace objects, 8(128KB) LOS objects, 29% free, 37MB/53MB, paused 1.177ms total 96.881ms
> I/EventLogService( 1730): Opted in for usage reporting
> I/EventLogService( 1730): Aggregate from 1448549400100 (log), 1448549400100 (data)
> I/SyncAdapterService(24506): Ignoring sync request for inactive user
> I/ServiceDumpSys( 1730): dumping service [account]
> E/WifiStateMachine(  740): WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.76 rxSuccessRate=2.76 targetRoamBSSID=30:85:a9:6d:dc:fc RSSI=-77
> E/WifiStateMachine(  740): WifiStateMachine starting scan for “XXXXX”WPA_PSK with 5240
> I/wpa_supplicant(  939): wlan0: CTRL-EVENT-SCAN-STARTED
> E/WifiStateMachine(  740): WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=1.65 rxSuccessRate=2.54 targetRoamBSSID=30:85:a9:6d:dc:fc RSSI=-78
> E/WifiStateMachine(  740): WifiStateMachine starting scan for “XXXXX”WPA_PSK with 5240
> I/wpa_supplicant(  939): wlan0: CTRL-EVENT-SCAN-STARTED
>
> Nothing obvious appears in the logcat output.
>
> We have looked in the log of the Push server and can see the message being
> sent to GCM
>
> 2015/11/26 10:22:00,265 WARN  [org.jboss.resteasy.resteasy_jaxrs.i18n] (http-/127.3.204.1:8080-3) RESTEASY000235: Field clientConnection of subresource org.keycloak.services.resources.TokenService will not be injected according to spec
> 2015/11/26 10:22:12,244 INFO  [PushNotificationSenderEndpoint] (http-/127.3.204.1:8080-3) Message submitted to PushNetworks for further processing
> 2015/11/26 10:22:12,244 INFO  [PushNotificationSenderEndpoint] (EJB default - 6) Processing send request with &apos;[alert=Test 16, criteria=[aliases=null, deviceTypes=null, categories=null, variants=null], time-to-live=-1]&apos; payload
> 2015/11/26 10:22:12,364 INFO  [APNsPushNotificationSender] (EJB default - 6) Message to APNs has been submitted
> 2015/11/26 10:22:12,487 INFO  [GCMPushNotificationSender] (EJB default - 6) Sending payload for [1] devices to GCM
> 2015/11/26 10:22:12,546 INFO  [GCMPushNotificationSender] (EJB default - 6) Message to GCM has been submitted
> 2015/11/26 10:22:15,267 WARN  [org.jboss.resteasy.resteasy_jaxrs.i18n] (http-/127.3.204.1:8080-3) RESTEASY000235: Field providers of subresource org.keycloak.services.resources.TokenService will not be injected according to spec
>
> The Aerogear Console also reports that the test pushes have gone AND that
> they succeeded.
>
> I can’t believe that we have missed a simple configuration issue on the
> UnifiedPush server.
>
Yes, strange, looks like you are doing everything the correct way

> We’ll try and bypass the UPS console and write direct to GCM now through
> curl or something. Do you know if the device token in the UPS console is
> the Android token to use?
>
That is good test indeed and yes the token in UPS is the one you can use
for your GCM test.

> Thanks
>
> Rob
>
> On 26 Nov 2015, at 14:33, Sebastien Blanc wrote:
>
> Hi Rob,
>
> Maybe obvious but just to be sure : have you enabled "Google Cloud
> Messaging for Android" API ?
>
> You also mention that you are using an old project, I have seen before
> issues with my old projects, could you create a new google project to see
> if that helps ?
>
> Last point : have you checked in the Android logs (logcat) that the message
> really dies not arrive ?
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20151126/fa9204c3/attachment.html