Marketplace Error: release-asset-not-found "null"

[Saidelocha]

What happened?

Hi,

Sometimes, when I try to update plugins I receveid that responde :

[Error] :release-asset-not-found "null"]

Sometimes it's perfectly working, and after a few plugin updated, this message appear and then I can not update anymore plugins. I have to wait a long time until it's working again.

Same time, I wish to ask for a button that update automatically all plugin if new version is released.

Thanks !

Reproduce the Bug

1. Go to marketplace
2. Install a lot of plugins
3. Try then to fetch new releases to upload them
4. Continue until the bug pop in.

Expected Behavior

No response

Screenshots

No response

Desktop Platform Information

masOS Monterey Macbook pro I7 core

Mobile Platform Information

No response

Additional Context

No response

[ncadou]

Seeing the same thing with 0.7.6, also macOS Monterey. Clearing the cache doesn't help.

[feng1o]

me too for 0.7.6 version, macOS. Clearing the cache doesn't help.

[hkunzhe]

me too for 0.7.9 version.

[ceruleannite]

+1, also for 0.7.9

Also noticed that the plugin setting are also missing for all plugins that are installed that previously had setting, with the xception of the "Readwise Office Plugin."

Specifically, the plugins which are now missing in the "Plugin Settings," but are currently installed are:

• Journal calendar
• logseq-todoist-plugin
• Tabs
• Hypthesis
• TOC Generator

[chouti]

+1, also for 0.8.1

[bobmhughes]

+1, also for 0.8.1 on Windows 10 and MacOS Monterey

[u3r]

+1, for 0.8.2 on Windows 10 with a proxy configured; Sometimes even occurrs before the first plugin installed

[ZeevKeane]

+1 0.8.7 on Mac OS

[emms007]

Version 0.8.7 windows same result. No proxy. Surprisingly there is not even a network call triggered. Playing around with the error I can't find any rootcause. Only object error-related entry is:

[AllenDang]

+1 0.8.8 on macOS v12.6

[emms007]

+1 0.8.9

[tokamoto-idcf]

A similar event occurred

0.8.8 macOS v12.6 0.8.9 Windows11

[jessun]

I have the same issue. But it is be fixed after 0.8.9+nightly.20221020 version on my mac.

[gaga5lala]

I have the same issue after upgrading from v0.8.7 to v0.8.9

[xdliyushen]

Same here on macOS v0.8.10

[Pvazevedo]

Some issue after update for v0.8.11 windows 11.

[uhuang]

Same issue across 3 computers (all Win10, 0.8.12) with almost identical plugins installed. Perhaps relevant: attempting to download a Theme will throw the error: download-channel-issue "rate limit exceeded", so maybe I was a bit too enthusiastic with downloading plugins...

[emway66]

issue on 0.8.14 MacOS

[spking11]

Same issue after updating to v0.8.14 on win11. But it will be resolved just a moment later without doing anything.

[oraluben]

Same on 0.8.15, MacOS

[sddhrthrt]

Same on Ventura 13.1, with 0.8.16

[hansenz42]

It could be network or proxy problem. I changed another proxy server and problem solved.

[somnus-L]

use global mode proxy maybe make since. I changed, it's work.

[lsdjr72]

Same problem 0.8.17 MacOS.

[xoyk]

How I reproduce the bug on 0.8.17 Ventura MacOS:

I have checked updates for plugins - a popup with available updates showed up. I closed the popup - because I prefer to check release notes on each plugin's GitHub page. After that, I started to install updates by update button on each plugin, and after I installed all updates, when I click "check updates" a bunch of errors :release-asset-not-found appeared.

[UdeRecife]

I have the same issue. I'm using Logseq 0.8.17 on Arch Linux.

I've updated the plugins with no errors. Then, after reloading Logseq, I was again greeted with a message to update a plugin which I had previously updated, and then those messages started to appear.

This is the second time it happens. Previously, I corrected this by uninstalling all plugins, and then reinstalling them.

[lsdjr72]

I have had the bug reoccur a couple of times as well. But my work around has been to either restart my computer, OR switch networks that I'm connected to. I have two wifi networks, two separate routers, at my house. When I switch networks the error disappears and then I can go back to my faster Internet connection and all is well. I am not a technical person, so I have no idea how or why this fixes the bug. All I know is that it does.

[kjetiljd]

I turned off wifi and then turned it on again, connecting to the same network, and then I could install plugins again, 0.8.17 on MacOS 13.2.1 (22D68).

[Bad3r]

CC: @xyhp915 possibly too many requests?

[zjx14250]

switch networks

[jonsterling]

Having this problem too, switching networks is irrelevant / doesn't help.

[jmignac]

This was happening to me at work. Solved it turning off the network proxy, installing the plugins, and turning it on again.

Logseq 0.8.18 macOS 13.2.1

[wanyt]

This was happening to me at work. Solved it turning off the network proxy, installing the plugins, and turning it on again.

Logseq 0.8.18 macOS 13.2.1

It's worked.

[cnrpman]

Please refer to this for network issues: https://discuss.logseq.com/t/plugin-marketplace-in-logseq-not-loading/13737