I didn't mean that GCM failed.. just thought that GCM maybe decided to block aerogear now or something like that. But since it happens on iOS too this doesn't seem to be the matter.. Any other clues? _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Of course I sent several requests... The problem with Openshift (that should never occur...)

has disappeared after the correction done some weeks ago. As I told you in my first message, I get a "job submitted" answer from the server.

On Wed, Apr 23, 2014 at 9:52 AM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > One thing to have in mind: > > Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. > > Than, the next request does boot up the server. In theory that can mean, > a push might be missed, while still booting up the system. > See ? A metrics/Analytics view would give all that information :-) (e.g. > how many push were sent, and delivered to the 3rd party networks) > > > @Android: is the app running? I think there are issues w/ the Android > process has has been killed > > > > On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner < > florian.schrofner(a)outlook.com&gt; wrote: > >> I didn't mean that GCM failed.. just thought that GCM maybe decided to >> block aerogear now or something like that. >> But since it happens on iOS too this doesn't seem to be the matter.. >> >> Any other clues? >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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

Now I can't see that... When I'm back in office.

Enviado do meu iPhone No dia 23/04/2014, às 10:02, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: On Wed, Apr 23, 2014 at 10:58 AM, Miguel Lemos <miguel21op(a)gmail.com&gt;wrote: > Of course I sent several requests... > > The problem with Openshift (that should never occur...) > I am sure they still feel very sorry about that this problem ever could happen > has disappeared after the correction done some weeks ago. > As I told you in my first message, I get a "job submitted" answer from > the server. > OK, so - what does the server-side log file say ? > > > On Wed, Apr 23, 2014 at 9:52 AM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > >> One thing to have in mind: >> >> Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no >> traffic. >> >> Than, the next request does boot up the server. In theory that can mean, >> a push might be missed, while still booting up the system. >> See ? A metrics/Analytics view would give all that information :-) (e.g. >> how many push were sent, and delivered to the 3rd party networks) >> >> >> @Android: is the app running? I think there are issues w/ the Android >> process has has been killed >> >> >> >> On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner < >> florian.schrofner(a)outlook.com&gt; wrote: >> >>> I didn't mean that GCM failed.. just thought that GCM maybe decided to >>> block aerogear now or something like that. >>> But since it happens on iOS too this doesn't seem to be the matter.. >>> >>> Any other clues? >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ 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

I made a reset to OShift and it's working again. This is really an issue that one way or another should be solved... Enviado do meu iPhone No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: One thing to have in mind: Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. Than, the next request does boot up the server. In theory that can mean, a push might be missed, while still booting up the system. See ? A metrics/Analytics view would give all that information :-) (e.g. how many push were sent, and delivered to the 3rd party networks) @Android: is the app running? I think there are issues w/ the Android process has has been killed On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner < florian.schrofner(a)outlook.com&gt; wrote: > I didn't mean that GCM failed.. just thought that GCM maybe decided to > block aerogear now or something like that. > But since it happens on iOS too this doesn't seem to be the matter.. > > Any other clues? > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ 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

Now I can't. Anyway: I already shared the log on a previous similar situation...

M Enviado do meu iPhone No dia 23/04/2014, às 11:47, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: Hi Miguel, thanks for the update. If you could share the log, of the JBoss instance on your OpenShift account, that would be great. And yes, as you may expect, we are interested in solving this issues... On Wed, Apr 23, 2014 at 11:42 AM, Miguel Lemos <miguel21op(a)gmail.com&gt;wrote: > I made a reset to OShift and it's working again. > > This is really an issue that one way or another should be solved... > > Enviado do meu iPhone > > No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org&gt; > escreveu: > > One thing to have in mind: > > Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. > > Than, the next request does boot up the server. In theory that can mean, > a push might be missed, while still booting up the system. > See ? A metrics/Analytics view would give all that information :-) (e.g. > how many push were sent, and delivered to the 3rd party networks) > > > @Android: is the app running? I think there are issues w/ the Android > process has has been killed > > > > On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner < > florian.schrofner(a)outlook.com&gt; wrote: > >> I didn't mean that GCM failed.. just thought that GCM maybe decided to >> block aerogear now or something like that. >> But since it happens on iOS too this doesn't seem to be the matter.. >> >> Any other clues? >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ 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

