Subscription pricing
Good morning, tech gurus.
I often use the 7sage iPhone app to view the discussion boards. Sometimes—particularly on threads that have a lot of replies or a number of long replies—the text does not render. I should say—the text will display briefly and then disappear. While I am able to scroll (usually still seeing nothing, except the 7sage disclaimer at the bottom which is always visible when I scroll to that point), the text of the thread does not load in sprite of refreshing, closing the app, starting from the Discussion main page and re-navigating to the thread in question, etc. The app frame and menu remain visible—but the majority of the text does not display.
This is an intermittent problem but occurs often enough to suggest a bug. I'm in iOS 8.2 on an iPhone 5s.
0
10 comments
I'm also having this issue on my 6+
No problem :) Thanks for the hard work!!
@2543.hopkins The update should come from our server side. I retested that thread on iPhone 5S and got the blank screen to reproduce :( This is going to take a long time to figure out, sorry!
I just had it on another thread as well.
Alan—unfortunately I'm still having the same problem (just had it when looking at the "Gaining back confidence" thread). I checked the App Store and didn't see an update—did you mean it's forthcoming from there?
@2543.hopkins @2543 I rolled out a fix a few minutes ago that should help. I'm not getting a blank screen anymore on iPhone 5S 7Sage app. Please let me know if you are still running into this problem
This explains why mine never loads
Thanks, @alan-91620 —best of luck on the bug-hunting!
@2543.hopkins @2543 Thanks for letting us know about this! I got this to reproduce on the http://classic.7sage.com/discussion/#/discussion/2322/february-lsac-scores discussion using iPhone 5S iOS 8.1.3. This will probably take a while to fix - I have trouble debugging this particular setup :|
Good news is that I couldn't reproduce it on iPad, iPhone 6, or Safari app (instead of the 7Sage app). So in the meantime, please try using one of these options. Sorry for the trouble!
This occasionally happens to me too. Particularly on threads with a lot of comments.