Back on March 29, 2020, I logged the comet 'ATLAS,C/2019 Y4,C/2019 Y4 (ATLAS)', as designated in SS6 Pro on my Android S10 with Android 10. Now, months later, I was looking back at my observations, and this object now shows that I logged P/2019 X1 (Pruyne), an object I've never heard of that was at magnitude 20 at the time. Thinking I might have somehow logged the wrong object at the time, I went back to my spreadsheet export from LiveSky, exported the day after and saved locally, and it showed the correct object. Since there's no way to manually go in and change an observation within the app to another object, keeping all other details, I know that this must be a bug. While not that concerned on this one specific object, it's crucial that the app doesn't go changing object observations. Maybe given that this is a comet, and comets are probably changing more than anything else in the databases, so thought maybe it could be something to do with that?
22 comments
-
Chris Just found a second instance of this. NGC 4186 I logged this same night, in LiveSky it shows up correctly (as does the comet mentioned above) but in SS6 Pro on my phone, when I click Observe > Observations > My Session Name > NGC 4186 > Show on Chart, it goes to UGC 7436 (not the same object). When I click on NGC 4186 on the map and click Selection > Show Observations it says 0 Observations. Lastly, when I click on UGC 7436 and click Selection > Show Observations, it literally shows NGC 4186 and NGC 4192B, which is another name for NGC 4186 and another observation I had of it years ago.
Something is going on here with these objects, but according to LiveSky, maybe it's just programming in SS and not the database being wrong. -
Keiron Smith Chris,
Would you say you experiencing the same issue as reported here?
Thanks!
-
Chris Sounds somewhat similar, yes, except I don't know if it was ALL of my observations as he references. Any idea when this can be fixed? It's a bit concerning given that SS is my primary log of observations.
-
Keiron Smith Piotr states the issue occurs after syncing with a second device. Can that be true in your case too?
Ros is working on LiveSky now.
Thanks!
-
Chris I'm syncing to two devices, yes.
-
John E. I logged the comet 'ATLAS,C/2019 Y4,C/2019 Y4 (ATLAS)', as designated...Now, months later, I was looking back at my observations, shows that I logged P/2019 X1 (Pruyne)
I'm having the same problem.
-
Keiron Smith Hi John,
We are working on this issue.
Thanks for your report!
-
John E. Any status update on this problem. I'm still encountering the same trouble when logging observations of Neowise.
-
Chris Still encountering this as well. Not sure if anyone is even reading our posts?
-
Keiron Smith Hi Chris,
Yes, posts are read, issues are documented. The next update for SkySafari will be SS7.
Thanks for your patience.
-
Ros Hartigan Chris can you tell me what devices you are using? (Android, iPhone, OS versions)
-
Chris Hi
I'm using Android on both devices, Android 10 on my galaxy S10, which is where I see most data quality issues, then Android 7 on my tablet Galaxy Tab S2) where I input the data at the scope.
-
Keiron Smith Chris,
Pro and Plus betas now available in Google Play have a fix for this issue.
Please test.
Thanks!
-
Chris Hey Keiron--
When I launch SS6 Pro and go to Observe > Observations and click on a Session, I now see dates only with no object names for any of my observations. When I click on one, I get the following message:
'This object cannot be found in the SkySafari Pro database.
It may have come from a different version of this app or from an entirely different application.'I see this on all observations in all sessions, or even observations not tied to a session. Is anyone else having this problem?
SS 6.8.1.2 on my Galaxy S10 with Android 11 -
Chris 
-
Keiron Smith Thanks, Chris. Looking into it.
-
John E. I do not see any change, my observation for July 25, 2020 still says "C/2019 Y5 (Panstarrs)" when it should say "Neowise". My observation for July 19, 2020 still says "C/2019 Y4-D (Atlas)" when it should also be "Neowise".
SS 6+ Ver. 6.8.0.6; Moto G; Android 6.0.1
-
Keiron Smith Another update will be released in a couple of hours.
Thanks, John!
-
Chris Just updated. The issue from earlier this morning is now gone, and it seems perhaps the issue with the comet I was having when I started this thread may be fixed. Unfortunately, the 2nd comment in this thread, pasted below, is still acting incorrectly as it did previously.
--------------------------------
Just found a second instance of this. NGC 4186 I logged this same night, in LiveSky it shows up correctly (as does the comet mentioned above) but in SS6 Pro on my phone, when I click Observe > Observations > My Session Name > NGC 4186 > Show on Chart, it goes to UGC 7436 (not the same object). When I click on NGC 4186 on the map and click Selection > Show Observations it says 0 Observations. Lastly, when I click on UGC 7436 and click Selection > Show Observations, it literally shows NGC 4186 and NGC 4192B, which is another name for NGC 4186 and another observation I had of it years ago.
Something is going on here with these objects, but according to LiveSky, maybe it's just programming in SS and not the database being wrong. -
John E. I just downloaded the new beta version. Now the comet designations are corrected. Both observations now correctly say it's comet "Neowise". Thanks!
-
Ros Hartigan Chris, we are investigating this second issue - thanks for the feedback.
-
Chris This appears to be fixed in today's beta! Thanks!