Apr 5
Images not visible
I am not able to see the images I upload to events. I can see them in the mobile app but not on the web application.
Completed
Sep 11, 2025
Same issue here(( Microsoft Edge Version 140.0.3485.54 (Official build) (64-bit)
Jul 6, 2025
I can't see markdown images on the web now... in chrome on Windows 11.
Jun 2, 2025
I have seen this issue lately. Here is my console log when it happens: main.dart.js:47447 Logging page view: entry ki8bsbejMAGUP3EYFRow:1 Access to XMLHttpRequest at 'https://firebasestorage.googleapis.com/v0/b/bullet-327a0.app…' from origin 'https://journal.bullet.to' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. main.dart.js:115270 GET https://firebasestorage.googleapis.com/v0/b/bullet-327a0.app… net::ERR_FAILED 200 (OK) Hope it is of some help.
Aug 7, 2025
Window 11 Pro Version 10.0.22631 Build 22631 Chrome Version 138.0.7204.184
May 20, 2025
Maybe it was an issue with particular websites, but I'm seeing markdown images on the web now, so issue closed on my end. Thanks!
Nov 19, 2024
Hi, thanks for the message. Which browser & OS are you using? I cannot reproduce the issue. Also, if you could share a screenshot of the console logs? Here is a tutorial on how to access them https://support.zybooks.com/hc/en-us/articles/30313156553499…
Apr 6, 2023
Thanks for the bug report! Fixed 👍
Sep 2, 2025
Hamish I am still seeing this bug in the web app v1.60.15. I uploaded this image today from the mobile app (console log attached). Version 139.0.7258.155 (Official Build) (64-bit) Windows 11 Pro 10.0.22631 Build 22631
Sep 2, 2025
Access to XMLHttpRequest at 'https://firebasestorage.googleapis.com/v0/b/bullet-327a0.app…' from origin 'https://journal.bullet.to' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.Understand this error js_util_patch.dart:126 GET https://firebasestorage.googleapis.com/v0/b/bullet-327a0.app… net::ERR_FAILED 206 (Partial Content)
This issue is fixed now, thanks for your patience!