Due to requirements from Google to target their latest OS and also have 16kb page sizes, this is going to force me to increase the minimum supported Android version to 7.0. There is literally no way for me to continue supporting older Android devices through Google Play with these requirements, as the third party libraries that I use will only work on Android 7.0 or higher. For users on older devices, the only option will be to switch to my FastSpring version. While I will continue trying to support older devices for a little bit longer, the nature of the changes is such that it will cause a large number of development headaches, so at some point I will have to fully drop support for users on older devices. Based on the statistics shown by Google Play, less than 1% of my users are on devices older than 7.0, so this will not affect the vast majority of users.
Mike
Interestingly I have an old tablet from 2016 with Android 4.4.4 (Blaupunkt Endeavour 1013). I just got the update to the latest MobileSheets version 3.9.20. I didn't notice any problems and even the new abc features work smooth.
I haven't released the update yet that will force the new minimum version. I'm addressing other problems first.
Mike
Thank you. I will keep an eye on it and change to fastspring or maybe look for a new tablet. Something new was on my list for quite some time...
Just got a fastspring version and will check it out. Thank you
That will certainly let you continue using the app longer while still receiving updates. I'll do what I can to port changes over to keep the legacy version compatible as long as I can.
Mike
Having installed the legacy version from fastspring, there is a problem with the internal updates.
I do get a notification about a new version
and it downloads the new version
In the end there is an error when installing
Sometimes I got an error during the download
The messages don't mention anything about legacy version. Might it be that it downloads the "normal" version instead of the "legacy" version?
I don't like the installer link being posted publicly, as it's only for customers who have paid through the FastSpring store (even though there is an additional layer of licensing, I don't want people who didn't pay downloading it), so I had to remove your attachments. Contact me at mike@zubersoft.com and we can continue the conversation there. I'll certainly look into this to see if I can reproduce the issue though.
Mike
(09-15-2025, 10:53 AM)Zubersoft Wrote: [ -> ]I don't like the installer link being posted publicly, .... Contact me at mike@zubersoft.com and we can continue the conversation there. ...
My apologies, Mike. I didn't think of this implication when posting. I will continue this topic directly with you.
Martin
(09-09-2025, 05:56 AM)Zubersoft Wrote: [ -> ]Due to requirements from Google to target their latest OS and also have 16kb page sizes, this is going to force me to increase the minimum supported Android version to 7.0. There is literally no way for me to continue supporting older Android devices through Google Play with these requirements, as the third party libraries that I use will only work on Android 7.0 or higher. For users on older devices, the only option will be to switch to my FastSpring version. While I will continue trying to support older devices for a little bit longer, the nature of the changes is such that it will cause a large number of development headaches, so at some point I will have to fully drop support for users on older devices. Based on the statistics shown by Google Play, less than 1% of my users are on devices older than 7.0, so this will not affect the vast majority of users.
I had a private email exchange with Mike where I asked:
Quote:Will you keep compatibility at the file level? In other words, after Jan 1 can I continue to sync all my devices, even the one running the legacy version, to the same Dropbox folder?
and Mike wrote:
Quote:If you are just synchronizing files outside MobileSheets, that's not a problem. If you are using the synchronization in MobileSheets, that will only continue to work until I change the database. At that point, the old version will become incompatible.
Does that mean the format of the database file stored in Dropbox,
mobilesheets.db, is changing? Will I have to rebuild that
.db file, or will there be an automatic conversion?
That just means that over time, I may add new things to the database. If I do that, then the old version won't know about those new additions which creates an incompatibilty. There is nothing you have to rebuild or do.
Mike
(09-14-2025, 02:00 PM)Zubersoft Wrote: [ -> ]That will certainly let you continue using the app longer while still receiving updates. I'll do what I can to port changes over to keep the legacy version compatible as long as I can.
Mike
I had the same problem with Google play, and after some help from Mike, purchased the legacy edition from Zubersoft store. I get the same failure signal when I try to update using mobile sheets, but using a browser I can download the updated legacy edition using the link I got from Fastspring after purchasing. Basically the link ends in mobilesheets_legacy.apk rather than mobilesheets.apk
I will continue supporting that legacy installer at least until January 1st.
Mike