In short, mobile app development can be a mess. the "nuke" option - this is what I presume Strava did with Bluetooth Completely drop the use of the problematic APIs of the library, along with any features that use it - a.k.a. Developer opens a ticket with the library's developer, waits for a new version and hopes it's fixed in that version, integrates the updated library and performs testing, then rolls out new version of app Wait for the patch or fix from the developer of the library: Unless the bug or problem is of critical level of severity, often this is the default action. Switch to a different library: That can be a very costly endeavor especially if it requires refactoring your entire codebase to the new library, so it is often not considered an option and dismissed Rollback to a previous library: Only an option is it's proven that the library is the cause, and the developer doesn't need the newer version due to some feature they're using Try to workaround the problem: Sometimes possible, sometimes not, depending on the nature of the issue and how "deep" the problem goes When there is a problem that isn't directly a developer's fault, some of the options for the developer include: Google has been messing around with Location permissions, for example the relatively new security measure that only allows location access when the app has focus (which IIRC was introduced somewhere during Android 10). But the point is, sometimes something breaks either due to an OS or library update. Likewise, there are also several location-related libraries including Google's official APIs as well as third party implementations that a developer can use for location-based apps. Sometimes a particular stack is chosen because of a specific feature it has, sometimes it's mandated by some high level business requirement that the developer may not have a say in, or various other business and/or technical reasons we're not privy to. Problem is, from a developer standpoint, there are multiple Bluetooth stacks available, each with their own pros, cons, and unique quirks. I recall the abovementioned Strava issues were related to Bluetooth crashes. The problem with mobile app development is that things rapidly change, and something that used to work flawlessly can suddenly break due to a change in security protocol, or even some routine update, and sometimes not even the developer's fault. I am not looking for solutions so much as I am wanting to know if anyone is experiencing similar difficulties or similar lack of support from Ride with GPS. They gave me an extra 6 months of subscription for free but that is like being given free frustration. On Monday this week I rode 50 miles and the app did not skip a beat for the one and only time in the past 7 weeks, but today I rode 10 miles and the app quit 100 yards down the road.Īt this point I am extremely disappointed in their response. I have checked my phone settings, as they requested, and downloaded a supposedly new and improved version of the app. I contacted Ride w/gps a month ago and although there has been a more or less continuous exchange of emails the basic response is " the information has been sent to the developers." It will start up okay but at some point will stop tracking and at the end of a ride fill in between two random points with a straight line. My Ride with GPS app stopped tracking my rides 7 weeks ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |