Aerodoc android client lat/long issue & updating agent status issue

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Aerodoc android client lat/long issue & updating agent status issue

columfoskin
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.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

Daniel Passos

On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
-- Passos

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

Matthias Wessendorf
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 <[hidden email]> wrote:

On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
-- Passos

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

Matthias Wessendorf
@Colum,

if you have interest, feel free to put together a PR for adding the tracking back :-) 

On Thu, Jan 19, 2017 at 9:09 AM, Matthias Wessendorf <[hidden email]> 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 <[hidden email]> wrote:

On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
-- Passos

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

columfoskin
Hi Daniel.

Is there specific reasons as to why it was removed? Also - is there much involved in getting this feature added back in, is it just a case of reverting back to the commit you have posted?

Thanks,
Colum.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

Daniel Passos
In reply to this post by Matthias Wessendorf
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 <[hidden email]> 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 <[hidden email]> wrote:

On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <[hidden email]> 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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
-- Passos

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users




--
-- Passos

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

Matthias Wessendorf
ah, great! 😘

Colum, interested? 😬

On Thursday, 19 January 2017, Daniel Passos <[hidden email]> wrote:
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 <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;matzew@apache.org&#39;);" target="_blank">matzew@...> 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 <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;dpassos@redhat.com&#39;);" target="_blank">dpassos@...> wrote:

On Wed, Jan 18, 2017 at 7:08 PM, columfoskin <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;columfoskin@gmail.com&#39;);" target="_blank">columfoskin@...> 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
<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;Aerogear-users@lists.jboss.org&#39;);" target="_blank">Aerogear-users@...
https://lists.jboss.org/mailman/listinfo/aerogear-users



--
-- Passos

_______________________________________________
Aerogear-users mailing list
<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;Aerogear-users@lists.jboss.org&#39;);" target="_blank">Aerogear-users@...
https://lists.jboss.org/mailman/listinfo/aerogear-users




--

_______________________________________________
Aerogear-users mailing list
<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;Aerogear-users@lists.jboss.org&#39;);" target="_blank">Aerogear-users@...
https://lists.jboss.org/mailman/listinfo/aerogear-users




--
-- Passos


--
Sent from Gmail Mobile

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

columfoskin
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.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue

Matthias Wessendorf
sure, don't worry :-) 

On Thu, Jan 19, 2017 at 7:54 PM, columfoskin <[hidden email]> wrote:
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



--

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users
Loading...