Detailed description

This is at least true for non-push notifications and there for newer phones:

The ordering of steps regarding notification setup is wrong in "MainActivity.onCreate".
First "fetchUserInfo" will be done - which surprisingly by its name will try all notification setup; e. g. create channels and so on.
Only as the last block after that will the "request notification permission" dialog be triggered.

So after a very first install of Tusky you need to fully restart it (i.e. restart the phone?) in order to get notifications.

Steps to reproduce the problem

1. Create a new virtual device with Api >= 33
2. Start Tusky there
3. Allow notifications when asked
4. There will be no notifications (for example there is the output "NotificationsDisabled" in Logcat)
5. Only after a full restart will there be some

Debug information

Current develop. Bu probably for some time.