IOS Apps and/or standard protocols?

Hello Jenkisan,

Sorry for not replying any sooner. I must have missed the notification of your post.

I don’t have any IOS devices to test with, and I’m totally unfamiliar with the IOS app landscape, so I couldn’t tell you.

Basically, if an app supports online tracking via HTTP, it should be viable and not even very difficult to add support for it to Trackserver. If you have any suggestions, please let me know so I can have a look.

As for the standard protocols you mention: as far as I know, these are not HTTP-based protocols, so Trackserver, being a WordPress plugin, cannot support these by nature. If you know of any protocols that ARE HTTP based and not supported by Trackserver (GpsGate would be a nice example), feel free to let me know.

Best regards,
Martijn.

SendLocation is an iOS-App which supports HTTP:

The HTTP GET-method is in following format:

https://yourserver.com/yourscript.php?lat=***&lon=***&speed=***&heading=***&vacc=***&hacc=***&altitude=***&deviceid=**

Is there a chance to get it running with Trackserver?

Best regards,
Harald.

I’m also interested in iOS support. I’ll try to find someone to test it with some iOS apps, iirc there are some apps that could work. Did you try OsmAnd for iOS?

Quote from its description:

Share your location so that your friends can find you

Let me know if it worked, please.

Support for SendLocation should be possible, but I wonder if there is any way to do authentication with it. There should be a a way to map the iOS device to the WordPress user, preferrably with a password too.

So if the parameters that SendLocation sends are fixed, and ‘deviceid’ is the only thing available to tell users/devices apart, that would be a bit limited.

Is there a way to get the device ID that SendLocation sends from the device?

As per https://itunes.apple.com/nl/app/sendlocation/id377724446:

“Where you must provide the “https://yourserver.com/yourscript.php” part to application settings.”

It would be possible to implement a scheme where the WordPress username becomes part of the URL, like this:

https://yourserver.com/wordpress/<sendlocation-slug>/<username>/?lat=...

and the deviceID could be used as a password.

If anyone is willing to test this, I can put support for it in GitHub….

Best regards,
Martijn.

Hi,

I would be happy to test this as it’s something I actually need quite urgently.

Dan

Ok, I’ll see what I can do. One question up front:

Is it feasable to use the device ID as a password? Can you get the device ID from your phone and enter it in a configuration field in the WordPress admin somewhere?

If not, there are still other possibilities. I could for example also make the secuity code (password) part of the URL, just like the username.

Can you give me an idea on what would be the most convenient way to implement authentication?

Hi,

Assuming device ID is the same as serial number then it’s simple to get from the phone’s “About” page in settings or just by connecting the phone to a pc with iTunes.

Dan

Ah, assumption ??

But I think I’d rather pick a solution where the security ID (password) can be changed by the user as often as s/he likes, because it will be traveling over the wire in plaintext. So the device ID is not appropriate anyway.

Thanks, I’ll let you know once I have something to test (I hope within a week or so).

Cheers,
Martijn.

Whatever you feel is best.

Hi,

I just released Trackserver v2.0 on www.remarpro.com with experimental support for SendLocation. Please update the plugin and see the options page and the Trackserver user profile for settings related to SendLocation.

I have not actually tested this with the app on an iOS device, because I don’t own any. I have tested with the URL specification as given on SendLocation’s iTunes page, and that seemed to work.

Please try it out. If you find any problems with Trackserver’s support for SendLocation, please open a new support ticket.

Best regards,
Martijn.

For completeness, the URL scheme I used (and what should be configured in SendLocation) is this:

https://<wordpress base url>/<sendlocation-slug>/<username>/<access key>/

Where <sendlocation-slug> defaults to ‘sendlocation’, <username> is your WordPress login username and <access key> is the key configured in your Trackserver user profile.

Cheers,
Martijn.