removal of BLE sensor support

Hi team Strava,

I'm really gutted to hear your are planning to remove BLE sensor support from your mobile apps. The alternative you mention (use another app to record your sensor data) isn't a real alternative: now I have to switch apps (during a workout!) in order to have a look at either the route or my HR. I have been a very happy paying member of your community because you serve al my needs in one integrated environment.

I will now have to either buy a head unit, or move to a different app that does help me with performance preparation, recording and reviewing in one storefront. Both options are a downgrade from my current Strava app experience but I'm afraid I don't see another option if you remove BLE sensor support. Isn't it possible to containerise BLE within the app so if users don't use it they are not bothered with the implementation of it? I btw personally have not had any crashes that I could relate to BLE sensor support.

160

コメント

265件のコメント
  • I had just renewed my Strava yearly subscription last month.

    This morning I submitted a support request to Strava requesting a pro-rated refund for the remaining year, due to the degradation of Summit features that I can no longer use now that I need another application (Beacon, Live Segments).

    They were really prompt and refunded the whole year. So vote with your wallet people! It's the only way to register your unhappiness with this retrograde move.

    In my reply I did note that I would resubscribe if the sensor support was reinstated.

     

     

     

     

     

     

     

     

    5
    コメントアクション Permalink
  • I can't believe that strava is going to have this mistake.... Really everything has its growth, heyday and decline, it seems that strava has begun its journey to the end.

    3
    コメントアクション Permalink
  • WTF! How pathetic. You cannot fix your app to properly interface with Bluetooth when historically I have had no problem in the past?

    This sounds more like a ploy to force me to buy expensive dedicated gear.

    Well, if you don’t fix this I will be looking for an alternative to Strava!

    I’m will be wasting money subscribing to Summit.

    4
    コメントアクション Permalink
  • I will cancel my subscription too. I do not use any bike computer, strava was a good choice. Unfortunately was.

    4
    コメントアクション Permalink
  • Yes, I see no reason to continue my Summit subscription when I can't get the data for it because you removed the main feature feeding in data. Pretty disappointed. Other Apps can work with these sensors flawlessly. If I have to switch up my hardware, I will also switch up my software - away from Strava. Easy enough.

    3
    コメントアクション Permalink
  • Год пользуюсь связкой Strava и Bluetooth. Никогда не было проблем. Разочарован. Придётся уйти из Strava.

    2
    コメントアクション Permalink
  • Really a bad decision. My BT HR monitor is working really fine with the app. I use most of the time a GPS for tracking my rides, but sometimes I just don't feel like switching the GPS from bike to bike and use the phone instead. I also use the phone for runs instead of the GPS because my GPS in my pocket goes crazy about altitude gain (as it is based on air pressure and in the pocket it simply does not work) and hence I use a phone in my pocket for that (as strava bases altitude gain on the map rather than air pressure). If I am forced to always use the GPS I will be messing many things..

    3
    コメントアクション Permalink
  • Bye bye Strava. What a hopeless decision to make. Saves me my premium fee if nothing else.

    4
    コメントアクション Permalink
  • The iOS app & Polar HR belt worked flawlesly so far for me. The given explanation does not sound convincing. I will cancel my Summit membership when the support is removed. Please reconsider.

    3
    コメントアクション Permalink
  • I chose Strava because it would be the ONE app I would use to track all of my activity.  I have been using it with an HRM, a cadence sensor AND a speed sensor when I ride indoors because the ONE app would cover every type of riding that I do. I have never had the app crash under these circumstances.  Your decision would indicate that it would be a common problem shared by all users of such devices.  Instead of discontinuing support for direct Bluetooth and ANT+ device pairing, consider why it works perfectly for myself and I am sure many others.  Like others who have posted, I too will no longer be a Strava user if you choose to implement this.  The social aspect of your app is not compelling enough to make me keep it in light of the horrendously reduced functionality.  I have ridden thousands of miles before Strava, and I assure you, I do NOT need your product to ride thousands more.

    5
    コメントアクション Permalink
  • Very disappointed that this feature is being removed. Like everyone else in this thread, I've never had an issue with Strava crashing despite having a Bluetooth HR strap paired with the app.

    So now you want us to use another app... whose developers can apparently get it to work without issue.

    Just to add insult to the situation - I keep getting Strava banners in the app and on the website telling me to use my heart rate data for analysis in the various other features. lol.

    3
    コメントアクション Permalink
  • I would like to request that one of the millions of athletes whose Strava Apps crashes post a reply to this thread with their story.  So far there is no evident anyone has problems with bluetooth crashing their app.

    4
    コメントアクション Permalink
  • I'm also jumping in on this inconceivable decision by Strava to discontinue Bluetooth support.  I started using Strava exclusively several years ago to track my activities.  Gone was the cycling computer attached to my stem that would make me stare down at my numbers instead of look up and enjoy the ride.  Now, it was grab my phone, pair my HR monitor, hit "record" and hammer down.  At the end of my ride (or run) I could instantly see my HR zones, fitness, and freshness, and power and HR averages.  To add insult to injury, now Strava is encouraging me to use another company who managed to figure out Bluetooth connectivity and upload using another app?  I'm seriously questioning the quality of the MBA program at Northwestern University which Mr. Quarles attended.  Unless this terrible business decision is rectified immediately, I will be cancelling my Strava membership.

    5
    コメントアクション Permalink
  • This really sucks. I use this good functioning(!!!!) option frequently. Fix it instead of taking it down!!

    4
    コメントアクション Permalink
  • Paid Summit user here also.  Completely unacceptable to remove features from a paid subscription service rather than fixing the bugs.  Truth be told, Strava under-performs in nearly every aspect except for social media.  The mapping utility is buggy as hell and lacks many of the mapping features of competitors.  The recording of rides has actually gotten worse over time instead of better.  And now they are actively removing much needed and desired features for cyclists and endurance athletes.  Hopefully MapMyRide, Komoot, or RideWithGPS will incorporate segments, KOM's and some social media aspects and we can just leave Strava all together.

    5
    コメントアクション Permalink
  • So what other apps are people trying out to replace Strava?

    2
    コメントアクション Permalink
  • I can't imagine what the real reason might be to remove this basic feature (at least if it is technical). It just cripples the recording feature. Why not remove the recording feature entirely then? If I am supposed to use a separate device it will also do the recording of the entire workout. I wonder what that crashes given as the reason for are supposed to be. Can't remember any with strava. If they occur with certain device combinations it might also be the gps device as well, then again the recording feature is obsolete entirely.

    You can remedy this crashing issues simply by giving a warning to users who want to use a sensor that it might crash the app. Removing the feature for this reasong is complete nonsense.

    Edit: I canceled my subscription and after contacting support got a full refund. Thats fair at least, so thanks for handling it that way. i am quite intent to see what better explanation for this course of action by strava will appear in the near future.

    2
    コメントアクション Permalink
  • PATHETIC!!! At least could have given Summit users the ANT+ & Bluetooth support as they pay for this anylitical service anyway.

    The fact you will be taking a major part of the service away on such short notice what other stupid announcmets will you make?

    You have lost my support and sure pro-atheletes probably use a better service than you offer. Unkudos to Strava.🤬

    3
    コメントアクション Permalink
  • The stated reason for cancelling ble support isnt believable. Is this some vc play, youve reprioritized? Did you lose key developers? Because what youre saying is just dumb. Step up and fix it or i too will be leaving.

    Happy app with ble hrm user on iphone for more than 5 years. Love the app for recording and upload even though i track my recorded rides with goldencheetah.

    3
    コメントアクション Permalink
  • Just cancelled my premium.

    I have been a massive advocate of the app for years but this move completely removes most of the use case for Strava. Without sensors the app seemingly becomes useless for 'in activity' use and is relegated to an 'after the event ' social media platform (which is a very crowded market space) and for which there is no need to pay.  Really disappointed by this retrograde step for what  I consider to be the prime purpose of the app for me .. to manage power and HR while riding and running . Having it all in one device was just a great and simple solution

    A few days notice on this change , not enough to sort out alternatives, with very little useful info on alternatives.  Have yet to find out if a sensor receiving device for  Powermeter and HR sensors can then feed the app live, or is that only an end of activity upload that is performed?

    I also dont believe the app was crashing for so many users, so that seems complete BS as well as a rationale- must be more to it. 

    2
    コメントアクション Permalink
  • So all other app suppliers in the world can make this work but not Strava! How pathetic. I am a full summit member and will be cancelling my subscription if you do this.

    2
    コメントアクション Permalink
  • As a result of this I've just cancelled my Summit subscription.  Has anyone had success seeking a partial refund for an annual subscription?

    Edit, my subscription (from Google Play) was fully refunded after I complained.

    2
    コメントアクション Permalink
  • I want a refund of my annual Summit subscription. I’ve enjoyed the first 6 weeks of real time HR and Cadence, but it now appears the final 46 weeks will be useless for my particular setup. Strava, you’re dishonoring our arrangement and I want my money back (minus the good first 6 weeks of course). I’ve raised a ticket in the iPhone app and am awaiting the refund of 46 weeks of Summit.
    Wish we didn’t have to part so soon.
    Sean G

    edit: it took 4 minutes for Strava to issue my refund. Thanks Strava for your excellent service over the years, I wish you good luck for your future path. 

    3
    コメントアクション Permalink
  • Have just cancelled my summit membership which I’ve held for a number of years. This ludicrous decision completely nullifies Strava as a usable platform for anything other than posting rides.

    will happily renew if this is sorted, but for now I’m done.

    2
    コメントアクション Permalink
  • Thank you Strava for saving me money. 
    i will move back to Map My Ride, save money, and use it as my activity aggregator.

    your explanations are weak and make no sense. I do not believe that "millions" of people have had crashes due to connecting sensors to the app.

    it would be cheaper for you to hire away programmers from wahoo or polar or garmin to fix this than suffer through the drop in revenue from paid subscribers leaving. THAT will be "millions"

    answer this...why would i continue to pay for strava?

    4
    コメントアクション Permalink
  • Cancelled.   Bluetooth devices were the only reason I had to pay for this service.   If Strava changes this silly decision i'll change mine!   Nice timing though - my sub was up for renewal in 2 weeks.

    2
    コメントアクション Permalink
  • I just paid for another full year of Summit last month, I’d like to get a refund, I’m not going to spend several hundred dollars more to do exactly what has always worked perfectly for me, no crashes, no bugs, ever. I have my music, my heart rate, segments, maps, can make an emergency call, have access to look up trails, etc. all on my phone, I’m still going to need to bring this with me, except now I have to have another device to do it? I want a headset for my bike, but I can’t run with that, so I’d really need two pieces of equipment to match it! Fix the bug, otherwise, strava will disappear, people don’t want to use a service that can’t handle fixing bugs in their software.

    3
    コメントアクション Permalink
  • Vote with your dollars!

    If more people cancel, maybe they will listen, if they bring it back you can subscribe again!

    I Just requested a prorated refund for my annual subscription, I paid so I can have one app/one device for my running and biking, keep my music with me, be able to talk to my wife if I need to or if she needs to reach me. If I have to use another app, there isn’t really a purpose to having strava at all, it’s just any other gps mapping software, and there are plenty of free ones out there that can track my heart rate as well.

    2
    コメントアクション Permalink
  • I’ve recorded 35,000km with Cadence and Wheel Sensor via BLE and Strava without issue.

    Where are all these mysterious users with stability issues?

    5
    コメントアクション Permalink
  • As an iOS developer, I'm struggling for an explanation as to what the problem is and why this is the "right" solution to it. A statement from the email says:

    "We recently discovered that pairing Bluetooth heart rate monitors and power meters directly with the app is causing Strava to crash for millions of athletes — most of whom don’t even use these kinds of sensors."

    I'm wondering whether the key to this is the combination of the word "recently" (since iOS 13) and the apparent paradox of how not pairing a device which a user hasn't got is reported as the cause of the problem for many.

    iOS 13 now asks for permission to use Bluetooth (previously it did not require permission but certain kinds of apps were using Bluetooth as a sneaky way to learn something of your location, even if you'd refused location services permissions). Could it be that users who have no intention of pairing a device are refusing Bluetooth permissions when prompted (it happens the first time an app attempts to use Bluetooth after upgrading to iOS 13) and the app is then making assumptions about Bluetooth availability (perhaps force-unwrapping a nil value, in developer speak), leading to these crashes?

    If that is the explanation, fixing it should be close to trivially easy.

    Even if that isn't the explanation, putting Bluetooth behind a big "I want to use Bluetooth" toggle switch in the app would protect all the sensor-less users while being a one-time minor inconvenience to those of us who have been happily and reliably using the feature for so long.

    9
    コメントアクション Permalink

ログインしてコメントを残してください。

お探しのものを見つけられませんでしたか?

新規投稿