Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Getting error for system assests while Building an Accelerometer Fetcher for Fitbit Versa 2

ANSWERED

Hello Developers,
I have have clone the repo from @Gondwana  fitbit-accel-fetcher and it works fine on atlas and vulcan. I have downgraded the SDK and made some changes for the build targets to mira and app build fine and gets installed in the simulator too. 

Problem happens when I try to install it on the simulator and run it. The CLI prompts an error saying 

Spoiler
 Invalid path '/mnt/sysassets/widgets/text_button.gui'

App: Error 22 Invalid value '' (mnt/sysassets/widgets/text_button.gui:1,1)
Could not find symbol '#text-button' in recBtn (resources/index.gui:5,1)
Undefined attribute 'href' in recBtn (resources/index.gui:5,1)
Could not find symbol '#text-button' in xferBtn (resources/index.gui:6,1)
Undefined attribute 'href' in xferBtn (resources/index.gui:6,1)
APP: App Started
No permission to access the user activity API (app/index.js:2,138)
Unhandled exception: TypeError: Cannot set property 'text' of null ? at app/index.js:50,1
 Companion: The 'wake-interval' API is not yet supported in the Fitbit OS Simulator. Behavior may not match the documentation or real devices.

I have installed the android app on the phone and trying to fine tune your project into versa 2. I am running SDK 4.3.0 I have updated the package.json and Node modules by commanding npm i after SDK installation on the app path but nothing changes the error. It would be great help if any one could help me with this mira development. 

Thank you so much in advance. 

 

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Please see this post. Among other things, the button components changed between SDK4 and SDK5. Refer to the SDK4 documentation in the linked post. You'll need to rewrite the button bits to use the SDK4-style buttons (or make other alternative arrangements).

It might be possible to do that using the sim, but that app won't work fully in the sim because the sim can't communicate with the server code on the phone, and it doesn't simulate an accelerometer.

Peter McLennan
Gondwana Software

View best answer in original post

Best Answer
3 REPLIES 3

Please see this post. Among other things, the button components changed between SDK4 and SDK5. Refer to the SDK4 documentation in the linked post. You'll need to rewrite the button bits to use the SDK4-style buttons (or make other alternative arrangements).

It might be possible to do that using the sim, but that app won't work fully in the sim because the sim can't communicate with the server code on the phone, and it doesn't simulate an accelerometer.

Peter McLennan
Gondwana Software
Best Answer

@Gondwana Thank you so much for your reply sir. Is there any guide to rewrite the button bits?

Or it's better to move to another fitbit (vulcan/atlas) for development?

Best Answer

I don't know of any guide. Learn by implementing a button using an example from the SDK4 documentation.

Newer watches won't provide much advantage for accelerometer data collection.

Peter McLennan
Gondwana Software
Best Answer