IPFS not working in version 2.20.0, .deb, 2.21.1 AppImage

[despens]

The debian packaged version 2.20.0 of Agregore doesn't do anything when trying to navigate to an IPFS URLs.

The terminal shows an error message:

(node:32554) [DEP0151] DeprecationWarning: No "main" or "exports" field defined in the package.json for /opt/Agregore Browser/resources/app.asar.unpacked/node_modules/js-ipfs-fetch/ resolving the main entry point "index.js", imported from /opt/Agregore Browser/resources/app.asar.unpacked/src/protocols/ipfs-protocol.js.
Default "index" lookups for the main are deprecated for ES modules.
IPFS Version: ipfs version 0.36.0
IPFS bin path: /opt/Agregore Browser/resources/app.asar.unpacked/node_modules/kubo/kubo/ipfs
Error occurred in handler for 'extended-webextensions-browserAction.setIcon': TypeError: The "path" argument must be of type string. Received an instance of Object
    at join (node:path:1354:7)
    at actionIcon (/opt/Agregore Browser/resources/app.asar.unpacked/node_modules/electron-extended-webextensions/index.js:1048:12)
    at BrowserActions.setIcon (/opt/Agregore Browser/resources/app.asar.unpacked/node_modules/electron-extended-webextensions/index.js:523:18) {
  code: 'ERR_INVALID_ARG_TYPE'
}

[RangerMauve]

Hmm that error seems unrelated to IPFS. Which URLs did you try to access and how long did you wait for it to load? IPFS can be very slow to resolve compared to hyper URLs.

Does ipns://agregore.mauve.moe/ resolve? OR ipns://ipfs.tech?

[despens]

Both URLs you suggested do not load. The error on the terminal appears immediately after hitting return in the URL bar or following an ipfs:// link.

With Agregore version 2.16.10 everything loads kind of instantly.

[RangerMauve]

The error is due to the UBlock extension using some extension APIs we don't have supported yet. It's on my TODO list to address it. I think it fires after every URL load.

Could you try the 2.17.1 release as well to see if it broke there? Seems to be when we last updated IPFS.

https://github.com/AgregoreWeb/agregore-browser/releases/tag/v2.17.1

[despens]

Indeed I see the same broken behavior with version 2.17.1!

[RangerMauve]

Ty for checking!

Could you try the following to see if it's a data format issue>

• navigate to Help > Open Data Folder
• Close agregore
• Rename the ipfs folder to something else (or delete it if there's no data you need to save from it)
• Use version 2.20 and see if IPFS loads
• (optional) rename the IPFS folder back if you want to restore its data in the older release of agregore

I have a feeling IPFS's Kubo daemon was lacking some sort of migration script handling. IF you have data in there we could spend some time figuring out how to migrate it manually, but it might be a decent chunk of effort. 😅

[despens]

I tried removing the ipfs directory while Agregore wasn't running.

Once I restart Agregore and navigate to an ipfs:// URL, a new ipfs directory is created. But there is no change in behavior, IPFS data is not loaded.

[akhileshthite]

Yeah, facing the same issue.

[RangerMauve]

I might just downgrade the kubo version and save us some trouble. 😅

[despens]

I'm getting new error when trying to access IPFS sites with the 2.21.1 AppImage version, see console output below that appears after clicking an IPFS link. Effect on the GUI is the same, nothing happens.

IPFS Version: ipfs version 0.22.0
IPFS bin path: /tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/go-ipfs/go-ipfs/ipfs
Error occurred in handler for 'extended-webextensions-browserAction.setIcon': TypeError: The "path" argument must be of type string. Received an instance of Object
    at join (node:path:1354:7)
    at actionIcon (/tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/electron-extended-webextensions/index.js:1048:12)
    at BrowserActions.setIcon (/tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/electron-extended-webextensions/index.js:523:18) {
  code: 'ERR_INVALID_ARG_TYPE'
}
TypeError: Invalid URL
    at new URL (node:internal/url:827:25)
    at normalizeOptions (file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfs-http-client/src/lib/core.js:37:11)
    at new Client (file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfs-http-client/src/lib/core.js:154:18)
    at file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfs-http-client/src/lib/configure.js:28:15
    at createAdd (file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfs-http-client/src/add.js:15:15)
    at Module.create (file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfs-http-client/src/index.js:108:10)
    at Daemon._createApi (file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfsd-ctl/src/ipfsd-daemon.ts:114:45)
    at Socket.readyHandler (file:///tmp/appimage_extracted_0e6a0ce81a468929c2cbf7348c33c30e/resources/app.asar.unpacked/node_modules/ipfsd-ctl/src/ipfsd-daemon.ts:267:18)
    at Socket.emit (node:events:531:35)
    at addChunk (node:internal/streams/readable:561:12) {
  code: 'ERR_INVALID_URL',
  input: '/ip4/127.0.0.1/tcp/2473'
}
[51257:0106/064703.003325:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 3 times!

[RangerMauve]

@despens Yeah I'm a bit confused as to why since I've got it running locally. It might be that some dependency had a patch level update which broke something. I'll try comitting my package-lock for the next release to see if it fixes it. 🤔 I swear it worked for a bit. 😅