Hi all,

Upon opening Connect, this is the screen I see. Interacting with the gray rectangle minimizes (not closes) the app - tapping elsewhere does nothing. I unfortunately cannot get to the bug report screen for more details. Looking at my settings:

  • Connect is version 1.0.416
  • Phone is a Galaxy S22+
  • Android 16
  • One UI 8.0

I can provide other info if it helps.

Thanks for your help! I appreciate it :)

all 17 comments

sorted by: hot top controversial new old
[–] 7 points 8 months ago (2 children)

I had the exact same thing yesterday. Clear app data made it work again.

  • source
  • hideshow 2 child comments
  • [–] 3 points 8 months ago* (1 child)

    Yes, that worked. I don't know what entails "app data", but it's all gone now. I figured my saved account and subscribed communities are saved at the server, so how harmful can it be?

    Turns out I didn't save my login in my passwordmanager :D

    Edit: Nevermind, it's stored under "sh.itjust.works" and not under "lemmy"

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 8 months ago

    I've reset the app without thinking it through before so I can relate.

    For reference, if there are others who don't know how to clear the app data, here's the steps for me on a Pixel 6 on Android 16. Some things may vary a bit depending on your device and Android version. I tap and hold on Connect and then tap on App Info in the popup menu. Tap on Storage & cache. Then tap on the clear cache button. Don't tap on the clear storage button since you'll lose some stuff.

  • source
  • parent
  • [–] 5 points 8 months ago (1 child)

    Mine started doing the exact same thing this evening. Using Blorp instead at the moment to access Lemmy.

  • source
  • hideshow 1 child comment
  • [–] 3 points 8 months ago (7 children)

    Are you able to bring up the main menu on the left and access Settings? Either with a swipe right on the left edge of the screen or tap and hold, then swipe right on the left edge.

    I'm on 416 as well but I haven't seen this problem though.

  • source
  • hideshow 7 child comments
  • [–] 3 points 8 months ago (4 children)

    For me, tapping anywhere in the darker region does nothing. Any action in the white space backs me out to the phone's home screen, Connect is still open in the background though.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 8 months ago (3 children)

    Just to confirm, you started seeing this after updating to 416? Or was it fine on 416 and you started getting this today?

    What I would try doing is clearing the cache. But don't clear the app storage or you'll lose some stuff. Clearing the cache may or may not help; depending on what's causing the problem.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 8 months ago (2 children)

    My app is set to auto-update, currently on the 416 version, but not sure when the update occurred. Cleared the cache earlier, but issue persists. I verified it wasn't the VPN I use, problem occurs whether it's on or off.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 8 months ago* (last edited 8 months ago) (1 child)

    If you can't access the main menu and you've cleared the cache then unfortunately there's nothing left but to wait for an update to resolve the problem. It looks similar to a problem a bug a few versions back and the dev is quite active so hopefully you'll see the update in the coming days.

    EDIT: Well, technically there is one option but I don't recommend it since you will lose some data. But it would probably fix the problem. But so can an update.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 8 months ago (1 child)

    Have you tried logging in on different servers?

    Do you have any DNS or firewall settings active?

  • source
  • hideshow 1 child comment
  • [–] 3 points 8 months ago

    I had to clear all data and cache this morning too

  • source
  • [–] 2 points 8 months ago* (last edited 8 months ago)

    Hi, thanks for the report and I'll take a look at this today.

    Edit: This issue should now be resolved on the latest version.

  • source