Acknowledged
over 1 year ago

On-device setting accept at most 31 characters

I'm developing on-device setting. Now I use on-device setting to input the weather key which is 32-bit string. When I input it and can only input 31 bits. The 32th bit is trimmed.

When I input the characters on watch, it popup a input dialog box on the "GARMIN CONNECT" app on my phone, and I can input at most 32-bit string. But after save, the last one is trimmbed.

So I can only input at most 31-bit string on on-device setting. I thinks it's a bug. Almost weather key is 32-bit string after all.

yp
  • over 1 year ago in reply to yp

    Thanks for the clarification—we'll take a look.

  • over 1 year ago

    my mistake... I miss-read on device settings...

  • over 1 year ago in reply to Shent-Aurkhan (SHN)

    Thanks a lot for comments. It works for OWM API key in setting. What I mean is that it doesn't work for setting on-device. In other words, I'd like to input the OWM API key on watch without phone. I can input at most 31 characters. That should be a bug.

  • over 1 year ago

    I don't think it is a common issue, all my apps use OpenWeatherMap API key which has 32 characters.

    I had a Fenix7 and now a Fenix7pro and I can put my OWM API key.

    and I think since I've published all my apps, 4 years ago, I would have got many report if it does not work.

    I think the issue is on your code side

  • over 1 year ago

    Hi Gavriel and Brandon:

    Thanks a lot for you prompt response. It's a little confusing in my expression by using bits. Indeed I mean I can only input at most 31 characters.

    I run the sample code "Keyboard" included in SDK 6.3.0 without any change. I tested fr935 and fenix7 and both have the issues. I didn't test others but I'm sure it's a common issue. Please run it by youself and input characters from the screen. You'll find you can input at most 31 characters.

    Thanks!