-
-
Notifications
You must be signed in to change notification settings - Fork 474
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] [iOS] Location publishes cease after losing WIFI connection and don't restart again #23
Comments
Comment by stefanoco from Tuesday Jan 14, 2014 at 07:17 GMT On 01/14/2014 07:36 AM, Ben Jones wrote:
Kind of random behaviour here:
I'll try to better observe the real behaviour but I suspect that when Thanks for the great app anyway!!! Stefano Costa |
Comment by jpmens from Tuesday Jan 14, 2014 at 07:18 GMT Works fine here, on two distinct devices ... I assume you've set PUBs to 'manual mode' (as discussed yesterday, I think it was)? Have you tried automatic mode? |
Comment by sumnerboy12 from Tuesday Jan 14, 2014 at 07:36 GMT Hmm good point JP. I did have it set to manual publish. I have just changed it to automatic so will keep an eye on it tomorrow as the wife makes her way into work. CK did mention that the region stuff was independent from the auto-publishing, but perhaps there is something awry in the connection logic when in manual publish mode, preventing region events from getting sent? |
Comment by stefanoco from Tuesday Jan 14, 2014 at 07:45 GMT Debugging with MQTTitude + MQTTInspector ;-) |
Comment by jpmens from Tuesday Jan 14, 2014 at 07:48 GMT ;-) |
Comment by ckrey from Tuesday Jan 14, 2014 at 08:22 GMT :D |
Comment by ckrey from Tuesday Jan 14, 2014 at 08:52 GMT Here's what happens (works as designed, not as desired): If the app goes into Background, the connection is disconnected because the app cannot maintain the TCP connection in background. If you bring the app back into foreground, you'll notice the BLUE connection indicator, meaning disconnected, nothing to do. When a location change is recorded (no matter if manual, significant, move or region mode), a messages is prepared and an attempt to connect to the broker is started. If there is an error, connect will be retried after 2, 4, 8, ..., 64, 64, .... seconds until it succeeds. BUT.... If the application is in background or is sent to background, the retries are stopped until the next message is generated. When your are stationary (e.g. at home), nothing will happen. The queued messages will sit and wait until the app receives the next location event. With automatic modes switched off, even when bringing the app to foreground, no new location updates are generated. Pressing the BLUE location indicator initiates a reconnect...the queue is emptied to the server. For the time being, to avoid the situation, don't switch to manual mode. |
Comment by sumnerboy12 from Tuesday Jan 14, 2014 at 09:03 GMT Ok - I can live with that Chris - I was only trying to reduce the number of publishes by setting to manual mode since all I really need is the enter/leave events, but if it needs to remain on auto in order to keep sending messages even when in the background, that is fine. Thanks for the update! |
Comment by ckrey from Tuesday Jan 14, 2014 at 11:14 GMT What I will do: a) make sure the app tries to connect in any case when opened in foreground |
Comment by jpmens from Tuesday Jan 14, 2014 at 11:17 GMT Excellent. That should cover it! |
Comment by sumnerboy12 from Tuesday Jan 14, 2014 at 19:13 GMT Great - thanks @ckrey ! |
Issue by sumnerboy12 from Tuesday Jan 14, 2014 at 06:36 GMT
Originally opened as https://github.com/binarybucks/mqttitude/issues/266
Not sure what exactly is going on here but since the latest version on iOS I have noticed that when the phone moves out of my home WIFI range and onto 3G, location publishes stop - all kinds. Even when the phone arrives home and goes back on WIFI nothing happens.
But if I then manually hit the publish button in the app (blue pin) then all of a sudden I get a load of messages dumped to my broker - enter/leave events for home, and for another region I have configured for work.
This used to work on the previous version.
The text was updated successfully, but these errors were encountered: