3

Bug Report

Describe the issue: Please describe what happened:

Clicking on comments, read or unread, leads to the white screen in the image.

What you expected to happen:

Connect moves to post, focused on comment and immediate replies.

Steps to reproduce:

  1. Click notification or visit inbox and show all
  2. Click comment
  3. Flash bang

Additional information: the issue resolved briefly when I cleared my cache, but it quickly returned.


Device Information

  • App Version: 1.0.371 (371)
  • Platform: android
  • OS Version: AP3A.240905.015.A2.G996USQSIHYL1
  • Notice: Using legacy Shared Preferences

Modified Settings

The following settings have been changed from defaults:

  • shouldAlwaysOpenInDefaultBrowser: true (default: false)
  • shouldDisplayTitleAbove: true (default: false)
  • shouldLimitCardImages: true (default: false)
  • shouldLoadCrosspostComments: false (default: true)
  • postTitleTextStyle: titleSmall (default: titleMedium)
  • customColoursPreset: 3 (default: 0)
  • enableExperimentalPostSwipe: true (default: false)
  • enableCommentNavigator: true (default: false)
  • shouldHighlightNewComments: false (default: true)
  • defaultRoute: /community?postListingType=Subscribed&hint=Frontpage (default: null)
  • defaultPostSort: New (default: Active)
  • nsfwView: hide (default: blur)
  • cardType: fullwidth (default: card)
  • postActions: [comment, save] (default: [comment, save, none, crosspost])
  • shouldRemembercommentPosition: false (default: true)
  • shouldShowFeedInstanceThumbnail: true (default: false)
  • shouldForceBlackImageBackground: false (default: true)
  • theme: dark (default: system)
top 3 comments
sorted by: hot top new old
[-] kuro_neko@lemmy.ca 3 points 1 week ago

Hi, thank you for the report! I haven't been able to reproduce this issue. I see you're using the legacy DB (Shared Preference). Could you try enabling this setting Settings: Use Drift Database to see if it resolves the issue?

[-] SpikesOtherDog@ani.social 2 points 1 week ago

I actually could NOT enable this at first. I cleared my cache first, no luck. I cleared my data second and it was then enabled when I reopened the app.

The issue does now appear resolved.

Is it possibly the app was storing cache data in the data area? 400 MB seems excessive to me for user data.

[-] RebekahWSD@lemmy.world 1 points 1 week ago* (last edited 1 week ago)

I had been having this issue as well. Also the app was taking around 40 seconds to load and crashed after about 2 minutes.

This change so far seems to be making all three of these things better!

Edit - Still crashing but my phone at this point is very old and bad even when new so that's fine.

this post was submitted on 23 Jan 2026
3 points (80.0% liked)

Connect for Lemmy App

3766 readers
20 users here now

A community for the mobile app Connect for Lemmy.

Links

founded 2 years ago
MODERATORS