Scrolling the notification app list causes "crash"

[Ixo]

It's the exact same issue as described here: https://community.fitbit.com/t5/Android-App/App-crashes-when-accessing-notifications/td-p/3367072

So I won't go into detail... What the op did sadly did not solve my problem. I wrote "crash" bc in detail the app does not crash but sends me back to the previous menu before opening the list of apps for notifications.

What I already tried:
- restart the phone
- uninstall and re-install the app (then restarted my phone again)
- restart my tracker
- delete unused apps (what helped op)

I'm using a Samsung S20. Anyone here to help please? It's pretty frustrating since I can't navigate past the letter "G" but I need to access apps for notifications that start with "T"...

[Ixo · Accepted solution]

Ok, so for anyone also experiencing this: I fixed it in a similar way that the op.

One app in particular was causing the crashing (in my case it was GYMKY). To find out which app is causing the crash do the following:

1. Open the notifications app list and slowly scroll down to the last app BEFORE it crashes (I'll be using op's screenshots here):

So in their case, it crashed after "Fitbit Coach"

2. Now open your apps in your android phone in the settings (wherever they are on your specific phone model); sort alphabetically if this is not the standard sorting method

3. Scroll down until you see the app that you found was the last one before the crash (in their case "Fitbit Coach") - now uninstall the app that comes right AFTER that app.

Now the notification app list scrolling should work again in your fitbit app (at least it did for me).
You might get away without deleting the app but I haven't tried any other steps, as I didn't need the app anyways. So maybe just stopping it, deleting the cache, etc or temporarily removing the app so you can then set up your fitbit notifications and then reinstalling the app would work too.

So yeah, hope that helps someone like me that has been searching for a clear solution. Thanks me 😂

[RiekoC]

Hello @Ixo 

Wow! You did a great job troubleshooting this issue and figuring out the solution.

Thank you for taking the time to share the fix in detail. This will be very helpful to others experiencing a similar issue.