[ThumbOne]

My next bizarre issue in migrating an addon to Kodi 19. The icon does not render.

Again I am stuck as debug logging reveals nothing, and I can find no way to diagnose more deeply.

I have compared the addon.xml with another addon that has an icon and they are identical:

    <assets>
        <icon>resources/icon.png</icon>
    </assets>

I have even tried this:

1. Put the icon from the working addon into my addon's resource folder. Still no luck, not even on a kodi restart. No icon for my addon.
   
2. Replace the icon in the working addon with another image. NO luck. I cannot for love or money, not even restating kodi, get this working addon to change its icon.
   

From 2. I'm assuming kodi has these icons cached somehow and isn't loading after the addon is registered.

To wit, I may need to deregister the addon and reregister it to refresh icon imagry.

But how?

I tried this:

1. Move both addons (the one with an icon, and mine without one) out of the addons folder (to somewhere else)
   
2. Restart Kodi. Confirmed neither addon is visible in Kodi. Tick.
   
3. Move them back (the one with working icon, with a different icon.png image)
   
4. Restart Kodi. The working addon still has its original icon, even though icon.png is a different image. And my addon still has no icon.
   

There is some black magic at work here, and the biggest frustration is lack of diagnostics in the debug log that convey when icon.png is loaded and whether or not it succeeded etc.

Any insights here appreciated.

[DarrenHill]

The support section is for existing addons. This kind of thread is better in the addon development section, as it will get the more appropriate audience to offer assistance.

I'll move it (and the other similar threads you've posted) there.

[ThumbOne]

Thanks kindly! Didn't spot that section! On a learning curve.

[ronie]

sounds indeed like a caching issue.

perhaps this wiki article will provide some clarity on how image caching works in kodi:
https://kodi.wiki/view/Artwork/Cache
in point #5 you'll find instructions on how to refresh a cached addon icon.

[ThumbOne]

@ronie, thanks enormously. That indeed fixed it! I had a strong feeling caching was at play but I'd searched the web endlessly about Kodi caching and did not find those links.

Using the one-liner sqllite query I finally got the cache cleared of that icon, and got the working addon loading a new icon. That is proof of concept that the icon file itself is working. Alas when I reference it as an asset in my new addon it does not load and I am still bamboozled for lack of debugging info as to why.

I wonder (and will search for it) if I can raise the log level to the point where parsing of the addon.xml file is revealed and I can see any errors that may be preventing the asset declaration being respected.

[AvanOsch]

@ronie, thanks enormously. That indeed fixed it! I had a strong feeling caching was at play but I'd searched the web endlessly about Kodi caching and did not find those links.

Using the one-liner sqllite query I finally got the cache cleared of that icon, and got the working addon loading a new icon. That is proof of concept that the icon file itself is working. Alas when I reference it as an asset in my new addon it does not load and I am still bamboozled for lack of debugging info as to why.

I wonder (and will search for it) if I can raise the log level to the point where parsing of the addon.xml file is revealed and I can see any errors that may be preventing the asset declaration being respected.

I'm having the same problem.
I just updated 2 of my own addons to work with Kodi 19 (and python 3), but I can't get the icons to show up.
I reset the entire cache (deleted textures.db and thumnails directory), but still no icons. Just a default "open box" icon.

Does anyone know what's going on?
Did something change in Kodi 19 in regards to icon/fanart images?
By the way, I'm using an Android device to run Kodi.

Thanks!

[AvanOsch]

I believe I found the problem;
It seems transparency is no longer allowed in icon files.
Removing the transparent background, and adding the <assets> tags to addon.xml solved it for me.