Thanks! This is enough information to file a bug ticket. Long story short: my hunch is that at one zoom level the app is showing stale data (both bike availability and bike angels points) so I needed the station panel as a tie breaker to see what zoom level is wrong.
Thanks for the prompt responses.
Here is another example. Time is 6:21 pm 05/29/2024.
Screenshot attached.
I do have a follow-up question though. I understand the bike availability changes dynamically within the 15-minutes window (at 5:00, 5:15, 5:30, 5:45 etc), but aren't BA points stable during that 15-minute window? You mentioned that when we click on a station, the app fetches the most current availability and point value. Why does it get the point values out of cycle? Or does it mean the point assigned to this station is dynamic and depends on the instantaneous availability?
My naive conceptual understanding is that the BA algorithm runs once every 15 minutes and assign the point values for the next 15 minutes. The app, when starting up, will first get the current values, then at every 15 minutes boundary (5:00, 5:15, 5:30 etc) it refreshes the stored point values. If that's the case, then there really isn't a need to fetch point value when we click on a station. Alternatively, the points are dynamic, and what we see on the app is just a snapshot in time, so there would be a lot of stale values showing, which isn't quite right either.
Thanks for any clarification.
Thanks! This is enough information to file a bug ticket. Long story short: my hunch is that at one zoom level the app is showing stale data (both bike availability and bike angels points) so I needed the station panel as a tie breaker to see what zoom level is wrong.
I can confirm this bug is still present (3 months later) on the current Citi Bike app on my Android phone version 15.70.3.1722411100. The only workaround is to restart the app or wait for the next 15 minute refresh. The issue also happens sporadically for me and is annoying.
