Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't upload new covers anymore #131

Closed
Fivda opened this issue Jun 7, 2022 · 5 comments
Closed

Can't upload new covers anymore #131

Fivda opened this issue Jun 7, 2022 · 5 comments

Comments

@Fivda
Copy link

Fivda commented Jun 7, 2022

I was able to use custom covers for a while, but for a few days, pretty much near the last time DiscordBee was updated, it doesn't seem like any new assets are being sent to the rich presence assets. Old assets are still there and can be read just fine, it's just there doesn't seem to be any kind of activity when it comes to uploading new ones. I've been stuck at "ASSETS (265 OF 300)" for a while. As you can see i haven't even reached 300.
It works fine with old ones:
image
But when it's a new cover, it just displays the MusicBee logo.
image

I did reinstall DiscordBee and i have the latest features, but it doesn't seem like there's anything. Here's my config:
image

Environment (please complete the following information):

  • MusicBee Version: 3.4.8033
  • Plugin Version: 2.2.1

Had a relatively similar issue a few weeks back:
(#124)

@DrakeIsBruh
Copy link

same thing

@metalglove
Copy link

I have the same problem. No assets get uploaded.

@Terrails
Copy link

Terrails commented Jun 22, 2022

Can confirm this too.

EDIT: found a related issue

@Miguel-Heijmans
Copy link

Miguel-Heijmans commented Jun 25, 2022

I can't upload covers either, I checked the app for covers but none seem to be uploaded. 2FA is on and i relogged, i closed discord closed MusicBee rebooted pc but nothing works. I took a look in the error log for anything related to discord and it seems to be throwing this error:

"System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The remote name could not be resolved: 'discord.com'"

@sll552
Copy link
Owner

sll552 commented Jun 25, 2022

To clear things up, it is not expected to work right now. Discord changed something that broke the way how the uploads are handled. I am working on a replacement which will be finished soon. for more info see #117

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants