Location error

[Sergio GD]

Hello, I upgraded my Moto G 2013 to Android 5.0.2 and now I have problems with some flows. I think it's something about location block. This is the log from one flow:

2015-03-08 12:34:48.691 INFO 1421@1: Flow beginning
2015-03-08 12:34:48.691 INFO 1421@4: Wi-Fi connected?
2015-03-08 12:34:48.697 INFO 1421@5: Location at?
2015-03-08 12:34:48.710 FAIL 1421@5: com.llamalab.android.util.GoogleApiException: addGeofences failed: null
2015-03-08 12:34:48.711 INFO 1421@5: Stopped by failure

[Sergio GD]

OK, I'm sorry. It was my fault. I had location disabled. The simplest thing is always the solution :)

[Automate developer]

Phew, glad to hear it's not a bug.
I'll fix the missing error message.

[Sergio GD]

I think location block it's not working anyway. I have some location blocks and flows stops at this point even if proceed option is immediately. I tried to reinstall the whole app with all the permissions and I have location enabled in my phone (battery saving option) but it doesn't work since I upgraded to android 5.0.2 :(

[Automate developer]

Please look at this thread:
https://groups.google.com/forum/#!topic/automate-user/OwPvL3nhI0s

Does you location flows have same symptoms?

I'am working with another user who is testing a nightly build with some workarounds.

Please try with the power saver disabled, it may be killing of the Google Play services, which is used for geofencing, etc.

[Sergio GD]

Hello,

It's not power saver from cell phone. I meant the location mode. I have three modes for location: high accuracy (network an GPS), battery saving (only based on network) and device only (only GPS). Before upgrading android all flows worked with battery saving location activated. I think maybe it's something about play services :( I'll try to post the extended log.

[Sergio GD]

2015-03-09 21:40:28.372 INFO 1474@4: Wi-Fi connected?
2015-03-09 21:40:28.374 INFO 1474@5: Location at?

I don't get more information. It only stops on location blocks when proceed is immediately (I checked if it was immediately and it was, just in case). Anyway, other blocks with proceed option "when change" doesn't work either.

[Sergio GD]

I forgot to say it doesn't work when I open Google maps. Before I upgraded android sometimes location blocks didn't work until I opened Google maps, just like the thread you told me. Now it doesn't do anything anyway.

[Automate developer]

I'll release a new Alpha soon, with a global settings to use the standard location services instead of the Google Play services.

Does the Location get block work?

[Sergio GD]

Thank you! I tried location get block and it works. I noticed location block whit "when change" proceed works too so I think the problem is only on immediately option.

[Sergio GD]

I'm testing with another flow and problem seems to occur when I'm not at location set in location block with immediately proceed. In that case flow stops. When I'm at location the flow continues and it works OK as you can see in the log below:

2015-03-09 22:05:15.204 INFO 1457@21: Location at?
2015-03-10 09:52:51.207 DBUG 1457@21: LocationAt ACTION_GEOFENCE: transition=1
2015-03-10 09:52:51.242 INFO 1457@8: Audio volume set
2015-03-10 09:52:51.282 INFO 1457@22: Delay

[Eugene Koon]

My "Location at" also does not work.  I waited 10 minutes but nothing happened.  i even left GPS on.  This is with the lastest update.

[Sergio GD]

This was the flow I tested with my current location and other random location. It only works and finishes when I'm at location set on block and message "yes" appears on screen.

[Automate developer]

I made some changes to the Location at block in the last version 1.0.13, to try to overcome the problem in this thread:
https://groups.google.com/forum/#!topic/automate-user/OwPvL3nhI0s

The geofencing should send Automate a message with the current "transition state" at every registration of a new geofence.
In the last release is use that message instead of doing my own check against the last known location, since it would be more accurate and in-sync with what the system thinks you're currently located.
But now it seems that the message isn't always sent, as the log below shows, so i'll probably have to revert back to doing my own geofencing when "immediately" is used.

[Sergio GD]

Yes, I think location block worked better before the last update. Anyway thank you for your work :)

[Automate developer]

I'am reverting some of the changes made in the last version and also adding a settings for using the old proximity alert API instead of Google Play services geofencing.
New alpha coming soon.