Properties are deprecated, but documentation doesn't say what to use instead

9938694 4 months ago

setProperty and getProperty are deprecated, but the documentation doesn't say what else I should be using instead.

I want to pass some data from a background method (AppBase.onBackgroundData) to a background service (ServiceDelegate).

What should I be using instead of a property?

Top Replies

jim_m_58 4 months ago in reply to 9938694 +1

Try using "Application.Storage"

All Replies

0 jim_m_58 4 months ago

Depending on the device you are using, getProperty/setProbery are what you use. (old devices),

But starting with devices with 2.4.0 or above of CIQ, you use getValue/setValue with Application.Properties or Application.Storage

0 FlowState 4 months ago

For further background:

https://developer.garmin.com/connect-iq/core-topics/persisting-data/

https://forums.garmin.com/developer/connect-iq/i/bug-reports/doc-sim-behavior-for-properties-getvalue-key-setvalue-key-is-inconsistent-regarding-whether-key-needs-to-be-present-in-app-properties-or-settings

0 9938694 4 months ago in reply to jim_m_58

It looks like I can't use `Storage.getValue` in `ServiceDelegate.onTemporalEvent`, right? I'm getting this error: `Cannot find symbol ':Storage' on type 'self'.`.

0 FlowState 4 months ago in reply to 9938694

What device are you testing with? Storage is only available to background processes starting with CIQ 3.2.0, as per https://developer.garmin.com/connect-iq/core-topics/persisting-data/

EDIT: jim_m_58’s comment below is likely the answer. If it were failing due to lack of support for storage in background processes in CIQ < 3.2.0, an exception would be thrown, as opposed to the error you’re seeing. Additionally, his answer is consistent with the error message you’re getting, as well as the details of your post (Storage isn’t a top-level module, it’s a module under Application, so your error message makes sense if your code indeed calls Storage.getValue() from the service delegate.)

0 jim_m_58 4 months ago in reply to 9938694

Try using "Application.Storage"

0 flocsy🤠 4 months ago in reply to 9938694

When you have an error related to your code it usually helps to include your code.