You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice to have access to information about longer stays. Android reports it via another event, DWELL events. iOS uses another API however, CLVisit.
Android and iOS also handle throttling differently. Android sets a loiteringDelay on initialization, while iOS reports the duration via the arrivalDate and departuredate properties.
The text was updated successfully, but these errors were encountered:
I add this feature on my local branch, but I figure out a simple way:
1 - define how long user must stay on "boundary" after entering to dispatch the dwell.
2 - if your time reach before user exit the "boundary" is your dwell
It'd be nice to have access to information about longer stays. Android reports it via another event, DWELL events. iOS uses another API however, CLVisit.
Android and iOS also handle throttling differently. Android sets a loiteringDelay on initialization, while iOS reports the duration via the arrivalDate and departuredate properties.
The text was updated successfully, but these errors were encountered: