SC1 watch face worked fine for years - now won't load, tried everything besides full factory reset

Hi;

I have been using the SC1 watchface for years on my Fenix 5 and 7X no issues.

2/3 days ago it randomly stopped, no idea why.  Did not update my firmware, did not change any settings, nothing, literally watching TV and the watch has a default one on.

I've tried reboots, uninstalling, rebooting, reinstalling, connecting to the PC, nothing works.

Any ideas how a perfectly working watchface just stops?

ta

  • Hi Phil, I've already tried this, and i'm not sure how this will resolve it.  A perfectly working watchface stops working.  There was no firmware updates to the Fenix to suggest the watchface was incompatible.  In my opinion there is another issue at play here. 

  • In my opinion there is another issue at play here. 

    That's exactly why you should contact the developer. He would either probably already know about the problem, or can debug it, which is what nobody else can do without having the access to the source code.

  • ... you can also try a few other CIQ watchfaces, just to see whether it is a general problem with all of them on your watch, or whether it is isolated to the concerned WF.

  • I don't think you're alone, as a Fenix 7X user reported something similar in a review from September 18, assuming you're talking about this watchface:

    apps.garmin.com/.../7fd7fe08-7b02-43f5-9b6b-3d574bfe82b4

    09/18/2024 | Version 1.3.0
    Amazing, I love SC1, I have installed it on my Fenix 5X Pro Plus, and now on my Fenix 7x Pro Sapphire Solar, so I use it for few years. Today, Garmin has sent a new update, and SC1 does not work anymore. Could you update it please ? Thank you.

    Also, I just installed SC1 as a test on my FR955 [running recent beta firmware]. At first it worked fine, but eventually it started crashing consistently. There is an error log on the watch, but it doesn't provide any useful information other than the crash is due to an unhandled exception, and it's happening on the same line of code every single time.

  • I agree that the dev is the person who is best equipped to troubleshoot and solve this problem. Indeed, they should be receiving automated crash reports for me, you, the person who wrote the above review, and anyone else who's currently experiencing crashes. Their crash reports should also have more information than what I posted above. In particular, they should be able to narrow down the exact line of source code where the crash is happening. [Ofc we can't do that since we have neither the source code, nor the built version of the app that was submitted to the store.]

    However, since the watchface hasn't been updated in almost three years, it's possible they are no longer actively developing the watchface.

    [I know that the general sentiment from both Garmin Support and the forums is that CIQ apps need to be constantly updated otherwise they'll stop working due firmware updates, but this really isn't true in general. It is possible that firmware updates can causes problems in apps that used to work fine, due to a bug or changed behavior in the firmware itself, especially if the app had a dormant bug that was never triggered, but this is generally the exception to the rule.]

    If I'm able to figure out why the app is crashing and/or a workaround to prevent the crash [both fairly unlikely], I'll post again.

    I can say that it doesn't seem to make a difference whether:

    - bluetooth is enabled or not (or whether Connect is open on the bluetooth-connected phone)

    - whether the default weather api key is set or not [indeed, the weather appears on the screen briefly, along with the rest of the watchface, before it crashes]

  • Here's a screenshot of the crash log [even though it's pretty useless to us], since the forum won't let me post it as text:

    https://postimg.cc/WqTfXXC1

  • Can also confirm that I installed SC1 on an old watch (FR935) and it does not crash.

  • Any ideas how a perfectly working watchface just stops?

    Looks like something has changed in openweathermap, the service SC1 uses for weather, causing SC1 to receive an error when it tries to retrieve weather data.

    It looks like SC1 is crashing after it tries to make a call to the openweathermap API. I saw an announcement from April 2024 which stated the API 2.5 was being shut down in June, and that everyone has to migrate to API 3.0. It seems that API 3.0 is the same as API 2.5, except everyone who has a key needs to switch it over to API 3.0, which apparently requires a subscription (which means that you have enter your credit card details, although there is a free tier which requires no payment unless you exceed certain usage limits)

    openweathermap.org/.../one-call-3

    The following link is not directly related to the app. It’s for a separate product that uses OWM integration, but I’m posting it bc it describes the migration process from API 2.5 to API 3.0: www.home-assistant.io/.../

    Having said that:

    - On my FR935, SC1 just displays “GPS OK” and “No Data”, in the field which is supposed to display weather info. (I’m using the default key there)

    - On my FR955, when I scroll to SC1, the watchface is briefly displayed with current weather info in the weather field, then it immediately crashes. As per the error log I posted, the watchface is crashing with an unhandled exception, which probably indicates that OWM is returning some error which is manifests itself differently on FR935 vs FR955 / Fenix 7, for whatever reason.

    On my FR955, I can use the following workaround to get the watchface to work:

    - After it crashes, I select another watchface and wait a while (maybe 20-30 minutes)

    - I disable bluetooth on the watch (so it’s not longer connected to the Connect app on my phone, and therefore can’t make any network calls)

    - As long as bluetooth is disabled, the watchface doesn’t crash (but ofc the weather field stays empty)

    Clearly this isn’t an acceptable workaround for the vast majority of users.

    I can think of one workaround that I’m not willing to try myself (EDIT: this won't work without changes from developer):

    - Subscribe to OWM. This means that you have to enter your credit card data, but you won’t be charged if you select the free tier (which should be more than enough for the watchface): openweathermap.org/price

    - Once you subscribe to OWM, you will either get a new API key that works with API 3.0, or your existing API key will be converted to work with API 3.0

    - Use this key in the SC1 settings. Since apparently nothing has changed about the API from 2.5 to 3.0 except for the subscription aspect, the watchface should start to work again

    EDIT: actually the API endpoint URLs changed, so the dev def needs to make changes