You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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:
Look at the Arkansas River. Numbers section
AW website: 1450 (correct)
Android app: 2080 in the list
Android app: 1110 when clicking through to the river page (refresh not available)
Ios app: 1110 list
iOS app: 1110 on page (refresh does not work - 2 years old)
the Fractions section in my iOS app is reading 774 and 2 years old in both the list and river page but will not refresh.
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.
@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
@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.
The text was updated successfully, but these errors were encountered: