question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

You attempted to set the key `_65` with the value `1` on an object that is meant to be immutable and has been frozen.

See original GitHub issue

Current behavior

Error being thrown when calling getItem and resolve within function is called.

This started happening randomly and I cannot seem to figure out why. Whenever get item is called this error is being thrown.

You attempted to set the key `_65` with the value `1` on an object that is meant to be immutable and has been frozen.

Expected behavior

I should be expecting it to return a stored item without this error.

Repro steps

I have not figured out how to repro it as I’ve never had this error before, I don’t even know if it is directly related I am just following the logs at this point.

  • Try to call getItem to a large storage item?
  • It seems to be returning debug-local from the requested storage key, which is also debug-local.

Environment

  • Async Storage version: 1.6.1
  • React-Native version: 0.60.4
  • Platform tested: iOS
  • Logs/Error that are relevant:
ExceptionsManager.js:86 You attempted to set the key '_65' with the value '1' on an object that is meant to be immutable and has been frozen.
- <unknown>: AsyncStorage.js:86:10

To get around it I am just doing this:

if (value) {
  resolve(value);
}

As that seems to work for now.

It seems that the value is returning null and is breaking only on this specific call from debug-local haven’t seen that before.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

9reactions
CatapultJessecommented, Sep 23, 2019

For anyone else seeing this error I was also getting it when using this library with redux-persist, and accidentally trying to store a promise in my store.

2reactions
krizzucommented, May 29, 2020

Hey you see values like _65, it means that you used Promise as value. Try to find if there’s a place in code where you forgot to await a value

Read more comments on GitHub >

github_iconTop Results From Across the Web

You attempted to set the key on an object that is meant to be ...
You attempted to set the key 'active' with the value 'false' on an object that is meant to be immutable and has been...
Read more >
You attempted to set the key on an object that is meant to be ...
Coding example for the question You attempted to set the key on an object that is meant to be immutable and has been...
Read more >
detectron2.config
If not given, return all keys (whose values are config objects) in a dict. ... std has been absorbed into its conv1 weights,...
Read more >
Python Sets Tutorial: Set Operations & Sets vs Lists - DataCamp
It is important to keep in mind that a major disadvantage of a frozenset is that since they are immutable, it means that...
Read more >
Object Reference for Salesforce and Lightning Platform
Boolean fields have one of these values: true (or 1), ... If a custom field on a custom object has unique set to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found