Now I can't. Anyway: I already shared the log on a previous similar situation... M Enviado do meu iPhone No dia 23/04/2014, às 11:47, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: > Hi Miguel, > > thanks for the update. If you could share the log, of the JBoss instance on your OpenShift account, that would be great. > And yes, as you may expect, we are interested in solving this issues... > > > >> On Wed, Apr 23, 2014 at 11:42 AM, Miguel Lemos <miguel21op(a)gmail.com&gt; wrote: >> I made a reset to OShift and it's working again. >> >> This is really an issue that one way or another should be solved... >> >> Enviado do meu iPhone >> >> No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: >> >>> One thing to have in mind: >>> >>> Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. >>> >>> Than, the next request does boot up the server. In theory that can mean, a push might be missed, while still booting up the system. >>> See ? A metrics/Analytics view would give all that information :-) (e.g. how many push were sent, and delivered to the 3rd party networks) >>> >>> >>> @Android: is the app running? I think there are issues w/ the Android process has has been killed >>> >>> >>> >>>> On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner <florian.schrofner(a)outlook.com&gt; wrote: >>>> I didn't mean that GCM failed.. just thought that GCM maybe decided to block aerogear now or something like that. >>>> But since it happens on iOS too this doesn't seem to be the matter.. >>>> >>>> Any other clues? >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> _______________________________________________ >>> 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 > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev

No favor. I'm not near a PC.., As I told before, I've already sent a log related to a similar problem a month ago, I think.

Anyway: this is a recurring problem that deserves a deep attention, I think. Enviado do meu iPhone No dia 23/04/2014, às 12:41, "Bruno Oliveira" <bruno(a)abstractj.org&gt; escreveu: Hi Miguel, if you make us a favor and send the logs next time, that would help a lot. Is hard to guess, because we don't have control over the OpenShift's infrastructure — abstractj On Wed, Apr 23, 2014 at 6:42 AM, Miguel Lemos <miguel21op(a)gmail.com&gt;wrote: > I made a reset to OShift and it's working again. > > This is really an issue that one way or another should be solved... > > Enviado do meu iPhone > > No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org&gt; > escreveu: > > One thing to have in mind: > > Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. > > Than, the next request does boot up the server. In theory that can mean, > a push might be missed, while still booting up the system. > See ? A metrics/Analytics view would give all that information :-) (e.g. > how many push were sent, and delivered to the 3rd party networks) > > > @Android: is the app running? I think there are issues w/ the Android > process has has been killed > > > > On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner < > florian.schrofner(a)outlook.com&gt; wrote: > >> I didn't mean that GCM failed.. just thought that GCM maybe decided to >> block aerogear now or something like that. >> But since it happens on iOS too this doesn't seem to be the matter.. >> >> Any other clues? >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

> On Wed, Apr 23, 2014 at 1:58 PM, Miguel Lemos <miguel21op(a)gmail.com&gt; wrote: > No favor. I'm not near a PC.., > > As I told before, I've already sent a log related to a similar problem a month ago, I think. What Bruno and I tried to say: We do think that the UNDERLYING problem of this is NOT necessarily the same as it was in the past. As said, feel free to send the recent log, if you like > > Anyway: this is a recurring problem that deserves a deep attention, I think. > > Enviado do meu iPhone > > No dia 23/04/2014, às 12:41, "Bruno Oliveira" <bruno(a)abstractj.org&gt; escreveu: > >> Hi Miguel, if you make us a favor and send the logs next time, that would help a lot. >> >> Is hard to guess, because we don't have control over the OpenShift's infrastructure >> — >> abstractj >> >> >>> On Wed, Apr 23, 2014 at 6:42 AM, Miguel Lemos <miguel21op(a)gmail.com&gt; wrote: >>> I made a reset to OShift and it's working again. >>> >>> This is really an issue that one way or another should be solved... >>> >>> Enviado do meu iPhone >>> >>> No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: >>> >>>> One thing to have in mind: >>>> >>>> Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. >>>> >>>> Than, the next request does boot up the server. In theory that can mean, a push might be missed, while still booting up the system. >>>> See ? A metrics/Analytics view would give all that information :-) (e.g. how many push were sent, and delivered to the 3rd party networks) >>>> >>>> >>>> @Android: is the app running? I think there are issues w/ the Android process has has been killed >>>> >>>> >>>> >>>>> On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner <florian.schrofner(a)outlook.com&gt; wrote: >>>>> I didn't mean that GCM failed.. just thought that GCM maybe decided to block aerogear now or something like that. >>>>> But since it happens on iOS too this doesn't seem to be the matter.. >>>>> >>>>> Any other clues? >>>>> >>>>> _______________________________________________ >>>>> aerogear-dev mailing list >>>>> aerogear-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>>> _______________________________________________ >>>> 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 > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

