You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered an issue when using Edge on my computer where URLs cannot be retrieved. From my research, it seems that there are two profile folders on my computer named "yqpdjyl6.default" and "qxw2p5tx.default-release."
The folder ending with "release" belongs to my current profile, while the other one is presumably a default folder containing a completely empty "places.sqlite" file with no tables.
As a result, the SQL command at line 114 in the "index.js" file directly queries the "moz_places" table, causing a "No such table: moz places" error in the "getHistoryFromDb" function. Consequently, it is unable to read any URLs.
The "getHistoryFromDb" function can be modified accordingly to handle this situation. If the file is empty, it can proceed to the next file without disrupting the loop, resolving the issue.
The text was updated successfully, but these errors were encountered:
Thank you for bringing this matter to our attention. While this project is no longer under active maintenance, we are open to community contributions. Should you wish to address this issue, please feel free to submit a pull request. We appreciate your interest and support.
Hello,
I've encountered an issue when using Edge on my computer where URLs cannot be retrieved. From my research, it seems that there are two profile folders on my computer named "yqpdjyl6.default" and "qxw2p5tx.default-release."
The folder ending with "release" belongs to my current profile, while the other one is presumably a default folder containing a completely empty "places.sqlite" file with no tables.
As a result, the SQL command at line 114 in the "index.js" file directly queries the "moz_places" table, causing a "No such table: moz places" error in the "getHistoryFromDb" function. Consequently, it is unable to read any URLs.
The "getHistoryFromDb" function can be modified accordingly to handle this situation. If the file is empty, it can proceed to the next file without disrupting the loop, resolving the issue.
The text was updated successfully, but these errors were encountered: