MerginMaps / MerginMaps/mobile
Preview panel does not display images referenced by URL (Android and iOS)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Description
Images referenced by a URL do not render in the feature Preview panel in the mobile app. When an attribute/image widget points to a remote image (HTTP/HTTPS), the panel shows no image (blank/placeholder) even though the URL is publicly accessible and opens in a browser.
Example URL used for testing (public):
https://naschov.cz/wp-content/uploads/2023/04/3-1024x1024.jpg
This reproduces on both Android and iOS.
Environment
PROD
Application (+ app version, build, operating system)
- Actual Android app version: 2025.6.0
- Samsung Galaxy A53 5G, Android 15
- Actual iOS app version: 2025.6.0
- Actual iOS version: iOS 26.0
Steps to reproduce
- Open a project
tester-ws-1/tc05_preview_panel - Click on 3rd point (from left): preview panel with URL image -> Image is not visible in the Preview panel.
Actual results
- The Preview panel does not render the image referenced by the URL (appears blank/no image).
Expected results
- The Preview panel should display images referenced by valid HTTP/HTTPS URLs (where reachable) or provide a clear error if blocked (e.g., unsupported scheme or fetch failure).
- Ideally, the app should cache the image locally for offline reuse once fetched.
Screenshots or logs
Conclusion
Created by GitHub Copilot and supervised by a human test analyst.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in tester-ws-1/tc05_preview_panel using the provided public image URL, on both Android and iOS. Trace the Preview panel's handling of remote HTTP/HTTPS images and define done as displaying reachable images or showing a clear fetch or scheme error; local caching is an additional expected behavior to assess.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp, ios
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100