Opened on my iPad (non beta) detection took 16s to load, opened on the iPhone (beta) and it was there immediately.
Perhaps that’s serverside caching?
The new beta so far works beautifully. On the regular app it’s been a restart nightmare the last few days. Not so much due to stuck predictions, but the app not loading properly on startup and occasionally running into the black screen of death. (stuck). No such issues in Beta (yet)
Just had the issue happen again in Beta: After modifying the duration of my workout for today, the adaptation triggered but workouts and prediction didn’t load. Left it running a bit, made another video (let me know if you’d like to have that one too - this time it’s the originally described setup without any progress bar but otherwise identical) and then restarted the app as I’m a bit short on time to do the workout. Hope the logs made it anyway. As before, workout and prediction were magically finished loading.
I logged in this morning to a test flight message that a new version was out that resolved the black screen. Unfortunately, it seems to have brought it back.
After about a minute, it changed to this
And eventually to this.
It never recovered fully, but if I click the hamburger it then brings me to the normal “Career, Calendar, etc.” menu.
@Pbase are you still running into issues with this?
Nope! I’m still on the beta with zero app issues.
@martenk, are your issues happening on the beta app?
On Beta I only saw it once, IIRC, which was the time I posted about before in this thread.
But when I left the beta program a week or two ago under the impression that the issue was fixed with the other Apple problem, the problem started to occur again.
Did it occur more than once?
I wonder if when you got back on the production app, you were still on an older version, and it updated once you reopened it.
On Beta, only once. On Prod also only once, but I’m only getting back into more active training right now, so there weren’t as many opportunities for it to happen yet.
When switching to Prod I made sure to have the latest version installed. Unless you refer to something cached internally by the app, I don’t think this happened
No problem in recent weeks - I’m back on prod now both devices
Let me know if you run into that issue again. 