[Bug]: Dive Locations dissapear from previouly recorded dives.

[ronhenry10]

Description

Seemingly random dive locations have suddenly been deleted from about 62 out of 1552 dives. Locations have disappeared from recent to very old dives (e.g. 1994 to 2026). Is there any way to recover this data?

Subsurface Version

6.0.5404

Platform(s)

Windows

Platform Version

Windows 11

Divecomputer Model

No response

Steps to Reproduce

1. Open Subsurface
2. Look for dives with empty Location

Logs

subsurface_out.log
INFO: validateGL(): created OpenGLContext.
INFO: validateGL(): obtained QOpenGLFunctions.
INFO: validateGL(): detected OpenGL version 4.6.
INFO: can't find Subsurface localization for locale en-AU
QObject::connect(QQuickWindow, QDeclarativeGeoMap_QML_6): invalid nullptr parameter
INFO: DivePixmaps DPR: 1.000000 metrics: 24 16 sz_bigger: 40
INFO: returning cloud URL https://ssrf-cloud-eu.subsurface-divelog.org/git/ronhenry@netspeed.com.au[ronhenry@netspeed.com.au]
INFO: loading dive data from: https://ssrf-cloud-eu.subsurface-divelog.org/git/ronhenry@netspeed.com.au[ronhenry@netspeed.com.au]
Cloud storage: checking connection to cloud server https://ssrf-cloud-eu.subsurface-divelog.org/git/ronhenry@netspeed.com.au
INFO: Checking cloud connection...
INFO: IP used for cloud server access 219.90.190.120
INFO: git storage: Waiting for cloud connection (1 second(s) passed)
Cloud storage: successfully checked connection to cloud server
INFO: git storage: Synchronising data file
INFO: git storage: update local repo

INFO: git storage: sync with remote https://ssrf-cloud-eu.subsurface-divelog.org/git/ronhenry@netspeed.com.au[ronhenry@netspeed.com.au]

INFO: git storage: Sync with cloud storage
INFO: git storage: delete proxy setting

Cloud storage: checking connection to cloud server https://ssrf-cloud-eu.subsurface-divelog.org/git/ronhenry@netspeed.com.au
INFO: Checking cloud connection...
INFO: git storage: Waiting for cloud connection (1 second(s) passed)
INFO: git storage: Waiting for cloud connection (2 second(s) passed)
INFO: git storage: Waiting for cloud connection (3 second(s) passed)
INFO: git storage: Waiting for cloud connection (4 second(s) passed)
INFO: connection test to cloud server https://ssrf-cloud-eu.subsurface-divelog.org/ failed 302 Error transferring https://ssrf-cloud-eu.subsurface-divelog.org//make-latte?number-of-shots=3 - server replied: I'M A TEAPOT 418 Linus does not like non-fat milk
INFO: failed to connect to https://ssrf-cloud-eu.subsurface-divelog.org/ next server to try: https://ssrf-cloud-u2.subsurface-divelog.org/
INFO: git storage: Trying different cloud server...
Cloud storage: successfully checked connection to cloud server
INFO: updating remote to: https://ssrf-cloud-u2.subsurface-divelog.org/git/ronhenry@netspeed.com.au
INFO: git storage: fetch remote https://ssrf-cloud-eu.subsurface-divelog.org/git/ronhenry@netspeed.com.au

INFO: git storage: Successful cloud connection, fetch remote
INFO: git storage: certificate callback for host ssrf-cloud-eu.subsurface-divelog.org with validity 1

INFO: git storage: certificate callback for host ssrf-cloud-eu.subsurface-divelog.org with validity 1

INFO: git storage: check remote status

INFO: git storage: try to update

INFO: git storage: Done syncing with cloud storage
INFO: git storage: Load dives from local cache
INFO: git storage: Successfully opened dive data
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
can't find a spot in the dataModel
INFO: Profile calculation for dive 1552 took 8 ms -- calculated ceiling preference is 1
INFO: Profile calculation for dive 1552 took 30 ms -- calculated ceiling preference is 1
INFO: returning cloud URL https://ssrf-cloud-u2.subsurface-divelog.org/git/ronhenry@netspeed.com.au[ronhenry@netspeed.com.au]
INFO: Profile calculation for dive 1451 took 39 ms -- calculated ceiling preference is 1
INFO: Profile calculation for dive 1451 took 28 ms -- calculated ceiling preference is 1
INFO: Profile calculation for dive 113 took 69 ms -- calculated ceiling preference is 1
INFO: Profile calculation for dive 729 took 30 ms -- calculated ceiling preference is 1
INFO: Profile calculation for dive 1065 took 32 ms -- calculated ceiling preference is 1
INFO: Profile calculation for dive 1190 too

subsurface_err.log (Size 0)

Mentions

No response

[dirkhh]

Anything that ever was in cloud storage can be recovered (with some effort on my part).
Let's make sure we first understand how this happened so we don't end up having to repeat this...

[ronhenry10]

Possibly a Subsurface-mobile version 3.4.7(5.0.9.35) © 2011-2022 problem?
History.
I opened Subsurface on a Windows 11 laptop to check on a dive that I had done a couple of years ago. I was looking up the name of a buddy. As I was looking at that time period, I noticed that some dives had locations missing. I sorted dives on location and noticed that 62 (actually 63 when I double check) dives had locations missing. Previously, I had made quite an effort to ensure all dives had locations, so I was surprised at how many dives had missing locations. In particular, there were recent dives that I could remember, and I am certain that the locations were recorded.
What changed?
The last 8 dives (all dives in 2026) were added via the Android version of Subsurface-mobile from a Suunto D5 dive computer using the Suunto app on my Samsung S21 mobile. Previously, I had not used the Android version of Subsurface-mobile to add dives as I have been using Atomic Cobalt (both 1 & 2) dive computers for many years. As you would know, Atomic Cobalt computers only have drivers for Windows. When yet another Atomic Cobalt 2 dive computer became unusable due to a button malfunction (a button reed switch died – very common – I have 4 Cobalts to be fixed to send Ronald Russel, the designing engineer), I decided to get a Suunto D5 which seemed to be more reliable. While they work, the Atomic Cobalt 2 is a beautiful dive computer, but I need something that is reliable!
The Android version of Subsurface-mobile I used is rather old: 3.4.7(5.0.9.35) © 2011-2022. Unfortunately, as I did not use it, and it all seemed rather complicated, I did not bother to keep Subsurface-mobile up to date, so it may be a version problem.
I am currently reading https://subsurface-divelog.org/subsurface-mobile-user-manual/ with a view to updating Subsurface-mobile and keeping it up to date.

[mikeller]

Possibly a Subsurface-mobile version 3.4.7(5.0.9.35) © 2011-2022 problem?

Yes, this sounds likely. 3.4.7 is a very old version. Newer versions are available from https://subsurface-divelog.org/current-release/, you should update to a current version before a restore is attempted.

Unfortunately Google's ever changing policies are preventing from us from publishing updated versions to the Google Play Store, so the latest version in there is completely outdated and contains bugs that have been fixed in newer versions.

[ronhenry10]

OK, so I have deleted the old Google Play Store Subsurface-mobile 3.4.7, ignored unsafe warnings from Android and installed Subsurface-mobile 6.0.5504, installed Obtainium, followed this link and Obtainium seems to know about Subsurface-mobile. I've downloaded my dive log into Subsurface-mobile, edited a dive log, and manually updated it to the cloud (auto update is on as well), updated Windows Subsurface to 6.0.5504 and confirmed that my Windows Subsurface can see the updates. How should I proceed to recover the dive locations?

[dirkhh]

well, that's something that I'll need to do for you most likely.
The best way to handle this would be

• send me email FROM the email address that you use for Cloud Storage (dirk@hohndel.org)
• in that email give me explicit permission to access your cloud storage
• tell me which dive numbers are missing their dive site
• and ideally around what date they got lost
  with that I should be able to either fix it, or know what other things to ask you :)