Unlikely pairing causes a problem at the API/server level. There should (but who knows what goblinry lurks there) be no interaction with the servers during the pairing process (maybe after a successful pairing).
My guess is that people who don't have any sensors hit the pairing button because it's not clear that they don't have to, because they don't know any better, and it causes crashes because it's shitly written.
Rather than fix the bugs they're using it as a crap excuse to remove some functionality they don't really want to have to continue to maintain.
I guess they just want people to use a different device (Garmin/TomTom/Fitbit/Suunto/Apple watch/cycle-computer/etc) to deal with the difficult ANT+/BLE stuff and then Strava (the website) just receives the data that is uploaded. The app is then just for people who aren't interested in smart watches/devices and who just want to log a run/cycle, or for people to browse the feed and show off to others.
Unlikely pairing causes a problem at the API/server level. There should (but who knows what goblinry lurks there) be no interaction with the servers during the pairing process (maybe after a successful pairing).
My guess is that people who don't have any sensors hit the pairing button because it's not clear that they don't have to, because they don't know any better, and it causes crashes because it's shitly written.
Rather than fix the bugs they're using it as a crap excuse to remove some functionality they don't really want to have to continue to maintain.
I guess they just want people to use a different device (Garmin/TomTom/Fitbit/Suunto/Apple watch/cycle-computer/etc) to deal with the difficult ANT+/BLE stuff and then Strava (the website) just receives the data that is uploaded. The app is then just for people who aren't interested in smart watches/devices and who just want to log a run/cycle, or for people to browse the feed and show off to others.