Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Access storage.list in CastLabs Electron 28 with Chromium 120 After Offline License Download #189

Open
ranjithrr opened this issue Oct 15, 2024 · 1 comment

Comments

@ranjithrr
Copy link

Description:

We are experiencing an issue after updating to CastLabs Electron version 28 (Chromium version 120). Previously, using CastLabs Electron version 27, we could access storage.list data across multiple domains without any problems. However, after the update, this functionality is no longer working as expected.

Steps to Reproduce:

We use Shaka Player version 2.0.0 for offline license download.
We open multiple Electron windows with different domains (e.g., localhost1, localhost2, localhost3) to speed up the offline download license process.
We randomly allocate the files to download the offline license.
After downloading, when playing the content, we open the player on the respective domain to access the relevant IndexedDB data.
We try to access the offline downloaded license through storage.list but receive an empty array.
If we open the console, navigate to the Application tab, and check IndexedDB, we can see the offline downloaded data.
Expected Behavior:

The storage.list should return the data of the offline downloaded licenses, just like it did with CastLabs Electron version 27.
Actual Behavior:

storage.list returns an empty array, even though the data is visible in IndexedDB when manually checked.
Additional Information:

Shaka Player Version: 2.0.0
CastLabs Electron Version: 28
Chromium Version: 120
The same setup worked as expected in CastLabs Electron version 27.
Could there be any recent security changes or restrictions introduced in Electron 28 or Chromium 120 that might be causing this issue?

@ranjithrr
Copy link
Author

Will you please help me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant