Greasy Fork

Seems to have a problem when adding a new set: Your script not list it.

v.0.3.2.2 Tapermonkey / Firefox

Have you tried the Sync button?

Have you tried the Sync button?

Not yet ...
And YES:
That's the solution!

Thanks, Fine work.
;-)
Note:
I don't remember to have read how / when we need to use the SYNC function.
Maybe it's to add to your script info?

When you change something in your script sets, the data on Greasy Fork might not match what's saved in the script. That's when you need to sync.

The script usually handles this automatically—like when you add a script to a set, or during its regular check-ins. But if you create a new set directly on the website, the script won't know until the next auto-sync. If you don't want to wait, that's when you might want to hit the Sync button yourself.

Maybe it's to add to your script info?

Good idea. I've added a brief Q&A.

Good idea. I've added a brief Q&A.

:-)
One little thing:
It seems your script icon is broken...

It's really strange. The icon of this script uses a data: URL format, which is the least likely to be corrupted or fail to load. Do you have a screenshot for that?

Do you have a screenshot for that?

I can for sur, but if i see a "problem" with your icon that's because i use:
GreasyFork script icon

By example, on its script page with it i see its icon:
https://icons.iconarchive.com/icons/custom-icon-design/mono-general-1/64/information-icon.png


Maybe i can't extract your data: url....

I do a request:
Seems your script can't extract data: image

About your Base64 icon:

// @icon data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAAXNSR0IArs4c6QAAAbBJREFUOE+Vk7GKGlEUhr8pAiKKDlqpCDpLUCzWBxCENBa+hBsL9wHsLWxXG4tNtcGH0MIiWopY7JSGEUWsbESwUDMw4Z7siLsZDbnlPff/7n/+e67G38sA6sAXIPVWXgA/gCdgfinRPuhfCoXCw3Q65XA4eLBl6zvw1S2eAZqmvTqOc5/NZhkMBqRSKWzbvgYxgbwquoAX4MGyLHK5HIlEgtFo9C+IOFEAo1gsWsvlUmyPx2MymYxAhsMh6XT6lpM7BXjWdf1xNpuRz+fl8GQywTAMGo0G1WpVnJxOJ692vinADPgcDAaZz+cCOR6PmKZJPB4XUb/fp1wuewF+KoBCf1JVBVE5dDodms3mWdDtdqlUKl6AX+8ALmS9XgtM0/5kvNlspKX9fv8RIgBp4bISCoXo9XqsVitKpRK6rrPb7STQ7XZ7eVRaeAYerz14OBxGOfL7/eIgmUwKzHEcJZEQ1eha1wBqPxqNihufzyeQWCzmtiPPqJYM0jWIyiISibBYLAgEAtTrdVqt1nmQXN0rcH/LicqmVqvRbrdN27bfjbKru+nk7ZD3Z7q4+b++82/YPKIrXsKZ3AAAAABJRU5ErkJggg==

If "GreasyFork script icon" don't extract it, maybe it's due to a formated problem .

Example of an Icon base64 working:

From: GM "Toggle CSS Style"

https://greasyfork.org/fr/scripts/466066-toggle-css-style/code

// @icon data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAxMDAgMTAwIj48dGV4dCB5PSIuOWVtIiBmb250LXNpemU9IjkwIj7wn5SbPC90ZXh0Pjwvc3ZnPgo=

I've also tried "GreasyFork script icon", it works in edge browser on my side. I can see the script icon of my script.
That's strange...

I use Firefox and Tampermonkey.

Yes, that's strange:
In console i have:

A resource is blocked by OpaqueResponseBlocking, please check browser console for details.

And in Browser console:

21:03:34,359 La ressource à l’adresse « https://api.iowen.cn/favicon/get.php?url=greasyfork.org » a été bloquée par OpaqueResponseBlocking. Raison : « after sniff: status code is not in allowed range ».


and Unauthorized for:
view-source:https://api.iowen.cn/favicon/get.php?url=greasyfork.org

The link https://api.iowen.cn/favicon/get.php?url=greasyfork.org was previously used as the @icon for my script, but it was changed to a data URL starting from version 0.16.

It appears that "GreasyFork script icon" has cached the old icon, which is not accessible, resulting in a broken icon. To resolve this issue, try deleting the "308166" key from the script storage of "GreasyFork script icon", or reinstall that userscript entirely.

Oh no, my mistake—it's not "308166" but rather "439699" (that's my script's ID). Deleting this storage key should clean up the cached old icon.

Yes, that's the origin of the "problem" !
:-)

Oh no, my mistake—it's not "308166" but rather "439699" (that's my script's ID). Deleting this storage key should clean up the cached old icon

Haha, too late.

yes, i suspected a strange thing about "308166" without make more search.

When i deleted and reinstall the script.
all its stored data was restored after, so i delete them,
letting only { } in its storage editor..

After that no problem.

Pffff, what a manipulation and questions to solve only that's little thing.

Anyway, that's was always cool to understand and solve it.

Thanks
:-)