Gradient rects doesn't work with last SDK

[gaperton]

@JonFitbit @LiamFitbit 

My inbox is full of the customers request asking me to fix the watchface with hands disappeared. The problem can be observed with both Ionic and Versa 2.

Hours, minutes, and seconds hands are drawn with a gradient rect. Watchface works perfectly on a simulator, but app on a real device has all gradient rects missing. Please, confirm that there's such a problem with a device firmware, or provide me with an example of gradient rects showing on a real device so I could figure out what I'm doing wrong.

[gaperton]

@JonFitbit @LiamFitbit 

Would you mind to confirm the problem or provide the solution, please?

[LiamFitbit]

Can you provide a test app that shows the issue you're seeing, preferably with screenshots that show the expected vs actual behaviour you'd expect to see? If you're seeing expected behaviour in the sim, you should be able to use that to capture the screenshot for the expected case.

[gaperton]

index.svg

<svg>
  <section x="50%" y="50%" width="100%" height="100%">
    <g id="minutes">
      <gradientRect x="-20" y="-45%-20" width="40" height="40"
        gradient-type="radial"
        gradient-x1="50%" gradient-y1="50%"
        gradient-x2="100%" gradient-y2="100%"
        gradient-color1="#00FF00"
        gradient-color2="black" gradient-opacity2="0"/>
    </g>
  </section>
</svg>

index.js

import document from 'document'


const el = document.getElementById( 'minutes' );

el.groupTransform.rotate.angle = 90;

[gaperton]

Expected result (Versa 2 simulator screenshot)

On real Versa, there's a black screen.

What is happening is that the gradient rect disappears when being rotated on a device. If you comment out this JS line...

el.groupTransform.rotate.angle = 90;

...gradient rect will appear.

[gaperton]

The same thing happens on a real Ionic. I remember seeing several complaints from other devs there in a forum, it's not just me, and I've got like 5 or seven emails from users of my app, I stopped counting.

[gaperton]

@JonFitbit @LiamFitbit 

Was the information provided enough to reproduce the issue? Would you mind to confirm the problem or provide the solution, please?

[gaperton]

@JonFitbit @LiamFitbit 

Was the information provided enough to reproduce the issue? Would you mind to confirm the problem or provide the solution, please?

[gaperton]

@LiamFitbit 

Hi Liam,

I saw you answered some other questions yesterday. Ignorance of this thread seems confusing. Trying to figure out what exactly stops you from writing a few words there. Is there something I could do to help? If you don't know how to respond to problems as I mentioned, it's easy. Fill the issue in your internal issue tracker which we don't have any access to, and write a sentence here like "don't worry, we're able to reproduce the problem, it will be fixed in the next firmware release".

[LiamFitbit]

I've been on holiday for a bit, so I'm slowly catching up on all my emails/threads whilst I've been out.

I've filed a ticket internally for this issue using the information you've provided.

[gaperton]

Thank you very much, that's what I wanted to hear :).

[gaperton]

Hi @LiamFitbit ,

There's still no fix for the issue, so I worked it around with pre-rendered transparent png images.

There's one week passed since I posted my app to review, and the status is still "waiting." Would you mind to ping QA so my fix will be finally published because people keep sending me complaints and I'd like it to stop?

https://gam.fitbit.com/apps/e69c9f39dcc3

[LiamFitbit]

The issue has been fixed internally and will be in the next release. Unfortunately I don't have dates to share as to when that will be.

[gaperton]

It's awesome news, thank you very much for your help!

Would you do me a little favor and ping the QA to publish an update to my watch face, please? I fixed the issue in the watch face because people are disappointed and it hurts the app rating.

[JonFitbit]

I've pushed that fix for you.

[gaperton]

Thanks, Jon!