Post by garmindave on Sept 30, 2018 9:35:48 GMT -6
I’m experiencing with my new iPhone XSMax and SWConnect. It appears that my locations are not sent or buffered if the SWConnect App is asleep in the background. You have to have it on the screen for the location to be sent. I’m completely non-technical but just use it. I have used Spotwalla for years and this is the first time I’ve not managed to sort my issues but I’m guessing I’m an early adopter with this mind numbing priced iPhone!
Anyone know a fix so I can run SWConnect whilst looking at a navigation screen?
Admittedly I don't have an iPhoneXs Max to test with, but would have assumed things should have just worked. Also, haven't spent a lot of time testing with IOS 12, but this is the first support thread I have heard. I'm curious when you mention wanting to watch a navigation screen. That popped out at me, and I've heard others mention that SWConnect stopped working when used with another navigation app.
As a check, could you simply try using with your phone, let the app sleep as expected, but don't use another navigation app? I'd be curious if that works. IOS will quite often kill a backgrounded app to make more memory room available. If you have other things running, sometimes that can happen. So, please as a test, kill all backgrounded apps, and run just SWConnect, and drive around while the app sleeps. Let me know what happens.
GarminDave, I noticed the same thing this weekend. I have been using SWConnect on my Iphones for a long time. I recently upgraded to the latest IOS. This weekend.. I only saw very sporadic data being displayed. So today, I did a test with leaving the app in the foreground and it worked fine. I think you are on to something here Dave. I concur it is an issue. I was not using any other mapping or navigation apps in either case so I don't think it was a conflict with navigation tools. I think something in the latest IOS changed and it is affecting SWConnect talking to Spotwalla.
I am the author of SWConnect. I had the chance yesterday to run a test. I don't have an iPhone Xs, but I do have the iPhone X. My testing showed everything worked fine. Admittedly, it was a fairly short test, about 25 minutes, enough to capture about 8 data points.
There one major thing that will cause points to be missed. Probably the most common is lack of precision from the GPS. The app ignores points that have low accuracy. If you're viewing the main page of the app, these show up down below in red status. Points that are accurate "enough" show up grey.
The app has two other criteria to accept incoming points. One is the 5 minute time threshold, and the other is a distance threshold. You must move at least 100 meters.
It's important to understand whether you are missing points within a larger grouping of points. I.e, you started tracking, and in one hour there are gaps in the tracking (without restarting the app). Missing points is entirely different than no points other than when starting and stopping tracking (those force entries).
I'd be interested in trying to determine which is happening. IF you can make a public trip that covers the data timeframe you're having problems, I can look at the messages. I have embedded debug information in the message part of the location message, which might help me in determining what is the problem.
I recently spoke with another customer who had initial problems, but his errors were due to GPS accuracy. When running later he had no problems, which leads me to believe (along with my simple test), that it's not necessarily an IOS issue.
I would love to help diagnose this, if you're willing to share a trip covering your outage timeframe.
Another wierd thing is halfway to Bryson City, I checked the Spotwalla page and it looked like I only made it to the local Starbucks from my house. It stayed like that for quite some time. I pulled the trip up today to make it public and now it looks like I only went around the block in Bryson City itself. Strange. It is a long way way Alpharetta Georgia to Bryson City South Carolina.
Also, fyi.. my phone is an Iphone 8 plus with IOS version 12.0 (16A366)
Hmm, thanks for the link. What's interesting, is that the trip info at the top shows 2 of 5 points displayed. I am unable to see the other 3. This "might" be due to a secure zone you've set up?
What would be helpful is to actually see the device messages. You have the ability to download your messages to a CSV file. If you could do that, and email to me (to keep this private), this might help further. To do that from the main menu select your name, and then "Devices" from the pull-down menu. This will open a page with a list of your device(s). From your device pull-down select "Browse Messages", which will bring up a page with all of the messages received from this device.
Near the upper left you'll see three buttons. Click on "CSV". That should download a file to your computer. Email that file to email@example.com, and I'll take a look at the data. I promise I will destroy the file after we've figured out what is happening. I appreciate you being willing to help.
PS: Just re-reading your post. So, if I understand you stopped at Starbucks at the start of your trip? Did. you use your phone while there? So, am I correct that this trip should have been from Alpharetta, GA to Bryson City? FYI, I googled and don't find a Bryson City in SC, but only in NC? What was the time (beginning and end) of your trip, and where did you start and end? You can post that info here, or include in the email with the data.
Ok. Sounds good Ray. I can do that. But not here at work. Our proxy will block that file with the GPS points thinking it is sensitive data. I will have to wait until I get home. I did have a 5 mile security zone from home. And yes.. Alpharetta, GA to Bryson City, NC. We left home around 8:30am, met up with the group at approximately 8:45am and headed for North Carolina at 9am. Landed in Bryson City sometime around 4pm I think. We took the long twisty road way to get there.
I don't recall using my phone (for voice) at Starbucks but I might have checked email and I was certainly messing with my music streaming (Slacker) to my helmet. All the usual things. hahaha.
Great. I look forward to getting the data and seeing what we can find. So the secure zone explains the missing data in that area? Certainly doesn't explain the rest of the many hours?
One thing I've learned is that when I stop and use my phone (in any way), I always check and restart SWConnect prior to heading out. This is easiest to do by setting "Auto-Tracking", which simply turns on tracking the moment you start the app. I have seen cases where running other apps while stopped will affect SWconnect by the operating system either killing it to get additional memory, or somehow disabling it. I know it's a bit of a pain, but making sure it's running just before starting, and making sure that other apps are not running in background which could cause the OS to try to purge apps to make space is a good thing.
No.. doesn't explain the rest of the hours of travel missing. I will check it is running frequently going forward. Can't hurt. The only change to how I have been using SWConnect is the IOS upgrade. I still currently blame Apple.
Just in case anyone is reading this, I wanted you to know that I haven't ignored Scott and his issues. He has been testing beta releases of the software for me to verify things are working. So far, at this point we believe that tracking wasn't enabled on his problematic trip. Whether that was caused by user error, (i.e. not turning it on), or something else, (like the OS killing the app, app crash etc) we don't know. But, given debug info in the messages, it is clear that tracking was restarted right before the end of the trip.
I have spent quite a few days in working on the app logic, to shore up any problems, and to provide better debug tools. Scott has been very generous with his time to assist me, and I believe everything is working as expected. I will be releasing a new version fairly soon.