Complete

Watch faces downloaded show a blank screen when starting to scroll up or down

When I start to scroll up or down from the watch face. To access the glance widgets. If I have a pre installed watch face selected. It will show the face image as I start scrolling, but with any installed faces (I've tried a few different ones from different developers including Garmin) when I start scrolling the watch face image disappears and shows a blank screen instead, making the whole scrolling feel very unnatural. 

Not a huge deal. Just cosmetic I guess. But I wish it would be fixed

  • Here's that forum thread - it's a "fun" discussion where some posters go through all the stages of bug denial in real time:

    - I don't see this

    - Ok I see this but it doesn't seem to be a problem?

    - Ok you've explained the problem but I think this is an extreme edge case that nobody would ever notice. Actually, I still refuse to acknowledge any problem exists at all

    forums.garmin.com/.../1817369

  •  Just to explain a little more, this area is specifically for reporting Connect IQ-related bugs (typically that developers encounter). Even if you're not a developer, you're welcome to report bugs here, but we ask for certain information to be included (see https://forums.garmin.com/developer/connect-iq/w/wiki/5/bug-reports-faq#new-report).

    If the problem you're seeing is related to a non-Garmin developed app, that may be a bug the app developer needs to address. The bug you've reported here sounds like a product-specific issue, which can sometimes be the case, and has to be fixed in product software since things of this nature may not be specifically related to Connect IQ.

    I don't mean to discourage you at all—just want to set the right expectation about this are of the forums. Thanks!

  • Yeah I hope it's fixed too. It's inconsistent with native watchfaces and it makes for a jarring user experience.

  • My apologies, I've never even seen this forum before, I was just complaining to the developer of the face I'm using, and he recommended I add it here. So sorry, I didn't know it was already posted. But hopefully the more it's posted the more visible the issue will be hopefully the sooner it will be fixed

  • It's a known issue. Just a few days ago there was a thread about it in the forum