Fit Recording: Simulator fails with "Permission 'Fit' required" - how to do it right?

In my datafield app (simpledatafield) i'm using a debug label (:test) for a unit test function.

This function, for testing purposes, calls a function in the production code to process test data with it. The production function contains createField calls, to store data in fit files. As specified, this does not work in simulator, because there is no open activity session while codes runs in simulator. Thus, in the test function i create a session. This does not work and fails with a permission error. But permission "FitRecording" is given to the app. If i change it to "Fit" (as stated in the error message) the code does not compile, How can i solve this problem?

Permission 'Fit' required for '$.Toybox.ActivityRecording.createSession'.

Top Replies

FlowState over 2 years ago in reply to CYBERMAN54 +1

CYBERMAN54 said:
I'm just struggling with the unit test function, which does not work in the simulator, while calling createField.

My educated guess is that anything which involves "real" functionality…
FlowState over 2 years ago in reply to CYBERMAN54 +1

CYBERMAN54 said:
actually, what i'm doing here, is unit-testing the WatchUI.compute function.

Got it, my bad.

I think you need to provide test shims (mocks) for createField(), setData() -- and any other…
FlowState over 2 years ago in reply to CYBERMAN54 +1 verified

Hmm, besides the type-checker warnings/errors, my example has a fatal flaw: any function annotated with :test is assumed to be a unit test, so the test driver tries to run createField(), which causes a…

All Replies

0 jim_m_58 over 2 years ago

What is your app type?

If in VSC, if you use "Edit Permissions, do you see something like this?

0 CYBERMAN54 over 2 years ago in reply to jim_m_58

My app needs BLE and Fit, but not positioning. Both are set in the manifest file. App type is simpledatafield.

<iq:permissions>
            <iq:uses-permission id="BluetoothLowEnergy"/>
            <iq:uses-permission id="FitContributor"/>
</iq:permissions>

0 jim_m_58 over 2 years ago in reply to CYBERMAN54

Notice the one I posted has Fit checked. FitContrib is unchecked. It's from the record sample in the SDK. A device app. Is your app a data field? There you don't create a session, as the activity does that.

0 CYBERMAN54 over 2 years ago in reply to jim_m_58

That's funny. I don't see "Fit" in my VSCode. Running newest versions of VSCode and IQ SDK.

0 jim_m_58 over 2 years ago in reply to CYBERMAN54

What type of app? In a data field you do not use creeateSession nor need the fit permission, as the fit file is created/managed by the native app.

0 CYBERMAN54 over 2 years ago in reply to jim_m_58

it's a simpledatafield / WatchUI app.
The datafield does not use createSession and storage in .fit files works.

But if i call the test function from the debug mode, it complains "symbol not found" regarding the first line where i use createField.

Here's the link to the code:

github.com/.../DataManager.mc

0 FlowState over 2 years ago in reply to jim_m_58

OP said it was a data field twice.

Anyway, what's happening here:

- As jim_m_58 said, data fields don't use ActivityRecording.createSession.

- As CYBERMAN54 said, he doesn't see the "Fit" permission. That's because it's inapplicable/unavailable for data fields, due to the previous point.

The "Fit" permission is for recording an activity, and "FitContributor" is for adding data to an activity. Since CIQ data fields are added to a native activity which already has the ability to record an activity, they don't need the "Fit" permission.

The way to record data in CIQ data fields is to use FitContributor. See docs and example here:

[https://developer.garmin.com/connect-iq/api-docs/Toybox/FitContributor.html]

0 CYBERMAN54 over 2 years ago in reply to FlowState

Thanks for the explanations! But, the recording works.

I'm just struggling with the unit test function, which does not work in the simulator, while calling createField.

0 FlowState over 2 years ago in reply to CYBERMAN54

CYBERMAN54 said:
But if i call the test function from the debug mode, it complains "symbol not found" regarding the first line where i use createField.

Hmm, interesting. Given that functions with the :test annotation are meant to be used for *unit* tests, it's not surprising that functionality like createField() would be unavailable in that context.

0 FlowState over 2 years ago in reply to CYBERMAN54

CYBERMAN54 said:
I'm just struggling with the unit test function, which does not work in the simulator, while calling createField.

My educated guess is that anything which involves "real" functionality (whether on-device or simulated) wouldn't be available for unit tests, since the idea is to unit test your functions, and not implement integration/system tests which test the system as a whole.

To do real CI/CD, I think you'd need to be able to automate the sim somehow, which isn't currently possible.