New post
1

Multiple Database And Object Recognition Bugs In SkySafari 7 & 8 Pro

Hello SkySafari Support Team,

I am a long-time user of your app, and I have recently discovered a whole set of bugs related to the object databases in SkySafari 7 Pro and SkySafari 8 Pro.

Below is a detailed breakdown of three specific issues I encountered, along with reproduction steps, object lists, and expected results. I have also attached ZIP archives containing screenshots, screen recordings, and sample log/list files to help your development team reproduce and fix these problems.

Here are the details:

 Problem 1: Broken link between objects and historical observing sessions (objects shown as "unrecognized")

 Description:
I have a large number of historical observation logs (observing sessions) originally created in SkySafari 6 Pro. After migrating to SkySafari 7 Pro and SkySafari 8 Pro, certain objects within these older sessions are now displayed as "unrecognized".

 Symptoms:

  • When tapping on an unrecognized object within a session, the app displays an error message: "The object cannot be found."
  • However, if I manually search for the exact same object using the app's standard Search feature, SkySafari finds it without any issues.
  • If I search for the object, open its info card, and tap "Show Observations", the app shows zero logs. In reality, there should be numerous historical observations linked to it.

 Actual Result:
The connection/link between historical observing sessions (observations) and specific objects in the database has been lost.

 Expected Result:
Legacy observations imported from older versions should correctly link to the current database objects, and tapping "Show Observations" should display all historical records.

 Attachments:
I have attached a ZIP archive containing:

  • Screenshots highlighting the affected objects and error messages.
  • Sample log files containing the problematic objects.
  • A screen recording demonstrating the entire issue in real-time.

Link to ZIP Archive:
 
https://mega.nz/file/9R1EBQYY#olsQf8k6tDnGmWSiWKFgB9vVa3UnOqxTzu4HJ5m5N5Y

 

Problem 2: Objects in Observing Lists shown as "unrecognized" and map to completely wrong objects

 Description:
In SkySafari 7 Pro and SkySafari 8 Pro, numerous objects within imported observing lists (.skylist) are displayed as "unrecognized". Furthermore, tapping on these objects opens the information and properties card for a completely different astronomical object.

 Steps to Reproduce / Example:

  1. Open the attached observing list: Herschel2500-v08.skylist.
  2. Tap on the very first object in the list, which is NGC 7234.
  3. Instead of NGC 7234, the app opens the object info page for NGC 5966.

 Actual Result:
The object is marked as "unrecognized," and its database entry incorrectly points to an entirely different object. This issue affects a huge number of entries across various observing lists.

 Expected Result:
The app should correctly recognize the object from the .skylist file, display its correct properties (e.g., NGC 7234 should open NGC 7234), and preserve the integrity of the observing list database.

 Attachments:
I have attached a ZIP archive containing:

  • The original observing list file (Herschel2500-v08.skylist) featuring the problematic entries.
  • Screenshots showing the incorrect object mapping.
  • A screen recording demonstrating the bug in action.

Link to ZIP Archive:
https://mega.nz/file/9R1EBQYY#olsQf8k6tDnGmWSiWKFgB9vVa3UnOqxTzu4HJ5m5N5Y

 

Problem 3: Missing objects in SS7 and SS8 databases (Regression)

 Description:
There is a database regression issue where multiple astronomical objects that were present and searchable in SkySafari 6 Pro have gone missing in newer versions.

The situation is bad in SkySafari 7 Pro, but it gets significantly worse in SkySafari 8 Pro, where even more objects from the same catalog have disappeared.

 Objects missing in SkySafari 7 Pro:

  • NGC 6144
  • PGC 4713561
  • PGC 4713565
  • PGC 4713558
  • PGC 5056923

Objects missing in SkySafari 8 Pro (even larger list):

  • NGC 6144
  • PGC 4689222
  • PGC 4689223
  • PGC 4713552
  • PGC 4713553
  • PGC 4713557
  • PGC 4713558
  • PGC 4713559
  • PGC 4713561
  • PGC 4713562
  • PGC 4713563
  • PGC 4713564
  • PGC 4713565
  • PGC 5056919
  • PGC 5056921
  • PGC 5056923

Note: In SkySafari 8 Pro, the app fails to return any results when searching for these specific identifiers, despite them being fully available in older generation software (SS6 Pro).

 Expected Result:
All objects available in legacy databases (SS6 Pro) should be preserved or properly mapped in the newer versions (SS7 Pro and SS8 Pro) without catalog data loss.

Link to ZIP Archive:
https://mega.nz/file/9R1EBQYY#olsQf8k6tDnGmWSiWKFgB9vVa3UnOqxTzu4HJ5m5N5Y

 

