Topic: How to update location in background (iOS) even user kill by swipe up

I want to create an app like RunKeerer.
It should continue to update location even if put into the background by the user.
In that state, the clock will be marked blue as shown in the attached image.
This article will show you what to do.
https://phongnt57.github.io/2018-11-10- … -swipe-up/
(pausesLocationUpdatesAutomatically = NO; / allowsBackgroundLocationUpdates = true / locationManager:didUpdateLocations etc)

Does this Infinity Code Online Maps asset support this?
Or do I need to create something like a plugin for Unity myself? (I don't know if that's possible.)

Regards

Post's attachments

Attachment icon blue_bg.jpg 9.42 kb, 198 downloads since 2023-12-10 

Re: How to update location in background (iOS) even user kill by swipe up

Hello.

Online Maps Location Service is a wrapper for Unity Location Service.
Unity Location Service does not support updating location in the background.
So the implementation of location updating in the background should be done outside Unity, on the Xcode side.
Unfortunately, I don't know Objective-C/Swift and won't be able to help you with this.

Kind Regards,
Infinity Code Team.

Boost your productivity a lot and immediately using Ultimate Editor Enhancer. Trial and non-commerce versions available.

Re: How to update location in background (iOS) even user kill by swipe up

Hi,

Thank you for your reply.I have to choose this one.
“Or do I need to create something like a plugin for Unity myself?”

But thank you for the information "a wrapper for Unity Location Service". When I added this word and searched, I found an example of getting the location from a native plugin. Although the purpose of this plugin is different from this background issue, it may be helpful.
https://kulwik.medium.com/unity-native- … 469d86190c

Re: How to update location in background (iOS) even user kill by swipe up

Also, this is in Japanese, but I found a way to create own plugin using Swift.
https://qiita.com/fuziki/items/955c2b35514bcfc37969

I try the iOS one first.