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
I'm trying to emulate the behavior of the example app in my application. In an Android physical phone, everything is working as expected.
Using an iOS phone (iPhone X, quite old), I see that the example application is kinda working, while my application is not working properly. Indeed, the example app tracks my movements even when the app is killed, pushing my position to https://tracker.transistorsoft.com correctly.
My app instead stops tracking, or doesn't track at all in some experiments.
I made an accurate comparison between the two behaviors (you can find the logs from .emailLog attached). In this experiment, I started tracking at ~22:30 and made some relevant movements (>300mt) at ~8:30, ~13:00 and ~18:30. The example app seems to be able to track all those relevant movements, while my app tracked only the first at ~8:30.
Note that the plugin configuration is the same. What could be the cause of this bad behavior?
Ensure your app is calling .ready(config) each and every time your app launches, no matter what; even if launched automatically by the OS in the background.
Required Reading
Plugin Version
4.16.9
Mobile operating-system(s)
What do you require assistance about?
I'm trying to emulate the behavior of the example app in my application. In an Android physical phone, everything is working as expected.
Using an iOS phone (iPhone X, quite old), I see that the example application is kinda working, while my application is not working properly. Indeed, the example app tracks my movements even when the app is killed, pushing my position to https://tracker.transistorsoft.com correctly.
My app instead stops tracking, or doesn't track at all in some experiments.
I made an accurate comparison between the two behaviors (you can find the logs from
.emailLog
attached). In this experiment, I started tracking at ~22:30 and made some relevant movements (>300mt) at ~8:30, ~13:00 and ~18:30. The example app seems to be able to track all those relevant movements, while my app tracked only the first at ~8:30.Note that the plugin configuration is the same. What could be the cause of this bad behavior?
example-app.log
my-app.log
[Optional] Plugin Code and/or Config
[Optional] Relevant log output
The text was updated successfully, but these errors were encountered: