Don't rely on ipfs_client_updater component being loaded for clearing IPFS cache #13605
Labels
feature/web3/ipfs
OS/Desktop
priority/P2
A bad problem. We might uplift this to the next planned release.
QA/No
release-notes/exclude
Milestone
brave/brave-core#7578 (review)
This is a follow up issue to fix the case that's been brought up in the review.
Currently we relied on ipfs_client_updater component being loaded to be able to get the executable path from it.
We should keep the last known good path maybe in a pref for us to use, so we could run
ipfs repo gc
even when the component is not yet loaded due to lazy loading.cc @bbondy
The text was updated successfully, but these errors were encountered: