Hello, Aerogear is sending android push notifications properly when the app is open (foreground) on an android device and the onNotificationGCM() function is being called successfully when the app is open. But it is not even putting a notification in the system notification tray when the app is in the background or not running at all... We are using phonegap and pushplugin on the client side and a lot of people on google are saying that if the server is not constructing the message payload structure properly, then Android devices will not create a notification in the android notification tray. Any suggestions??? here is the link I found during my research suggesting maybe Aerogear isnt structuring message payloads properly for background notifications tray alerts...(scroll to bottom) http://community.phonegap.com/nitobi/topics/_pushplugin_background_notifi... -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Sndroid-Background-push-notific... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Are you using the AeroGear Pushplugin or the "classic" one (pushplugin) ? Anyway, could you check that this is set in your manifest : https://github.com/jboss-mobile/unified-push-helloworld/blob/8e8b7fbdae50... , that make sure you message arrives even when the app is not started (but our plugin should set this for you) On Sun, May 31, 2015 at 11:02 PM, delalis <delalis(a)gmail.com&gt; wrote: > > Hello, Aerogear is sending android push notifications properly when the > app > is open (foreground) on an android device and the onNotificationGCM() > function is being called successfully when the app is open. But it is not > even putting a notification in the system notification tray when the app > is > in the background or not running at all... > > We are using phonegap and pushplugin on the client side and a lot of > people > on google are saying that if the server is not constructing the message > payload structure properly, then Android devices will not create a > notification in the android notification tray. > > Any suggestions??? > > here is the link I found during my research suggesting maybe Aerogear isnt > structuring message payloads properly for background notifications tray > alerts...(scroll to bottom) > > > http://community.phonegap.com/nitobi/topics/_pushplugin_background_notifi... > > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Sndroid-Background-push-notific... > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

hum ... strange, maybe Erik has the explanation, some caching stuff on platform side .... you could try this : remove the plugin, remove the android platform (phonegap platform rm android), add the plugin again, change the plugin.xml and add the platform again :) Otherwise you can't wait for Erik's fix that will be soon PRed (and this way you can also review it ;) ) Sebi On Mon, Jun 1, 2015 at 7:48 PM, delalis <delalis(a)gmail.com&gt; wrote: > > Hi Sebastien, unfortunately removing the ACCESS_NETWORK_STATE from the > plugin's plugin.xml file does not stop it from adding this line to the > AndroidManifest.xml when running the "phonegap build android" command, and > we also tried "phonegap prepare android", which also added it back into > the > manifest file. > > Is there somewhere else we need to remove it from in order to stop it from > adding to the Android manifest xml? > > > > > > -- > View this message in context: > http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... > Sent from the aerogear-dev mailing list archive at Nabble.com. > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

That worked thanks Erik. But now I have to re-code my client to register using the aerogear way of doing things instead of the generic way I did it before... The classic pushplugin doesnt require you to provide a push-config when calling the register() function...we were able to specify that later in the success method. That way we could first register the device in the GCM cloud, and then get a token, and provide that token to aerogear using the java sender API.

But this aerogear pushplugin looks like it requires the variant information upfront when calling register()...which we can provide but I need to know the URL to expose from the aerogear server and specify it in the push-config....

this link https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/#_d... says to use "pushServerURL": "<pushServerURL e.g http(s)//host:port/context >", in the push-config.json file...so what would this link actually be? http(s)//host:port/context would be http(s)//host:port/ag-push? or would it actually be the word "context"

