The bug was fixed in 4.28.2. Do you need to activate many? I have 4.27 on an old phone and the last backup activated. There I can see which tracks were visible. Otherwise, you could install 4.27 and install a backup. Assuming you have not made any changes in the meantime. Then install 4.28.2 and do the conversion again.
The bug was fixed in 4.28.2. Do you need to activate many? I have 4.27 on an old phone and the last backup activated. There I can see which tracks were visible. Otherwise, you could install 4.27 and install a backup. Assuming you have not made any changes in the meantime. Then install 4.28.2 and do the conversion again.
Hiding the tracks probably occured when I started 4.28.1. So the tracks were already hidden when the fix was in place. I already went back to 4.27 and restored an old backup. But thanks for confirming the fix. So I can upgrade to the most recent version now.
Hiding the tracks probably occured when I started 4.28.1. So the tracks were already hidden when the fix was in place. I already went back to 4.27 and restored an old backup. But thanks for confirming the fix. So I can upgrade to the most recent version now.
Nope, after upgrading to 4.28.2, tracks are all hidden again. Even restoring the very same track backup into 4.28.2 makes the tracks invisible while in 4.27 the same backup keeps them visible like they were when creating the backup (incl. those who were hidden as well).
Nope, after upgrading to 4.28.2, tracks are all hidden again. Even restoring the very same track backup into 4.28.2 makes the tracks invisible while in 4.27 the same backup keeps them visible like they were when creating the backup (incl. those who were hidden as well).
sorry for the inconvenience. The track visibility status is not part of the backup, it is written in the migrated database. On some rare occasions, the status is reset and all tracks are hidden from the map. Working on indicating the issue but if you migrated your database, another migration will not solve your visibility status.
Hi all,
sorry for the inconvenience. The track visibility status is not part of the backup, it is written in the migrated database. On some rare occasions, the status is reset and all tracks are hidden from the map. Working on indicating the issue but if you migrated your database, another migration will not solve your visibility status.
Understood. But when I make a fresh install of 4.27 and restore a backup, visibility is fully restored too. When I THEN upgrade to 4.28.2, shouldn't visibility remain as in 4.27?
Understood. But when I make a fresh install of 4.27 and restore a backup, visibility is fully restored too. When I THEN upgrade to 4.28.2, shouldn't visibility remain as in 4.27?
Anyway, would you please send the backup for a test? The main dev has informed me that he actually found something and your backup file could prove the indication (leading to a fix of this). Thanks!
Anyway, would you please send the backup for a test? The main dev has informed me that he actually found something and your backup file could prove the indication (leading to a fix of this). Thanks!
I opened a private ticket with a link to the backup file and this ticket. Unfortunately the file was too large for any kind of attachment in an email or inside the ticket. (>120 MB)
I opened a private ticket with a link to the backup file and this ticket. Unfortunately the file was too large for any kind of attachment in an email or inside the ticket. (>120 MB)
Worth for me, yes. Easier, no. I've been using the feature of making tracks visible or invisible since I started using a paid LM more than 5 years ago in order to distinguish routes I hiked from those I haven't hiked yet. It's almost like a hiking diary to me. We're talking about a high 3-digits number (including future ones), not just a few ones. Sometimes that's also hiking-wise one of my major preparations for returning to a previous hiking vacation because it shows what I wanna do or what I still wanna do when I get back to the place sometime later. There can be years in between which makes it hard to remember what I already did especially when tracks are close to or merely variations of each other. That's my motivation. Please understand that I won't discuss whether that's a reasonable one (which I'm sure you guys won't). It's what I do and it's why it would be a pain in the ass for me if I'd loose that yes/no information without a chance for recovery - even if it means going back to a previous version, restoring the backup incl. visibility info (which works up to this point) and installing the update again with a fully restored library (which does not work so far). On top of it, it seemed I can't install the version from the store once I used an archived apk. So restoring my backup into 4.28.2 from the store AND thus restoring the visibility information will be vital to me.
Worth for me, yes. Easier, no. I've been using the feature of making tracks visible or invisible since I started using a paid LM more than 5 years ago in order to distinguish routes I hiked from those I haven't hiked yet. It's almost like a hiking diary to me. We're talking about a high 3-digits number (including future ones), not just a few ones. Sometimes that's also hiking-wise one of my major preparations for returning to a previous hiking vacation because it shows what I wanna do or what I still wanna do when I get back to the place sometime later. There can be years in between which makes it hard to remember what I already did especially when tracks are close to or merely variations of each other. That's my motivation. Please understand that I won't discuss whether that's a reasonable one (which I'm sure you guys won't). It's what I do and it's why it would be a pain in the ass for me if I'd loose that yes/no information without a chance for recovery - even if it means going back to a previous version, restoring the backup incl. visibility info (which works up to this point) and installing the update again with a fully restored library (which does not work so far). On top of it, it seemed I can't install the version from the store once I used an archived apk. So restoring my backup into 4.28.2 from the store AND thus restoring the visibility information will be vital to me.
The bug was fixed in 4.28.2. Do you need to activate many? I have 4.27 on an old phone and the last backup activated. There I can see which tracks were visible.
Otherwise, you could install 4.27 and install a backup. Assuming you have not made any changes in the meantime. Then install 4.28.2 and do the conversion again.
The bug was fixed in 4.28.2. Do you need to activate many? I have 4.27 on an old phone and the last backup activated. There I can see which tracks were visible.
Otherwise, you could install 4.27 and install a backup. Assuming you have not made any changes in the meantime. Then install 4.28.2 and do the conversion again.
Hi all,
sorry for the inconvenience. The track visibility status is not part of the backup, it is written in the migrated database. On some rare occasions, the status is reset and all tracks are hidden from the map. Working on indicating the issue but if you migrated your database, another migration will not solve your visibility status.
Hi all,
sorry for the inconvenience. The track visibility status is not part of the backup, it is written in the migrated database. On some rare occasions, the status is reset and all tracks are hidden from the map. Working on indicating the issue but if you migrated your database, another migration will not solve your visibility status.
You can send an email to locus.map@asamm.com Or open a private ticket. In both cases, include a link from this ticket so that there is a reference
You can send an email to locus.map@asamm.com Or open a private ticket. In both cases, include a link from this ticket so that there is a reference
Hello Mac Bo,
as a main Android developer, btw. sorry for this, I have to ask > does it worth it? Isn't it easier to re-enable "few" tracks again manually?
Hello Mac Bo,
as a main Android developer, btw. sorry for this, I have to ask > does it worth it? Isn't it easier to re-enable "few" tracks again manually?
As this issue is now being solved privately, I'm closing the topic. If there is any news, I'll reopen it.
As this issue is now being solved privately, I'm closing the topic. If there is any news, I'll reopen it.
Replies have been locked on this page!