I'm trying to replace the file containing the IndexedDB database of my Chrome App with the database from my client's Chrome App so that I can view and get his data.
I've experimented with installing 2 Chrome Apps on my Google Chrome. I've tried to get the database files from
C:\Users[username]\AppData\Local\Google\Chrome\User Data\Profile 3\Storage\ext[chrome_app_id]\def\IndexedDB\chrome-extension_[chrome_app_id]_0.indexeddb.leveldb
folder (1st chrome app) and replace the database files on the second one. But the 2nd chrome app's data is still not updated with the data from the 1st one.
Is there a right way to do this?
I successfully updated the indexeddb database of my chrome app by replacing the database files while chrome is shut down.
Related
I wrote a google chrome extension which should sync data to my chrome profile to all of my computers.
Therefore i'm using the chrome storage api: Google Chrome Storage
I'm able to store and read the data on my primary pc. But on my other computer the data is not accessible.
I'm using the same profile on both computers. And i'm using the chrome.storeage.sync methods.
Because i don't want to publish the extension now i installed the extension with the developer mode activated and not over the chrome store.
Is this the reason why the data is not syncing?
Ok, i now published my app to the chrome store and now it's syncing.
So syncing is not working while your extension is under development.
I am trying to build my 1st chrome extension for which I need it to be automatically logged in when we install that by accessing the local storage of our website if a user is logged in to the website
This is an extension that does almost same thing Storage Area Explorer
I want to remove the last two application links. These two apps are old chrome remote links, each for a different user. Unable to delete with a long press. There is no remote application in the app folder.
It's an app in the chrome app folder.
Right-click the app and open the app in finder.
Delete it.
I have an IndexedDB that was created with Chrome on a VM. I copied the folder to my local machine, and now I would like to see it in devtools. (and I have a script that will create CSVs for me)
My problem is that all the files are deleted as soon as I navigate to the domain and open devtools. It then adds empty LOG and LOCK files.
What I've Tried:
Using the IndexedDB created on my local machine:
Remove and re-add IndexedDB into the same chrome profile on the same machine: works fine.
Copy IndexedDB to a different chrome profile on
the same machine: works fine.
Changing the domain in the DB folder
name: Files not deleted, but DB won't show up in devtools
Using the IndexedDB from the VM:
Copying the IndexedDB domain folder (https_domain...): The files are deleted
and the log file shows: 2020/04/20-15:31:04.420 1cc4 Delete type=2 #897 There is one line for each of the LDB files I copied in.
Copying only the LDB files and manifest file - same issue as above
Cross Posted to:
https://superuser.com/questions/1543794/indexeddb-copy-from-vm-to-local-machine
IndexedDB copy from VM to Local Machine
https://webapps.stackexchange.com/questions/141564/indexeddb-copy-from-vm-to-local-machine
Edit: This has randomly started working, using the same files that I was trying it with before :S
Just recently in the last few days, whenever I use the Google Cloud web interface in Chrome to upload a file into a Storage bucket, I am seeing:
I confirm the file DOES NOT exist in the bucket, it is a random file id name. Uploading files into this bucket from Chrome worked just as recently as last week. I don't think I changed anything related to the bucket. I believe I have updated my browser Google Chrome (69.0.3497.100 (Official Build) (64-bit)) and macOS to Mojave though.
Anybody else confirm?
UPDATE: I was able to upload a file from Firefox successfully to the same bucket (62.0.3 (64-bit)), so it seems to be a regression in Google Chrome 69 which is sort of ironic.
Uploading to Storage in Chrome now magically works. I believe the error was due to AdBlocker which recently pushed an update. Perhaps AdBlocker was the culprit.