thanks for your help! -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Thanks Sebastien! heres what I sent to my team to give you a better idea of how we had it set up to use javascript to register with GCM and then Java to insert into the Aerogear database: - We recently switched from using the “classic phonegap push plugin” to the “Aerogear phonegap push plugin” because background Android pushes weren’t coming through, or the payload was different than the classic push plugin expected, still not sure about that. Either way, it was recommended by Aerogear devs to switch to the Aerogear push plugin. - Our Aerogear server is hidden behind the ESB. - The device originally called the Drupal Rest service Leaton created to register devices - We can no longer do that because the Aerogear push plugin requires you to specify the Aerogear server in a config variable so it can talk DIRECTLY to the Aerogear service to register the devices. But since it is behind the ESB, we can not specify this server from the clients perspective. - So I thought maybe we can just call the rest service to register the devices like we used to, and forego the Aerogear’s “register()” function all together. However, this wont work because calling the “register()” function is how the client creates a handler to handle the push notifications … i.e. register(onNotificationGCM) - Since the classic push plugin didn’t require an Aerogear server URL, we were able to use it to register the device with Apple/GCM, and then in the success method we called Leatons REST service to insert it into a database on the ESB, and eventually it would make it into Aerogear using a JAVA service (Aerogears Java Sender API) running on the ESB. - But the new Aerogear push plugin’s register() method seems to want to register the device with Apple/GCM AND with the Aerogear server all in one step. But since the Aerogear server (ESB) is not accessible to the public, we are POOCHED. I’m going to try to call the register() function without specifying the aerogear server, but I expect it to fail since the Aerogear push plugin API says it is required…. What to do…what to do…. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Im wondering if this is a case of "were doing it wrong" and we should find a new place for the UPS to live that can be contacted directly by the devices with the push-config json info pointing right to it....

-- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

ah okay. I didnt think of putting the REST service in the config. But then what would we pass to the REST service as the device token to pass to aerogear in the subsequent Java call? in the classic push plugin, the onsuccess(event) came back with a device token that we would then send to the REST service to register with Aerogear using a Java call. On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote: > > > On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote: > >> Thanks for writing back so quickly! >> >> 1) Can't your "Leatons" REST Service proxy the register request to the >> push >> server ? >> >> ---Yes that is what we were doing before, the classic push plugin called >> register() which simply registered the token with APNS/GCM, and in the >> onSuccess function we would then send an AJAX call to Leatons REST >> service >> which would then put the device token we got back from the register() >> call >> into the Aerogear database using whatever methods Aerogears API exposed >> (sorry, I think that is what I meant by the Sender API)... so if you >> suggest >> using the REST service as a proxy to the push server and bypass the >> register() function altogether, how would we hook up the client >> onNotification() handler? >> >> 2) Or maybe just let Leaton accept the register request made by the >> aerogear >> plugin and store the json payload, later a service can submit that to the >> UnifiedPush Server. >> ---Again, how would we hook up the phonegap client onNotification() >> handler >> if we arent calling register from the clients javascript code?? >> > > I meant : you still use the plugin javascript code register() but just > make sure that your backend API (Leaton or whatever) accept the path and > the json payload so : > > POST http//myleatonservice/rest/registry/device + JSON Payload > > You just point to "http//myleatonservice/rest" in you push-config, > "/registry/device" will be added automatically by the plugin. > > Could sound hacky but worth to explore. > > This way you still hookup your onNotification() handler > >> >> >> >> -- >> View this message in context: >> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > ------------------------------ > If you reply to this email, your message will be added to the > discussion below: > > http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... > To unsubscribe from Android Background push notifications not working, click > here. > NAML > <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=... > ------------------------------ View this message in context: Re: [aerogear-dev] Sndroid Background push notifications not working <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... Sent from the aerogear-dev mailing list archive <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

