12-27-2019, 04:19 AM
As mentioned in the release notes (https://zubersoft.com/mobilesheets/forum...4#pid27604) version 2.8.0 and version 2.8.1 have some issues with database access (this causes an unrecoverable error during initialization that stops much of the app from loading correctly). Once I was made aware of the problem, I submitted an update Tuesday morning, but it was too late as Microsoft hasn't approved the update since then. I'm hoping they will approve it today, but there is no guarantee.
If you want to be able to roll back versions, you'd have to use the FastSpring version of MobileSheets (https://zubersoft.onfastspring.com/) which I distribute myself but is licensed per device. We can switch you over to that version if you want to have more control over when you update and the ability to install older versions. Having said that, I'm able to update that version immediately, so there is rarely a situation where there is a known bug that I can't fix right away. FastSpring users of the Windows 10 version have been on version 2.8.2 since Tuesday, so they haven't seen these issues.
Chen - yes, I do need to produce some kind of log or status window that shows which files MobileSheets encountered problems with. This is on my list of things to do.
Spidron - you may find that you still encounter the issue sometimes. Switching the language like that caused the database to be reloaded, which probably got around the problem. If you fully close the app and restart it, the same problem may occur again. So that's a workaround, but not really a fix.
Sorry everyone for the problems this update has caused - I was trying to fix some major memory leaks by updating code in one of Microsoft's libraries which was a pretty important change. Unfortunately, I managed not to see all the problems during my tests.
Mike
If you want to be able to roll back versions, you'd have to use the FastSpring version of MobileSheets (https://zubersoft.onfastspring.com/) which I distribute myself but is licensed per device. We can switch you over to that version if you want to have more control over when you update and the ability to install older versions. Having said that, I'm able to update that version immediately, so there is rarely a situation where there is a known bug that I can't fix right away. FastSpring users of the Windows 10 version have been on version 2.8.2 since Tuesday, so they haven't seen these issues.
Chen - yes, I do need to produce some kind of log or status window that shows which files MobileSheets encountered problems with. This is on my list of things to do.
Spidron - you may find that you still encounter the issue sometimes. Switching the language like that caused the database to be reloaded, which probably got around the problem. If you fully close the app and restart it, the same problem may occur again. So that's a workaround, but not really a fix.
Sorry everyone for the problems this update has caused - I was trying to fix some major memory leaks by updating code in one of Microsoft's libraries which was a pretty important change. Unfortunately, I managed not to see all the problems during my tests.
Mike