10 comments

  • Avatar
    Keiron Smith Official comment

    DevOps reference: SKY-223

  • 0
    Avatar
    Keiron Smith

    Thank you, Developers will review your report and resolve the issues.

  • 0
    Avatar
    Евгений Богатырев
    The problematic objects listed in my initial bug report are just a few examples; there are many more.
    Today, I discovered another issue in SkySafari 8 Pro. Some objects from the GAIA catalog that were present in SS6 and SS7 are missing in SS8. I will provide more details shortly.

    I would also like to note that all these issues are critical. Because of them, I am forced to stop using SkySafari 7 Pro and SkySafari 8 Pro, which I already purchased, and go back to the older SkySafari 6 Pro, where everything works correctly.
  • 0
    Avatar
    Keiron Smith

    Thanks for all the screenshots, recordings and logs.  Developers are reviewing your detailed troubleshooting reports.

  • 0
    Avatar
    Евгений Богатырев

    Problem #4: Missing GAIA catalog stars in SkySafari 8 Pro

     I have noticed that a large number of stars from the GAIA catalog are missing in SkySafari 8 Pro, even though they are present in both SkySafari 6 Pro and SkySafari 7 Pro.

    Below is a list of missing stars that I managed to find just by checking my old observation logs. I assume the actual list of missing objects is much larger.

     Examples of missing GAIA stars:

    GAIA 3678422472916760704
    GAIA 6849625049234177920
    GAIA 2090486515707275008
    GAIA 2090486309548837120
    GAIA 3960606673282514560
    GAIA 3824445317962285056
    GAIA 3824256717358313216
    GAIA 2090483698208800512

  • 0
    Avatar
    Евгений Богатырев
    Problem #5: Frequent ANR (Application Not Responding) crashes on Samsung Galaxy A06
    Description:
    I am experiencing frequent "Application Not Responding" (ANR) system dialogs while using SkySafari 8 Pro. The app freezes periodically, prompting me to either close it or wait.
    This happens on a Samsung Galaxy A06 device (MediaTek Helio G85 chipset, 4GB RAM).
    What I have already tried to fix the issue:
    • Performed a clean installation of the app from the Google Play Store (all previous versions were completely uninstalled beforehand).
    • Disabled the realistic horizon panorama (switched to transparent/line).
    • Turned off time flow animations and set the time step to 1 second.
    • Disabled LiveSky auto-sync, notifications, and all online/social features to minimize background network requests.
    • Adjusted Android system settings (enabled RAM Plus and set battery usage to "Unrestricted" for SkySafari).
    Despite all these optimizations, the ANR freezes still occur. It seems like the app's database queries or rendering engine heavily overload the CPU/RAM on this specific hardware configuration.
    Could you please optimize the background thread management for budget devices to prevent these ANR freezes?

    SkySafari 6 and 7 Pro work fine on this device.
  • 0
    Avatar
    Keiron Smith

    Thank you - developers have received your additional reports!

  • 0
    Avatar
    Bryan Hamilton

    I have seen these issues as well and am about to report an additional, yet similar, issue which is  even worse since objects seem to actually get removed from the database.  I am following this and will not be ready to upgrade to SkySafari 8 until these issues have been resolved, or have been markedly improved, over SkySafari 7.

  • 0
    Avatar
    Keiron Smith

    Hi Bryan, 

    SS7 will not receive anymore app updates.  Any fixes will arrive in SS8.

    Please consider upgrading to SS8 to verify and be able to provide better feedback regarding this issue.

    Thanks!

  • 0
    Avatar
    Bryan Hamilton

    This memo indicates that these issues get worse in SkySafari 8 so I am not going to just upgrade and pay for things to get worse with this problem, even if other improvements would normally make things worth it.  This is a serious reliability issue.

    I have watched videos on SS8 and am still not aware of any fixes or new features that give me a reason to upgrade anyway, mostly because all My Activities in the forums which are closed say Solved, even when I know some of them are not actually fixed or implemented. I did ask AI whether version 8 now allows people to modify previous observations in seconds, which would normally be worth an upgrade, and it told me that was changed but you guys did not confirm that's the case in my previous feature request when you closed it. Also, if my post about SkySafari kicking me out with my BT keyboard was fixed that would be a reason as well but it just has a status of Solved with no comments.

    You guys have solved issues in the past with version 6 and then informed me that they were resolved with a comment but I have seen no answers that anything I have reported for version 7 was resolved in version 8.

    Don't you guys have a way of letting people know the final status of the issue they reported or are following?  I can kind of understand it, if I reported it before version 8, but I requested the feature for modifing using seconds just a few weeks ago.  I would expect that if you aren't going to comment you would have other statuses like "Sent to Development", "High Prority", "Update coming","Known Issue", "Will not be addressed", "Implemented", "Resolved in Version 8" etc but saying Solved for everything leaves me in the dark with no information on whether I want to upgrade or not.

Please sign in to leave a comment.