Failed to invoke Symbol Storage.deleteValue()

I'm am executing the following code

// Request access token and refresh token in exchange for authorisation code
    var codeVerifier = Storage.getValue("codeVerifier");
    // Only persisted to length of exchange
    Storage.deleteValue("codeVerifier");

The last action to delete the key from Storage is failing with

Error: System Error
Details: 'Failed invoking <symbol>'
Time: 2023-12-10T15:24:17Z
Part-Number: 006-B4169-00
Firmware-Version: '19.19'
Language-Code: eng
ConnectIQ-Version: 4.2.4

Anyone come across this before. Is it trying to tell me I can't delete the Storage key because I have a local variable that somehow is locking it because the Storage.getValue() in the previous line?

flocsy🤠 over 1 year ago

Can it be a bad error message caused by this documented behaviour?

(Application.ObjectStoreAccessException) —

Thrown if called from a background process on device that does not have ConnectIQ 3.2.0 support

Ultra over 1 year ago in reply to flocsy🤠

It has now worked on subsequent executions. No change to that bit of code. I’m wondering if it was a memory issue though the simulator suggests it shouldn’t be.

flocsy🤠 over 1 year ago in reply to Ultra

are you close to the memory limit?

Ultra over 1 year ago in reply to flocsy🤠

Nowhere near, about 11kB away (background process) and the value I’m trying to delete is about 1kB

Ultra over 1 year ago

Well I’ve moved the delete into a separate function and haven’t seen the error since. I think it may have been an error trying to delete a key from storage when a local variable has a strong reference to that storage key.

flocsy🤠 over 1 year ago in reply to Ultra

no way, that makes no sense

DaveBrillhart over 1 year ago

Are you sure you ever set "codeVerifier"? That might happen if that doesn't exist in Storage.

Ultra over 1 year ago in reply to flocsy🤠

Well it might, depending on what’s going on under the hood. Clearly something going on under the api hood else the error wouldn’t have happened.

flocsy🤠 over 1 year ago in reply to DaveBrillhart

That's an interesting idea. Did you see this happen? The documentation doesn't state that behaviour.

Ultra over 1 year ago in reply to flocsy🤠

I did indeed see it happen, this isn’t a thought experiment. As stated I’ve solved the issue in the app I’m developing. But in an idle moment I might investigate more of the exact conditions causing it.