this post was submitted on 06 Apr 2025
5 points (100.0% liked)

Summit

1391 readers
48 users here now

Community to discuss Summit, an open-source Android app for browsing Lemmy and PieFed.

Get the app on the Play Store.

F-Droid

APK / Obtainum

Source code

Support the app

Support me on Patreon

Website: https://summit.idunnololz.com/

founded 3 years ago
MODERATORS
 

Issue Summary:
When accessing a user's profile in Summit for Lemmy and attempting to view their profile image, the image initially fails to display and shows a black screen. However, tapping the "X" to close the image viewer and then re-tapping on the profile image resolves the issue, allowing the image to be displayed and zoom functionality to work as expected.


Steps to Reproduce:

  1. Open Summit for Lemmy and navigate to a user's profile.
  2. Tap on the user's profile image.
  3. Observe that the screen displays blackness instead of the profile image.
  4. Tap the "X" to close the image viewer.
  5. Re-tap the user's profile image.
  6. Observe that the profile image now loads correctly, and zoom functionality works as intended.

Expected Behavior:

When tapping on a user's profile image, the image should display correctly on the first attempt, allowing users to zoom in/out or interact with the image immediately.


Actual Behavior:

On the first tap, the profile image fails to load and shows a black screen. The image only appears after closing the image viewer and re-tapping the profile image.


Device Information:

  • App Version: 1.58.7
  • Device Model: GALAXY S24
  • Operating System: ONE UI Version: 6.1, Android Version: 14

Additional Notes:

  • This issue impacts user experience negatively and may cause confusion for users trying to view profile images.
  • Reproduction of the issue appears consistent across attempts.

Please let me know if further details or logs are required to assist in resolving this issue. Thank you!

top 1 comments
sorted by: hot top controversial new old
[–] idunnololz@lemmy.world 2 points 1 year ago

Thanks for reporting this issue. This bug was actually pretty annoying to troubleshoot but I figured it out. Will fix in v1.60.x.