Question

166

Uncaught TypeError: Cannot read property 'local' of undefined in chrome extension

rated 0 times [ 173] [ 7] / answers: 1 / hits: 22355 / 11 Years ago, wed, february 27, 2013, 12:00:00

I have written a Chrome extension. I cannot use
localStorage.setItem and localStorage.getItem for storing and retrieving because background and browser action runs in different environment [as seen here].

So I decided to use the Chrome storage API:

var storage = chrome.storage.local;

var myTestVar = 'somevar';

var obj = {};

obj[myTestVar] = $(#somevar).val();

storage.set(obj);

which produced the following error:

Uncaught TypeError: Cannot read property 'local' of undefined

What am I doing wrong?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

karivictoriab

Add To Favorites

Follow

Total Points: 530

Total Questions: 90

Total Answers: 95

Location: Honduras

Member since Sun, Dec 26, 2021

2 Years ago

karivictoriab questions

1 JSX props should not use arrow functions eslint warning

Wed, Feb 10, 21, 00:00, 3 Years ago

1 How to scroll and expand an Accordion by onClick on an icon from a component?

Fri, Aug 21, 20, 00:00, 4 Years ago

1 Hide all labels and tooltips in Chart.js and make it very small size

Wed, Apr 8, 20, 00:00, 4 Years ago

1 CORS – Cross Origin Request Blocked – The 'Access-Control-Allow-Origin' header contains invalid value

Fri, Jan 24, 20, 00:00, 4 Years ago

1 VueJs clear form after success

Mon, Dec 30, 19, 00:00, 4 Years ago

View All

answered 11 Years ago kayle · Accepted Answer

Make sure that all necessary permissions have been declared in the manifest file. storage, in your case.

In general, the following steps should fix the problem of apparently undefined Chrome APIs:

Read the documentation of the API you're using and get yourself familiar with the prerequisites, usually manifest permissions (e.g. chrome.storage#manifest).

Check if your (user's) Chrome version supports the API, by looking at What's new.

Check if the script is running in the right context. Most APIs are only available to the extension's process. (the chrome.storage API can also be used in content script though)

Otherwise, resort to your usual debugging skills: Typos, variable shadowing, ...