Hi, This features was removed[1] by me. For more details here[2] is where magic happened [1] https://github.com/aerogear/aerogear-android-cookbook/commit/ 0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff- 7953a6ab3baf837d865c743a054cc357 [2] https://github.com/aerogear/aerogear-android-cookbook/commit/ 697cefdf60203200a2dc2aa89d60f0ed0418c715#diff- 7953a6ab3baf837d865c743a054cc357L113 On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <columfoskin(a)gmail.com&gt; wrote: > Hey all, > > I am working on building a Node js version of the backend for the Aerodoc > application and have some questions if anyone can help it would be great. > > Can anybody help me to understand when the lat/long pairs are sent from > the > android device to the Aerodoc backend? I have spent some time debugging > and > trying to figure this out - without much success. > > I have been looking at the request sent from the android app on login and > it > is not then. My guess from looking at the Java code is this happens when > when a HTTP PUT is called on the ’saleagents’ endpoint but I cannot > determine when that endpoint is hit (from looking at the code & > debugging). > > Also, from what I see, updates to the agents status are sending a POST to > the backend, and not a PUT and therefore hitting my POST endpoint - > causing > issues. Is this expected behaviour? > > Any insight or help appreciated. > > Colum. > > > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating > -agent-status-issue-tp1013.html > Sent from the aerogear-users mailing list archive at Nabble.com. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- -- Passos _______________________________________________ Aerogear-users mailing list Aerogear-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users

I have removed it because it doesn't work with Firebase + Android N. Just created a issues to fix that problem and add it back. https://issues.jboss.org/browse/AGDROID-599 On Thu, Jan 19, 2017 at 6:09 AM, Matthias Wessendorf <matzew(a)apache.org <javascript:_e(%7B%7D,'cvml','matzew@apache.org');>> wrote: > Why was this removed? It's a key part of the demo. Not sure I recall any > discussion around removing this :-( > > On Wed, Jan 18, 2017 at 10:22 PM, Daniel Passos <dpassos(a)redhat.com > <javascript:_e(%7B%7D,'cvml','dpassos@redhat.com');>> wrote: > >> Hi, >> >> This features was removed[1] by me. For more details here[2] is where >> magic happened >> >> [1] >> https://github.com/aerogear/aerogear-android-cookbook/commit >> /0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff-7953a6ab3baf8 >> 37d865c743a054cc357 >> [2] https://github.com/aerogear/aerogear-android-cookbook/commit >> /697cefdf60203200a2dc2aa89d60f0ed0418c715#diff-7953a6ab3baf8 >> 37d865c743a054cc357L113 >> >> >> On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <columfoskin(a)gmail.com >> <javascript:_e(%7B%7D,'cvml','columfoskin@gmail.com');>> wrote: >> >>> Hey all, >>> >>> I am working on building a Node js version of the backend for the >>> Aerodoc >>> application and have some questions if anyone can help it would be >>> great. >>> >>> Can anybody help me to understand when the lat/long pairs are sent from >>> the >>> android device to the Aerodoc backend? I have spent some time debugging >>> and >>> trying to figure this out - without much success. >>> >>> I have been looking at the request sent from the android app on login >>> and it >>> is not then. My guess from looking at the Java code is this happens when >>> when a HTTP PUT is called on the ’saleagents’ endpoint but I cannot >>> determine when that endpoint is hit (from looking at the code & >>> debugging). >>> >>> Also, from what I see, updates to the agents status are sending a POST >>> to >>> the backend, and not a PUT and therefore hitting my POST endpoint - >>> causing >>> issues. Is this expected behaviour? >>> >>> Any insight or help appreciated. >>> >>> Colum. >>> >>> >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating >>> -agent-status-issue-tp1013.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users(a)lists.jboss.org >>> <javascript:_e(%7B%7D,'cvml','Aerogear-users@lists.jboss.org');> >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users(a)lists.jboss.org >> <javascript:_e(%7B%7D,'cvml','Aerogear-users@lists.jboss.org');> >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users(a)lists.jboss.org > <javascript:_e(%7B%7D,'cvml','Aerogear-users@lists.jboss.org');> > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- -- Passos

Hey Matthias, Its not that I am not interested, but I am really busy trying to get the node backend complete in the next week or so, before even looking into microservices! I am starting several other college projects in the next week or so too, so I couldn't really prioritise the android fix over my college work. I need to manage my time carefully over the next few weeks or so! Colum. -- View this message in context: http://aerogear-users.1116366. n5.nabble.com/Aerodoc-android-client-lat-long-issue- updating-agent-status-issue-tp1013p1032.html Sent from the aerogear-users mailing list archive at Nabble.com. _______________________________________________ Aerogear-users mailing list Aerogear-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users