"Permission for module '0080000f' required". What's this?

Recently, the update 19.20 for fenix6series inovled an issue for the cadence display. Look this thread for more information. https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/273829/running-cadence-shown-as-half-of-steps-min-after-19-20-update

After seeing fbbbrown's answer, I determined to use Sensor.getInfo().cadence as a temporary workaround. But it doesn't work. I am sure I edited the permission in the manifest.xml.

I received a log file as below.

---
Error: Permission Required
Details: "Permission for module '0080000f' required"
Time: 2021-11-13T02:59:43Z
Firmware-Version: '19.20'
Language-Code: chs
ConnectIQ-Version: 4.0.6
Store-Version: 5
Filename: BBCN0631
Appname: 
Stack:
- pc: 0x10001b5c
- pc: 0x100002fa
- pc: 0x10002365
- pc: 0x100007bf
---

The pc counter points the line compute(info), it seems not the real culprit. Any idea to solve this problem

Top Replies

li2niu over 3 years ago in reply to flowstate +1

https://forums.garmin.com/developer/connect-iq/i/bug-reports/sensor-getinfo-doesn-t-throw-any-compilation-exception-when-used-in-a-data-field-app I have reported this bug

All Replies

flowstate over 3 years ago

This is a datafield? Correct me if I'm wrong (anybody), but I don't think datafields are allowed to access the Sensor module outside of background processes.

Does this actually work in the sim? Or on your real device?

li2niu over 3 years ago in reply to flowstate

flowstate said:
This is a datafield

Yes.

flowstate said:
but I don't think datafields are allowed to access the Sensor module outside of background processes.

Oh s**t, I didn't know that before.

flowstate said:
Does this actually work in the sim?

It does work in the simulator but crash on users' real devices.

Finally I adopted your workaround. Thanks~

if ( (value == 14 /* OPTION_CURRENT_CADENCE */) && (info.currentCadence != null) )
{
var version = System.getDeviceSettings().monkeyVersion;
if (version[0] == 3 && version[1] == 2 && version[2] == 6)
{
    return info.currentCadence * 2;
}
return info.currentCadence;
}

flowstate over 3 years ago in reply to li2niu

Np. Seems like it would be a bug if that's allowed in the sim but not a real device. Should probably post a bug report :/ about that, at least to confirm whether I'm right about what I said or not.

li2niu over 3 years ago in reply to flowstate

Np. I will confirm that

li2niu over 3 years ago in reply to flowstate

flowstate said:
I don't think datafields are allowed to access the Sensor module outside of background processes.

Is there any doc for the Sensor module usage ，ie where is allowed to access or not ？

jim_m_58 over 3 years ago in reply to li2niu

From the API Doc for Sensor. You'll see the same thing for a number of things in the Sensor doc in general.

getInfo() as Sensor.Info

Get the current Sensor Sensor.Info.

This is useful for retrieving the current sensor info either on demand or periodically within a Timer.

Note:

Will cause an app crash if called from a data field app

jim_m_58 over 3 years ago in reply to jim_m_58

One of the first cases where I recall this coming up is when you are trying to read temperature in a data field (a tempe with watches or the internal temperature with Edge devices.). You need to have a small background service to access Sensor.Info that returns the temperature.

flowstate over 3 years ago in reply to jim_m_58

It seems strange that it wouldn't also crash in the sim or even throw a compilation error (like in other contexts where a module is accessed when it shouldn't be.) I suppose the compile-time error would be trickier because of the background vs. foreground aspect, but surely the sim could be made to crash at runtime in the same way as the device.

jim_m_58 over 3 years ago in reply to flowstate

Do a bug report.

flowstate over 3 years ago in reply to jim_m_58

jim_m_58 said:
Do a bug report.

Thanks, I suggested that a few comments above. This bug doesn't affect me and I file lots of bug reports about stuff already.