Runs on my environment, but does not on others....

[RKW000]

Sorry for asking this kind of really crappy things here...

I am totally stack on developing a Clockface. The situation is that my Clockface runs on my testing environments, however it does NOT runs on others environments including reviewer at Fitbit.... So, unfortunately I have no way to fix the issues. The environments where the Clockface is tested is following:

- iOS: 11.4, Versa Firm: 32.32.10.15, FItbit App: 2.5.2

- android: 8.1.0, Versa Firm: 32.32.10.15, Fitbit App:2.72.1

- android: 7.1.1, Versa: 32.32.10.15, Fitbit App:2.72.1

- Simulator: 0.6.0 with macOS: 10.13.4

And the reviewer at Fitbit tested the environment bellow:

- Android 7.0, FitbitOS 10.15, Mobile app 2.72.1

- Android 8.0, FitbitOS 10.15, Mobile app 2.72.1

- iOS 11.4, FitbitOS 10.15, Mobile app 2.72.1

( I have no idea what is the meaning of 'FitbitOS 10.15', by the way. Since the latest OS is 2.1.1, I suppose. https://help.fitbit.com/articles/en_US/Help_article/2302 )

The URL for the Clockface resources are here:

[Clockface] https://gam.fitbit.com/gallery/clock/7fddd4e5-fe97-40ae-9c06-f9dbbbc3498f

[Source] https://github.com/ryoyakawai/secondarytimezone2

[FlorinI]

FWIW, your watchface worked fine for me, on watch and on simulator.

- Android 8.0.0, versa 32.32.10.15, app 2.73

- Simulator: 0.6.0 with Windows 10

[RKW000]

Thank you very much for you help!
It is great imformation since hobby developer is not able to have various kinds of developing environments.

So far, I found the place in my side where might causing this situation. The things is that the data coming from settings must be handled as JSON at companion, whereas my code was not handled. So I fixed those and submit code to review. I am not sure, this is the issue. But I will see 🙂

By the way, this spec is said in sample code of tutorial page in Settings in Action at Application Settings whereas Settings API in Reference is saying nothing about it.

(This thread is about to solve almost same problem)

And weird things is where there exists both, one is the situation of 'the device can be run the app' and the other is 'the app can NOT be run'm and these are happening on exact same device.

So I am suspecting that platform might have some bugs in both/either Stuidio and/or OS.

Anyway, thank you very much for your help!! I appreciate your kindness!!

[RKW000 · Accepted solution]

Wow, great!!

Passed review process!!

I suspect the problem was in data handling on companion. All of the data must be handled as JSON.