Replace images: no reaction

[ChristianGruen]

Sometimes, images of covers or persons cannot be added/replaced. For example, when I download the following image…

https://portal.dnb.de/opac/mvb/cover?isbn=978-3-7017-1730-9

…and try to assign it to a book, the spinning wheel appears for a fraction of a second, and nothing happens. If an image was previously assigned, it disappears.

Interestingly, I can assign the same image when I open it with PhotoEditor and save it under a different name.

[tfonteyn]

on the one hand...

I started the emulator, started chrome and fed it that image url. Result.. the whole emulator crashed 😵‍💫
Talking of a killer-image 🤣

But on the other hand...

I restarted the emulator with a cold-boot, started chrome, and this time the image loaded just fine.
Saved it to downloads, then started NTMB and use "From Gallery" to assign the image as a front cover.
All worked fine.

1. generate and upload a bug-report. Your logs might contain an indication of what happened.
2. In situations like this, you can long-click the (now empty) cover and from the menu choose "Restore previous image" Obviously only if all things go 'normal', in this particular instance that might fail. The logic behind it is fairly robust though: previous images are renamed before a replace/delete is done.

[ChristianGruen]

I started the emulator, started chrome and fed it that image url. Result.. the whole emulator crashed 😵‍💫 Talking of a killer-image 🤣
I restarted the emulator with a cold-boot, started chrome, and this time the image loaded just fine. Saved it to downloads, then started NTMB and use "From Gallery" to assign the image as a front cover. All worked fine.

;·) …I guessed that this one might be difficult to reproduce. It happens with every maybe 10th image; I could reproduce it on Pixel 8a and a tablet, but I haven’t found a clear pattern when this happens. Whenever it happens, it always happens for this image, and I think it only affects larger images that may need to be shrinked.

This is how the stalled spinning wheel looks like for maybe a second (provided that it becomes visible at all):

1. generate and upload a bug-report. Your logs might contain an indication of what happened.

Done so (probably without valuable information, if I got it right): ntmb-debug-2025-08-18.zip

2. In situations like this, you can long-click the (now empty) cover and from the menu choose "Restore previous image" Obviously only if all things go 'normal', in this particular instance that might fail. The logic behind it is fairly robust though: previous images are renamed before a replace/delete is done.

It could be that this process is not finalized. There is no such menu option:

[tfonteyn]

nothing related to the image indeed.

unrelated: I did see some "AuthorTypeMapper|WARN|map|typeName=..." so I added those to the internal list of mapping.

It could be that this process is not finalized.
likely indeed.

If it happens again, take another bug-report immediately after. Don't forget logs are recycled at each app start, so it's important to generate reports immediately.

[ChristianGruen]

If it happens again, take another bug-report immediately after.

…I did so (well, 2 minutes after the incident).

[tfonteyn]

I checked the sources.... there is really only one possible issue: scaling the image.

All other outcomes would give an onscreen dialog with an error message.

Scaling is left to an OS routine, for reference here

But I don't log the error if it fails... fixing that now. The next version will log a message. We can revisit this issue then.