You don't need to be an 'investor' to invest in Singletrack: 6 days left: 95% of target - Find out more
I did a lap of Swinley yesterday, uploaded the ride into Strava on my phone & noticed 47 achievements when the upload was complete.
Went to have a look at the detail when I got home & it's not showing achievements (the little trophy symbol) for any of my rides, so I can't see if I got any PBs yesterday
Any idea how I get them back?
My phone doesn't show the new 2015 yearly achievements individually. It does however show the total number. I have to look on my pc to see them. The only ones that actually show on my phone are overall pb's.
Mine does this sometimes...they usually filter through in the end at some point.
I know it's lame but it's actually quite annoying when you think you've got a PB on something you were aiming for 😆
The ride I did earlier today is already showing the achievements (Android app)
Update your app to the latest version
Sometimes happens to me. Changing the activity from bike ride to run then back again works for me.
My older app version sometimes gets confused and shows the cups for someone else's ride alongside mine. The web is always right though.
Hi Legoman I had the same problem every time I did a ride. i contacted strava who were pretty helpful.
In my case I am using an I-phone 4s with the old IOS software. There is a bug with using the older IOS system as strava was updated to run smoothly on the latter IOS. The most simple solution was to get on the PC go into settings and and make each ride private, then public again. This is a work around for the IOS problem.
I am not suggesting you have the same problem, but doing the private / public thing may work for you too.
Have they ditched the in-year PR badges? I've not seen one for a while despite doing some quickest (for me) this year times. My world is destroyed as a result and the lack of that hollow symbol in my life is eating away at my self esteem and causing devastation to the local kitten population.
I noticed that today thepurist. No idea.
Edit . wrong thread
Cheers everyone, looks like it was the old iOS that was the problem
NorthCountryBoy - your fix seems to have worked, thanks buddy!