Error saving geofence

[MortenB]

I have a problem with my geofence.
I have set it up with a radius of 50 and an action that changes
the value of a variable.

The problem is that the geofence is never triggered and if I try to do changes
to my geofence I get the following error:

"An error was encoutered while saving the geofence"
I have tried to delete and create it again. Creation goes ok but it does not trigger
and when I try to do changes again I get the same error.

Running on a Samsung S4 Active with position activated so I wonder what I
have done wrong.

[RogueProeliator]

It looks like it is balking at the number format (the comma as the separator), which is weird as it is supposed to be using the current localization... What is your language set to for the phone, Norwegian? (Not what the app is showing, obviously that is English... for now.)

I'll see if I can duplicate it -- we'll get you fixed up.

Adam

[MortenB]

Hi

Yes it is set up with norwegian location. The same for my mac as well.

[MortenB]

Hi Adam

Had a chance to look into this yet?

//Morten

[RogueProeliator]

Had a chance to look into this yet?

I have it fixed for the next version of the application... but I THINK you can work around it by only entering a whole number (e.g. don't include the comma and decimal portion). The issue is that while the longitude and latitude are obeying the current number format, the radius is NOT... by eliminating all but the integral part, I think it should parse okay.

Adam

[MortenB]

Hi Adam

It looks like that was the trick. I entered 100 instead of 100,000 in radius and was able to save it.

Thanks for feedback.

//Morten

[MortenB]

Hi

I still have a problem with my geofence. It never triggers. So even if I "break" the radius of the fence it still say "never" under last triggered.
Any ideas as to how to try to find out what is wrong?

[RogueProeliator]

I still have a problem with my geofence. It never triggers. So even if I "break" the radius of the fence it still say "never" under last triggered.
Any ideas as to how to try to find out what is wrong?

The application is completely dependent on the system to tell it whenever a geofence is broken, so it is your system itself that is not triggering the change. So the only real two possibilities that I see are that DomoPad is setting the wrong geofence position, the geofence fails to register with the system or your location services are are setup properly.

To eliminate the first two, edit your geofence and double check that the longitude and latitude are correct using, say, Google Maps. Then disable the geofence (uncheck the box) and save it. Go back to the details, edit and save. You should get a small toast popup saying that it was enabled successfully if I remember correctly.

If those two work, check your location settings in the phone's settings. See what mode you have activated - I would recommend on high (GPS and networks) at least for testing, though my devices stay on high all the time anyway. This should eliminate the unreliable WiFi and/or cell tower location support which can be inaccurate at times.

Adam

[MortenB]

Hi

Well I think the problem is the format of the lat and long. With norwegian settings on my phone, the lat and long is separated with a , (comma) not a . (dot).
If I use the comma-values in google map it does not work but if I use it with dots it shows exactly the correct location.
I will try to change my settings on the phone and see what happens.

[MortenB]

Hi again

Well. I did some tests yesterday by setting the phone to use english and also . (dot) as separator. Still it does not trigger any geofence. I have my phone set to high accuracy.
Any other good suggestions as to what to try.