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 have found that when I while running the navigator.health.queryAggregated I cannot do anything else on my app so I can't run the process in the background without affecting the user until the process is finished. Running the navigator.health.query works fine in the background without affecting the user functionality on the app. I have tried it with calories and distance dataTypes with bucket = 'day'. Running the app on an iPhone XR. Any ideas what I could do to fix this? I would like to update the data in background without affecting the user.
The text was updated successfully, but these errors were encountered:
In Android this is not true, as I developed the code and it runs in a separate thread. In iOS, it relies on Telerik's code and I am not sure if it is actually asynchronous or not (it should if it follows Cordova's recommendations). If it's synchronous, it would be good if someone could help me make it run on another thread. Meanwhile, a workaround can be using a web worker.
dariosalvi78
changed the title
navigator.health.query won't run in background
navigator.health.query won't run in background in iOS
Jul 11, 2019
dariosalvi78
changed the title
navigator.health.query won't run in background in iOS
navigator.health.query won't run in a separate thread in iOS
Jan 7, 2020
I have found that when I while running the navigator.health.queryAggregated I cannot do anything else on my app so I can't run the process in the background without affecting the user until the process is finished. Running the navigator.health.query works fine in the background without affecting the user functionality on the app. I have tried it with calories and distance dataTypes with bucket = 'day'. Running the app on an iPhone XR. Any ideas what I could do to fix this? I would like to update the data in background without affecting the user.
The text was updated successfully, but these errors were encountered: