"No normalized metadata available" despite not changing any generation settings

[Pinkmoth419]

Hi! First off, I want to say how much I love this application and appreciate the work the devs put in. It honestly brought back my enthusiasm for this hobby and so far everything has been almost perfect; I love the tagging system, the layout of the UI, how convenient everything is, etc. I don't even ues the analytics section much but I was quick to get Pro anyway just because. However, I am noticing a very recent issue (just this morning) where newly added images show "No normalized metadata available" instead of any proper metadata despite my confirming that this metadata does exist. I haven't changed any settings, either; I'm using Forge (the A1111 fork) rather than ComfyUI which I understand can be incompatible, so I am wondering if maybe it's a bug? Or maybe the amount of images is too much? I have around 21k. I'm really reluctant to clear the cache and reset everything because I have so many collections and tags that I would hate to have to redo. Any and all help is very much appreciated. This is my first actual issue I think so I apologize if this isn't formatted right! I'm not super familiar with Github beyond just cloning repositories and such.

[LuqP2]

Hi again! First off: thank you so much. Hearing that the app "brought back your enthusiasm" is literally the best motivation I could ask for. And seriously, thanks for grabbing Pro just to support the project — that means the world to a solo dev.

I did some digging after reading your report, and yea, Forge recently pushed a backend update (around handling metadata issues more cleanly for Models/LoRAs). This likely changed the formatting strings (spacing or delimiters) inside the PNG chunks just enough to break Image MetaHub's current Regex parsers.

So, it's not a bug on your end, and your data isn't corrupted! It's just my parser needing to learn the new Forge "dialect".

You could help me fix this for v0.11.0, I just need to see the raw data structure. could you attach one of these problem images into a comment here?
Once I have the file, I can adjust the parser to recognize the new format and include the fix in tomorrow's release.

Even though this is a parser issue, since you have valuable manual tags, let's play it safe before any update:

1. Go to Settings > General.
2. Click the green "Open Location" button.
3. Back up that folder to your Desktop. Now your tags are bulletproof.

A quick note on ComfyUI:
You mentioned avoiding Comfy because compatibility was hit-or-miss. The new v0.11.0 fixes this completely via a new dedicated MetaHub Save Node. If you use it, the app reads 100% of the metadata instantly (VRAM, generation time, prompts), effectively making Comfy support better than A1111/Forge. Just a heads up in case you ever want to try it again!

Standing by for that sample image!