Open ngottlieb opened 11 months ago
@AWKevin can you confirm that you updated the app when Greg released the changes I made a month or two ago? And that nothing happens when you refresh either on reach detail level or on the whole Colorado river list?
Yes, refresh is broken on both.
Yes, I am on 1.4.2(1)
Kevin Colburn National Stewardship Director American Whitewater 828-712-4825 @.*** www.americanwhitewater.org
On Mon, Jun 26, 2023 at 12:24 PM Nick Gottlieb @.***> wrote:
@AWKevin https://github.com/AWKevin can you confirm that you updated the app when Greg released the changes I made a month or two ago? And that nothing happens when you refresh either on reach detail level or on the whole Colorado river list?
— Reply to this email directly, view it on GitHub https://github.com/AmericanWhitewater/wh2o-vue/issues/551#issuecomment-1607820668, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4RVJ6PQUQBM3XTQQIV3PLXNGZVBANCNFSM6AAAAAAZUMLUAY . You are receiving this because you were mentioned.Message ID: @.***>
When you refresh the full list of Colorado rivers, do other reaches update and just not the Numbers / Fractions? Or is nothing updating? @AWKevin
Both are updated now. I have no idea why.
@AWKevin reports (along with multiple users) an issue where both apps seem to be stuck on a two year old gauge reading for a reach that has multiple up-to-date gauges:
The 2080 on the Android app is accounted or by the confusing primary/non-primary multiple gauge configuration, but @AWKevin's iOS app being unable to refresh from a two year old reading and the 1110 reading on Android detail page don't seem to be explained by that. This isn't a consistent issue: I don't see it on my iOS app, so maybe some old gauge that no longer reports is being cached and continually requested by the offending phones.
Spawned from discussion in https://github.com/AmericanWhitewater/wh2o/issues/2724.