These are the server logs I have.. I'm not quite sure which ones you need, so I've added them all. Are attachments working on this mailing list? Cheers, Florian ------------------------------ From: miguel21op(a)gmail.com Date: Wed, 23 Apr 2014 13:26:08 +0100 To: aerogear-dev(a)lists.jboss.org Subject: Re: [aerogear-dev] Problems sending notifications Cordova I think I understood... I hope you understand too what I'm trying to say: since I started with Aerogear some months ago I was warned about this situation. This is a recurring problem. Maybe there are already many logs reporting it... Anyway, as you may know, when I can I try to send all the information possible to track these kind of situations, bugs etc. to help your work. Now I just can't. Signing off ;-) M Enviado do meu iPhone No dia 23/04/2014, às 13:02, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: On Wed, Apr 23, 2014 at 1:58 PM, Miguel Lemos <miguel21op(a)gmail.com&gt;wrote: No favor. I'm not near a PC.., As I told before, I've already sent a log related to a similar problem a month ago, I think. What Bruno and I tried to say: We do think that the UNDERLYING problem of this is NOT necessarily the same as it was in the past. As said, feel free to send the recent log, if you like Anyway: this is a recurring problem that deserves a deep attention, I think. Enviado do meu iPhone No dia 23/04/2014, às 12:41, "Bruno Oliveira" <bruno(a)abstractj.org&gt; escreveu: Hi Miguel, if you make us a favor and send the logs next time, that would help a lot. Is hard to guess, because we don't have control over the OpenShift's infrastructure — abstractj On Wed, Apr 23, 2014 at 6:42 AM, Miguel Lemos <miguel21op(a)gmail.com&gt;wrote: I made a reset to OShift and it's working again. This is really an issue that one way or another should be solved... Enviado do meu iPhone No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org&gt; escreveu: One thing to have in mind: Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no traffic. Than, the next request does boot up the server. In theory that can mean, a push might be missed, while still booting up the system. See ? A metrics/Analytics view would give all that information :-) (e.g. how many push were sent, and delivered to the 3rd party networks) @Android: is the app running? I think there are issues w/ the Android process has has been killed On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner < florian.schrofner(a)outlook.com&gt; wrote: I didn't mean that GCM failed.. just thought that GCM maybe decided to block aerogear now or something like that. But since it happens on iOS too this doesn't seem to be the matter.. Any other clues? _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

I think I understood... I hope you understand too what I'm trying to say: since I started with Aerogear some months ago I was warned about this situation. This is a recurring problem. Maybe there are already many logs reporting it... Anyway, as you may know, when I can I try to send all the information possible to track these kind of situations, bugs etc. to help your work. Now I just can't. Signing off ;-) M

Florian, This error is common when you're using a prerelease JDK, or one you have built yourself. What JDK version are you running?

No, I don't mind at all.. Should I just set up a new UPS cartridge and test if the server crashes again, or should I check for the keystore?

By the way there really seem to be some problems concerning Google Cloud Messaging itself.. I didn't receive any other push notifications today (except from an Asian messenger my girlfriend made me use,

I assume it doesn't use GCM in order to address the Chinese market). Suddenly all notifications (including the aerogear notifications) arrived and my phone started going nuts. So maybe it isn't your fault after all.. Also I don't think it's only my phone, because my colleague also didn't receive any aerogear notifications the day before yesterday (although he had no problems with it today) until I restarted the server. Maybe GCM made the UPS server crash, because it had some problems/unexpected behaviour?

-- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problems-sending-n... 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

I started seeing issues on Friday. For devices that had previously registered, my push notifications were being received. However, when I started changing the alias on those devices, they no longer received push notifications.

I am running aerogear-push 0.9 on OpenShift. I restarted the server but the problem still exists. I noticed that I don't have a keystore file. I am using the curl method for sending push notifications on the command line from a mac. I guess I will do what I know one of you is going to suggest and that is to upgrade.

I just wanted to let you guys know that it might not be your code. It might be an OpenShift issue, who knows. I don't have any error messages in the log. I even set the logging level to debug and still didnt get any more useful messages. I just see info messages relating the a client registering and a message when I send the push notification.

I have both iOS and android devices. I made sure to send the push notification to just a single android device as well as a seperate push notification to send to an iOS device. Both devices had different aliases.

-- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problems-sending-n... 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

wrote:

Update: I managed to get both Android and iOS push notifications working again. I am using the latest aerogear cordova push plugin with a 0.9 aerogear server. Not sure exactly what the problems where. However, I suspect it might have something to do with the issue that Matthias put in a Jira ticket in for.

I did find some issues with the Android version when the app is paused or not running. Seems to behave differently between Android 4.2.2 and 4.4. I am going to do some more testing and open Jira tickets as necessary.

-- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problems-sending-n... 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

Recently, I unregistered the device. Then deleted the app from the Nexus 7 and restarted the device. I then redeployed the app and registered the device. It then started receiving again. I have also had to delete and recreated the variant to prevent duplicate messages from being sent. I have had to do similar things from my Samsung Tab3 but not nearly as often. -- View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problems-sending-n... Sent from the aerogear-dev mailing list archive at Nabble.com. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <javascript:;> https://lists.jboss.org/mailman/listinfo/aerogear-dev