On Tue, Jul 2, 2013 at 5:46 PM, Yavuz Selim YILMAZ <yavuzsel(a)buffalo.edu&gt; wrote: Hi all, Is there any way to track errors on submitted push messages to the PushNetworks? Here is my scenario: I have AG Unified Push Server deployed on my machine, and I created an application. Then I registered 2 iOS variants, one with my development certificate, and another with my distribution certificate (hope I did this step correctly, what I did was actually I run the iOS variant addition step for my both certificates - by following the steps here: https://github.com/aerogear/aerogear-unified-push-server). I am able to successfully register my apps with APNs (execution hits my corresponding delegate) and I am able to register my devices with client info to my AG Unified Push Server (registerWithClientInfo executes my success block). But then, when I broadcast a message to everyone (using http://SERVER_IP:8080/ag-push/rest/sender/broadcast), my development device receives yay! the notification while distribution device does not receive anything. not supported - in development :) Is it because of the way I am creating the variants? Or a certificate issue that I couldn't track? Any thoughts or recommendations are appreciated. Best regards, --- Yavuz Selim Yilmaz SUNY at Buffalo Computer Science and Engineering PhD Candidate _______________________________________________ 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

YAY :)

On Tue, Jul 2, 2013 at 6:10 PM, Yavuz Selim YILMAZ <yavuzsel(a)buffalo.edu&gt;wrote: > Thank you! > > btw, http://SERVER_IP:8080/ag-push/rest/sender/selected also works well. > :) > > Best regards, > > --- > Yavuz Selim Yilmaz > SUNY at Buffalo > Computer Science and Engineering > PhD Candidate > > On Jul 2, 2013, at 12:00 PM, Matthias Wessendorf <matzew(a)apache.org&gt; > wrote: > > > > > On Tue, Jul 2, 2013 at 5:46 PM, Yavuz Selim YILMAZ <yavuzsel(a)buffalo.edu&gt;wrote: > >> Hi all, >> >> Is there any way to track errors on submitted push messages to the >> PushNetworks? Here is my scenario: >> >> I have AG Unified Push Server deployed on my machine, and I created an >> application. Then I registered 2 iOS variants, one with my development >> certificate, and another with my distribution certificate (hope I did this >> step correctly, what I did was actually I run the iOS variant addition step >> for my both certificates - by following the steps here: >> https://github.com/aerogear/aerogear-unified-push-server). I am able to >> successfully register my apps with APNs (execution hits my corresponding >> delegate) and I am able to register my devices with client info to my AG >> Unified Push Server (registerWithClientInfo executes my success block). >> >> But then, when I broadcast a message to everyone (using >> http://SERVER_IP:8080/ag-push/rest/sender/broadcast<http://server_ip:8...), >> my development device receives >> > > yay! > > >> the notification while distribution device does not receive anything. >> > > > not supported - in development :) > > > >> >> Is it because of the way I am creating the variants? Or a certificate >> issue that I couldn't track? Any thoughts or recommendations are >> appreciated. >> >> Best regards, >> >> --- >> Yavuz Selim Yilmaz >> SUNY at Buffalo >> Computer Science and Engineering >> PhD Candidate >> >> >> _______________________________________________ >> 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