When is 'event' equal to 'heartbeat' in the POST schema

[svenbw]

In the documentation in the HTTP post schema (see https://transistorsoft.github.io/capacitor-background-geolocation/interfaces/location.html#http-post-schema) event can be set to motionchange, geofence or heartbeat.

However the onHeartbeat function handler will not post data itself when invoked by the plugin (https://transistorsoft.github.io/capacitor-background-geolocation/classes/backgroundgeolocation.html#onheartbeat). If an update must be sent to the server the getCurrentPosition function must be called. Since this is invoked from javascript the event will be missing.

Can anyone give details what the condition(s) are that will set event to heartbeat in the posted server data?

[danillo10]

Same problem

[christocracy]

You are free to attach extras to your getCurrentPosition call, attaching any meta data you wish.

[svenbw]

We're using the extras already.

My original question was mainly to understand under which conditions the event is set to heartbeat because it's in the documentation listed as a possible option.

[christocracy]

The docs must be wrong.

[danillo10]

They work only with app open, if app is closed heartbeat doesnt work

[christocracy]

if app is closed heartbeat doesnt work

On iOS (nobody has specified iOS vs Android), that’s correct: no heartbeat after terminate. Read api docs Config.stopOnTerminate.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.