Images won't load and unable to insert images into Logseq #bug

[zionchan00]

What happened?

Starting either a week or two a week ago my Logseq started becoming unable to accomplish the above tasks. All blocks with images in them have replaced the images with 'image.png'. When I click on the block to view the text which links to the image within my files, the text command seems to be normal. Furthermore, I cannot upload images anymore to Logseq, either through the / command > selecting a file nor through copy paste.

Reproduce the Bug

1. Upload an image to a page
2. Image should not be displayed. Instead, an icon which represents a file will behest to the text 'image.png' . If one had my bug, they would not be able to upload images at all so this step would not even happen

Expected Behavior

No response

Screenshots

The syntax for the image to load seems unchanged

Desktop Platform Information

M1 Mac synced to google drive

Mobile Platform Information

No response

Additional Context

No response

[xyhp915]

Hi @zionchan00 Could you try to open the image file that located in assets directory to check file is broken or not?

[quickdudley]

I also seem to have the same bug on the mobile app.

• Logseq version: 0.6.7
• iOS version: 15.4.1
• Device model: iPhone X

[quickdudley]

@xyhp915 continuing to assume the same underlying cause: in my case the image is still valid and present in the assets folder. The embed was displaying correctly last time I looked at the page it's on; the App Store has updated Logseq once since then.

[EngineerLeonJ]

Thanks. Remove the space and problem solved.

[Satoriq]

I have similar problem Platform: mac m1(12.4 macos), local db, chromium, logseq v0.6.3 Images are present in assets and can be opened by mac default image viewer Renaming images doesn't solve the problem Opening logseq local folder in private mode doesn't solve the problem All images created till the moment of problem occur are broken, newly created local images are fine (same format .png, same file name pattern, same place in assets folder) Remote(url) images are fine

[cnrpman]

Closing this since the issue @Satoriq talking is about the outdated browser deployment.