You don't have to worry about that :) the AeroGear push plugin will already include the device token in the payload, in fact you don't have to worry at all about the payload, just call register() On Tue, Jun 2, 2015 at 10:16 PM, delalis <[hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=0>> wrote: > ah okay. I didnt think of putting the REST service in the config. But > then what would we pass to the REST service as the device token to pass to > aerogear in the subsequent Java call? in the classic push plugin, the > onsuccess(event) came back with a device token that we would then send to > the REST service to register with Aerogear using a Java call. > > On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote: > >> >> >> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote: >> >>> Thanks for writing back so quickly! >>> >>> 1) Can't your "Leatons" REST Service proxy the register request to the >>> push >>> server ? >>> >>> ---Yes that is what we were doing before, the classic push plugin called >>> register() which simply registered the token with APNS/GCM, and in the >>> onSuccess function we would then send an AJAX call to Leatons REST >>> service >>> which would then put the device token we got back from the register() >>> call >>> into the Aerogear database using whatever methods Aerogears API exposed >>> (sorry, I think that is what I meant by the Sender API)... so if you >>> suggest >>> using the REST service as a proxy to the push server and bypass the >>> register() function altogether, how would we hook up the client >>> onNotification() handler? >>> >>> 2) Or maybe just let Leaton accept the register request made by the >>> aerogear >>> plugin and store the json payload, later a service can submit that to >>> the >>> UnifiedPush Server. >>> ---Again, how would we hook up the phonegap client onNotification() >>> handler >>> if we arent calling register from the clients javascript code?? >>> >> >> I meant : you still use the plugin javascript code register() but just >> make sure that your backend API (Leaton or whatever) accept the path and >> the json payload so : >> >> POST http//myleatonservice/rest/registry/device + JSON Payload >> >> You just point to "http//myleatonservice/rest" in you push-config, >> "/registry/device" will be added automatically by the plugin. >> >> Could sound hacky but worth to explore. >> >> This way you still hookup your onNotification() handler >> >>> >>> >>> >>> -- >>> View this message in context: >>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>> _______________________________________________ >>> aerogear-dev mailing list >>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> ------------------------------ >> If you reply to this email, your message will be added to the >> discussion below: >> >> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >> To unsubscribe from Android Background push notifications not working, click >> here. >> NAML >> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=... >> > > > ------------------------------ > View this message in context: Re: [aerogear-dev] Sndroid Background push > notifications not working > <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... > > Sent from the aerogear-dev mailing list archive > <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com. > > _______________________________________________ > aerogear-dev mailing list > [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=1> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=2> https://lists.jboss.org/mailman/listinfo/aerogear-dev ------------------------------ If you reply to this email, your message will be added to the discussion below: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... To unsubscribe from Android Background push notifications not working, click here <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=... . NAML <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=...

