Jump to content

Gefencing on IOS inconsistent


PB11

Recommended Posts

iPhone 13 iOS 17.0.3 set to "Always" location access with Precise Location "enabled" in IOS

UD Mobile 1.1.27

I'm experiencing significant delays with iphone 13 pro and ios 17 using UD Mobile Geofencing.

I've been home for the past several days, and randomly UD geo will trigger my arrival in the middle of the night turning on lights and unlocking doors. I've made changes to my programs to remove the risk of my house unlocking at 2am. 

If i look at the logs my entry was logged at 11:20pm two nights ago(groceries at about 3pm but home from 5pm on) 

It then again triggered entry at 12:37am the next night. 

I have both a "neighborhood" fence (700m) and an "at home"(300m) fence.

My wifes phone has been home all day, and yet is registered as not having entered in the last two days.

Have now added a second smaller entery fence as recommended in another post to account for missed entries. Will test to see if this makes a difference.

Is there anyway to utilize wifi connectivity to trigger State variable change?

Edited by PB11
Link to comment

Thanks for opening a new topic.  The last few versions of UDM for iOS had Geofencing issues for some users, version 1.1.27 was released Friday Night. This could be the cause of any issues before UD Mobile was updated.  iOS automatic app updates usually occur between 0-3 days after release. 

In the previous post it shows a fence at 100m, please try the smallest fence at 500m, to see if false/entry exist persists.  If false entry/exit persists we can look at the logs, if it does not then try slightly decreasing radius until the issue returns.  This will show the minimum fence required in your area.  Fence accuracy depends on many factors such as cell-tower/wifi density, elevation, and obstructions. Some locations may have accurate readings at 200m and others could be 1000m.  My personal experience in a density populated area, 200m works well except in my basement. When my phone is in the basement (obstruction) I will get false entry/exist for anything less than ~1mi.

If an entry/exit is missed again please check the logs (Setting-Tab > Geofence > Document Icon at the top) after 1 hour, it is very possible an error is logged.  If the error is not self explanatory please send me a Private Message or open a Ticket and attach a copy of the UDM backup file and we can review the logs.  Note that attachments to tickets require file to be zipped. 

Unfortunately iOS does not send UDM WiFi status and UDM cannot request WiFi information when the app is in the background/suspended/not-started. Apple also denied our request to run processes in the background related to Geofencing altogether and we have no other reasons to run background processes.  So, unless Apple changes their policies,  UDM cannot use WiFi as a trigger or request location itself as UDM does not receive location updates unless iOS notifies UDM of a fence crossing.

Link to comment

Javi,

It seems to me if UD Mobile is not aware of the phone's location when the app is running in the background (or is not allowed to communicate with the IoX device unless actively running in the foreground) it has very little utility for geofencing.  My experience has been that the app "stores" the geofence status changes while running in the background/suspended/not-started and them reports them all to the IoX device when I open the app in the foreground -- not very helpful.

Interestingly, MobiLinc HD works just fine with both the Polisy and i994 ZW IR Pro when running in the background/suspended/not-started.   I guess Apple allowed them to use the iOS location for geofencing.

Link to comment
On 10/8/2023 at 9:41 AM, PB11 said:

I've been home for the past several days, and randomly UD geo will trigger my arrival in the middle of the night turning on lights and unlocking doors. I've made changes to my programs to remove the risk of my house unlocking at 2am. 

I wonder if you’re dropping local network and it’s jumping outside the geofence area while looking to connect to the cell signal. I had this problem ages ago (before we got more towers near us). But I haven’t had noticed delays with UD Mobile current beta build 1.1.27 or the last few. And I rarely have UD Mobile open or in the background (I am notorious for force closing apps often). 
 

19 minutes ago, samara said:

My experience has been that the app "stores" the geofence status changes while running in the background/suspended/not-started and them reports them all to the IoX device when I open the app in the foreground

I don’t have this issue, but I also don’t have overly complex triggers. Mine works as crossing boundaries if not even running..and yes, Mobilinc HD does as well, and that app runs even less than UD Mobile these days. 
 

My experience is running on iPhone 15 pro max with UD Mobile and eisy updated/current as of this post. (I don’t have the specific versions handy as I’m “mobile” at the moment.)

Link to comment
6 hours ago, samara said:

Javi,

It seems to me if UD Mobile is not aware of the phone's location when the app is running in the background (or is not allowed to communicate with the IoX device unless actively running in the foreground) it has very little utility for geofencing.  My experience has been that the app "stores" the geofence status changes while running in the background/suspended/not-started and them reports them all to the IoX device when I open the app in the foreground -- not very helpful.

Interestingly, MobiLinc HD works just fine with both the Polisy and i994 ZW IR Pro when running in the background/suspended/not-started.   I guess Apple allowed them to use the iOS location for geofencing.

I think I have seen a similar issue. The app does not "store" the fence crossing, iOS is pausing network connectivity.  The latest version of UD Mobile adds logs to assist with isolating these issue so that we can report these issues to Apple.

There was an issue with the last few versions of UD Mobile on iOS which caused background geofencing to be inconsistent which may have caused your issues.  Apple also has a history of breaking Geofencing with iOS upgrades, iOS was updated a couple of weeks ago.  This could be related to the version (APIs) the apps target or the iOS firmware running on your phone.  It is also possible (as evident from the last few versions) that we have an error in the app.  We would like this to run as smooth as possible, alas for some users it does not appear this is happening. 

In order to find issues in UD Mobile or allow us to have enough data to report iOS issues to Apple we need logs. If interested in helping us please follow the recommendations in my previous post then send us the backup (log) file.

  • Like 1
Link to comment
On 10/9/2023 at 10:58 PM, Javi said:

I think I have seen a similar issue. The app does not "store" the fence crossing, iOS is pausing network connectivity.  The latest version of UD Mobile adds logs to assist with isolating these issue so that we can report these issues to Apple.

There was an issue with the last few versions of UD Mobile on iOS which caused background geofencing to be inconsistent which may have caused your issues.  Apple also has a history of breaking Geofencing with iOS upgrades, iOS was updated a couple of weeks ago.  This could be related to the version (APIs) the apps target or the iOS firmware running on your phone.  It is also possible (as evident from the last few versions) that we have an error in the app.  We would like this to run as smooth as possible, alas for some users it does not appear this is happening. 

In order to find issues in UD Mobile or allow us to have enough data to report iOS issues to Apple we need logs. If interested in helping us please follow the recommendations in my previous post then send us the backup (log) file.

Javi,  I submitted a ticket with the UDM log file attached.

Link to comment
Guest
This topic is now closed to further replies.

×
×
  • Create New...