Error: Malformed UTF-8 data
See original GitHub issueWhen trying to get a value from localStorage using the get() method, I receive an error stating
Error: Malformed UTF-8 data
This only happens when using non-Base64 encoding.
The stack trace shows:
Error: Malformed UTF-8 data
at Object.stringify (secure-ls.js:1845)
at init.toString (secure-ls.js:957)
at SecureLS.get (secure-ls.js:248)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Why I get Malformed UTF-8 data error on crypto-js?
I encrypt a name and pass it as URL parameter. I was supprised, that the decrypt code did not work It was because...
Read more >Malformed UTF-8 data · Issue #271 · brix/crypto-js - GitHub
Error : Malformed UTF-8 data. But when I try this encrypt(data, '123') and decrypt(data, '123'), it is successful. and why? How to fix...
Read more >Malformed Utf data : r/CodingHelp - Reddit
I am using cryptojs modules to decrypt a encrypted string using key and iv. I am getting the error Malformed utf data error....
Read more >Javascript – Why I get Malformed UTF-8 data error on crypto-js
I try to encrypt and decrypt this string using crypto-js : const str = `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.
Read more >How can I fix the UTF-8 error when bulk uploading users?
Question. When I tried to bulk upload users, I received the following error message: For some reason, the data to import was not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can you guys please clean the localStorage once and try it? If you were on older version, the way data was stored was using a different method than in the latest version i.e. v1.2.1. So, you need to clean the localStorage once before using the latest version
I met the same problem, I resolved it when I clear the local storage