On Tue, Jun 2, 2015 at 10:24 PM, delalis <delalis(a)gmail.com&gt; wrote: > So please correct me if I am wrong... > > if we call register() and set our Java REST service in the config, we > will need to take the payload passed into the REST service, parse out the > device token (which you said is sent there automatically), and send that to > Aerogear using the method we are already currently using to register device > tokens with Aerogear in the Service? (since the REST service can talk to > the UPS) > > is this correct?? > Yes :) But you can also keep the payload as is and just pass it to the UPS endpoint (since it's already the payload he expects) > > On Tue, Jun 2, 2015 at 4:20 PM, Sebastien Blanc [via aerogear-dev] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=11744&i=0>> wrote: > >> You don't have to worry about that :) the AeroGear push plugin will >> already include the device token in the payload, in fact you don't have to >> worry at all about the payload, just call register() >> >> On Tue, Jun 2, 2015 at 10:16 PM, delalis <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=11743&i=0>> wrote: >> >>> ah okay. I didnt think of putting the REST service in the config. But >>> then what would we pass to the REST service as the device token to pass to >>> aerogear in the subsequent Java call? in the classic push plugin, the >>> onsuccess(event) came back with a device token that we would then send to >>> the REST service to register with Aerogear using a Java call. >>> >>> On Tue, Jun 2, 2015 at 4:11 PM, Sebastien Blanc [via aerogear-dev] <[hidden >>> email] <http:///user/SendEmail.jtp?type=node&node=11741&i=0>> wrote: >>> >>>> >>>> >>>> On Tue, Jun 2, 2015 at 9:51 PM, delalis <[hidden email] >>>> <http:///user/SendEmail.jtp?type=node&node=11739&i=0>> wrote: >>>> >>>>> Thanks for writing back so quickly! >>>>> >>>>> 1) Can't your "Leatons" REST Service proxy the register request to >>>>> the push >>>>> server ? >>>>> >>>>> ---Yes that is what we were doing before, the classic push plugin >>>>> called >>>>> register() which simply registered the token with APNS/GCM, and in the >>>>> onSuccess function we would then send an AJAX call to Leatons REST >>>>> service >>>>> which would then put the device token we got back from the register() >>>>> call >>>>> into the Aerogear database using whatever methods Aerogears API >>>>> exposed >>>>> (sorry, I think that is what I meant by the Sender API)... so if you >>>>> suggest >>>>> using the REST service as a proxy to the push server and bypass the >>>>> register() function altogether, how would we hook up the client >>>>> onNotification() handler? >>>>> >>>>> 2) Or maybe just let Leaton accept the register request made by the >>>>> aerogear >>>>> plugin and store the json payload, later a service can submit that to >>>>> the >>>>> UnifiedPush Server. >>>>> ---Again, how would we hook up the phonegap client onNotification() >>>>> handler >>>>> if we arent calling register from the clients javascript code?? >>>>> >>>> >>>> I meant : you still use the plugin javascript code register() but >>>> just make sure that your backend API (Leaton or whatever) accept the path >>>> and the json payload so : >>>> >>>> POST http//myleatonservice/rest/registry/device + JSON Payload >>>> >>>> You just point to "http//myleatonservice/rest" in you push-config, >>>> "/registry/device" will be added automatically by the plugin. >>>> >>>> Could sound hacky but worth to explore. >>>> >>>> This way you still hookup your onNotification() handler >>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> View this message in context: >>>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >>>>> Sent from the aerogear-dev mailing list archive at Nabble.com. >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=1> >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11739&i=2> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> ------------------------------ >>>> If you reply to this email, your message will be added to the >>>> discussion below: >>>> >>>> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >>>> To unsubscribe from Android Background push notifications not >>>> working, click here. >>>> NAML >>>> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=... >>>> >>> >>> >>> ------------------------------ >>> View this message in context: Re: [aerogear-dev] Sndroid Background >>> push notifications not working >>> <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >>> >>> Sent from the aerogear-dev mailing list archive >>> <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com. >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=1> >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=11743&i=2> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> ------------------------------ >> If you reply to this email, your message will be added to the >> discussion below: >> >> http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... >> To unsubscribe from Android Background push notifications not working, click >> here. >> NAML >> <http://aerogear-dev.1069024.n5.nabble.com/template/NamlServlet.jtp?macro=... >> > > > ------------------------------ > View this message in context: Re: [aerogear-dev] Sndroid Background push > notifications not working > <http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... > Sent from the aerogear-dev mailing list archive > <http://aerogear-dev.1069024.n5.nabble.com/> at Nabble.com. > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Hi Sebastien, I tried to post to my REST server using the push.register() function. My PHP REST server receiving the call, but it doesnt look like the JSON payload is in either the _GET or _POST params. is there anything I am doing wrong? var pushConfig = { pushServerURL: window.localStorage.getItem("site_path")+"/register_device", alias: "test", android: { senderID: "46901159####", variantID: "test", variantSecret: "test" } }; push.register(onNotification, testSuccessHandler, testErrorHandler, pushConfig); ----------------------------------------------------------------------------------- Then on the PHP server I am doing this: $allVals = ""; foreach ($_GET as $key => $value) { $allVals.= $key."=>".$value.", "; } foreach ($_POST as $key2 => $value2) { $allVals.= $key2."=>".$value2.", "; } watchdog('mobile_handler', 'all params passed:'.$allVals); print($allVals); --------------------------- My service is logging the transaction, but I am not getting any JSON payload in either the GET or POST params containing a device token being sent to my service. This is what it is logging (drupal site logs): all params passed:q=>register_device/rest/registry/device, So you were correct that it is tacking on /registry/device, but where is the JSON payload?? thoughts? -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Android-Background-push-notific... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev