I wanted to update this thread now that Iāve had more time to examine what is going on with this new release.
My conclusions are as follows:
1-The freezing issue does seem to be memory dependent, and deleting other apps, photos, etc. to allow the Tablo app more memory definitely helps.
2-The messed up sorting of recordings, as I described them with proof shown above, no longer appears to be a problem. Doing reset and reboot seems to have fixed that problem permanently.
3-The player no longer appears to be able to properly handle playback of recordings in progress. The previous version of the player had messed up scrolling/scrubbing but at least it was able to play any recording while the recording was still being made. This new version never allows any play back, but puts up a black screen with controls to pause, play, fast rewind and forward, along with a scrolling cursor, none of which work whatsoever.
None of these three problems existed in the prior version, which are used five days a week for at least a year on a daily basis to listen to recordings while on the road.
When the app is for whatever reason āupgradedā, after a very long (over a year) waiting time, all of these new issues show up, some immediately, some after use.
Unlike other threads I have started on this forum, where many other users have reported experiencing identical problems, I remain surprised that this specific thread and the issues it reports do not appear to be happening to others.
Are there other iPhone 6 Plus users out there who are not seeing these issues whatsoever? I find it hard to believe that my phone has some unique attributes which renders it effectively useless for Tablo playback.
I have mentioned previously that my role as an Apple developer does require beta installations of iOS, now on 10.3 . This is the only thing I can think of which could account for my extremely uncommon experience. I have had several beta iOS updates since the new Tablo app was installed, and all have behaved the same.
I plan to remove the beta profile from my personal iPhone as soon as the gold master of iOS 10.3 is released, to avoid any future confusion of this type. I would not be at all surprised if iPhone users who install the official 10.3 release of iOS will then begin to experience the problem I have been reporting.
Hopefully Table will then take whatever steps are necessary to get their iOS app for the iPhone fixed.
Larry