EncryptedLocalStore internal error

[Yuhar]

AIR 26 Beta (May 3,2017).

We use EncryptedLocalStore to encrypt users credentials. This worked fine in all version or AIR until now.

EncryptedLocalStore.getItem(SomeString) results in the below error.

[trace] error.name: Error

[trace] error.errorID: 0

[trace] error.message: EncryptedLocalStore internal error

[trace] Error: EncryptedLocalStore internal error

[trace] at flash.data::EncryptedLocalStore$/processErrorCode()

[trace] at flash.data::EncryptedLocalStore$/getItem()

...

This is currently only tested on the AIR Simulator (Intelli-J) on Mac.

[Yuhar]

The error doesn't seem to happen when running on iOS. It appears to only show on Desktop.

[suriti_singh]

Hi Yuhar,

Can you please try the steps below and see if the problem is resolved.

1. Delete your application data in the folder:

~/Library/Application Support/Adobe/AIR/

2. Reboot the system.

To Investigate further, we need answers to following questions.

Is the problem occurring when you run the swf through adl also? Can you share .air of the application? And what is last AIR version on which it was running successfully?

Thanks,

Suriti

[dews]

Same issue here.  I did as suggested and I'm still getting the same error as described - using the debugger (MAC FB 4.7).

In response to the Q you asked Yuhar, last working version was the release build 25

[suriti_singh]

Can you take a look at the link below and try the solutions mentioned in it?

Unreadable Encrypted Local Store and the general internal error

[amritag9336052]

Hi,

Thanks for reporting the issue. We were able to reproduce it. We are working on the fix for the issue!

[dews]

Did today's release address this?  I don't see this issue listed in the ongoing or fixed sections of the release notes??

[amritag9336052]

Hi,

The latest AIR beta has the issue fixed. You may download it from Download Adobe AIR 26 Beta - Adobe Labs​.

Thanks!

[itlancer]

Sometimes we also still get "EncryptedLocalStore internal error" with latest released AIR 28 with Windows 10.

It happens randomly and cannot be reproduced after application restart.

I don't have exact scenario how to reproduce this, but it still happens sometimes with our clients.