jasonh300 wrote:And it's been 3 days since I posted the update that the developers have recognized the problem and are working to find a solution...2 days of which have been a weekend. This isn't the only problem that they're working on.
Why take it so personally Jason? I'm not sure why you would say it's been 3 days and just 1 working day. See all the below history:
On Nov 8th (10 days ago) at viewtopic.php?f=10&t=31184&start=60#p285149
you posted "Support had been contacted directly about this and they're looking into it, as of this morning."
On Nov 11th (7 days ago) you again posted asking for more info the developers asked you, though I think if they glanced at the thread they would have found references to dates of missing drives that were still listed but not showing as editable.
Now 3 days ago you posted viewtopic.php?f=10&t=31184&start=120#p291782
which indicates they were telling you "OK, it seems that this is a problem in processing some new drives. There's a status update on the Status-Page and we're working on a fix.". Some of my editable areas for drives were newer (within a few days of when the problem started) and some weren't. Sure, it could have been the way it was phrased or they could be working on an issue they found that is different from the problems reported in this thread that I started.
Anyway as a professional developer I understand there are often multiple problems to deal with but also being responsible for teams of developers and revenue associated with what is released, I'm extremely aware of prioritization. Maybe this isn't the worst or most impactful issue they have but from my end it's the only one I'm having. If the team is the same one working on the front-end client, maybe they are focused on that and what I consider a poor decision to release the new client in the state it was in. I'm glad I followed all the beta posts and decided against upgrading my Android app for the time being.