@colegota Hi, I encountered this problem during the first run of the app from time to time (during testing...) , but so far it was really enough to reboot a device /or reinstall #AndStatus... Maybe clearing app data instead of reinstalling will work for you? Please read what helped one of users: https://github.com/andstatus/andstatus/issues/505
@colegota Ok, as I wrote here https://github.com/andstatus/andstatus/issues/511 I think that I need to investigate this case closely using verbose logs of the app. Please backup the app with logs as described... and send me zipped backup folder. Currently I am on vacations, will start investigation next Monday. The bug is weird and needs to be fixed. I couldn't reproduce it, so I didn't fix it before. Please stay turned and help me...
@colegota Thank you for testing. I can think of another way to move forward before I create the permanent fix: Restore AndStatus data from a backup, created on a device, where everything works as expected. This device could be even Android emulator.
@colegota I tried to add new account in #AndStatus v.50.01, and I cannot do this either. Actually, I'm using v.50.01 now and didn't notice any other problems yet. But I didn't add new accounts since last upgrade. So existing users seems like unaffected by this bug.
Will fix the latest version as soon as I will be at my PC (I'm still faraway...)
For the new users: 1. Please uninstall v.50.01, 2. Install v.49 using G-Droid/F-Droid app. I just tried G-Droid, see screenshot - three versions of AndStatus are available. https://f-droid.org/en/packages/org.gdroid.gdroid/ 3. Add all necessary accounts. 4. Create a backup in AndStatus Settings -> Storage -> "Back up app data to SD card". Backups are always good, and in a case step 5 fails you can quickly restore everything, reinstalling v.49 and then Restore this backup from the first screen of the app. 5. (optionally) Update AndStatus to v.50.01 in the same G-Droid/F-Droid app. #G-Droid misbehaved here for me on a first attempt... but after I had restarted it, it updated AndStatus successfully. https://loadaverage.org/attachment/5398183
@colegota In short: Notifications section in #AndStatus settings lists some other things; not timelines. Longer answer: "Unread notifications" timeline includes activities: "create(post) note", "announce (retweet/repost/reblog) note", etc. which were recognized by AndStatus app as belonging to at least one of checked "Notification event types". No matter how the activity was received for some of them (e.g. for mentions) but one-to-one for others: "Home timeline" notification corresponds to the Home API timeline for all Twitter-like APIs (i.e. Twitter, GNU Social and Mastodon) and Inbox API timeline for #ActivityPub client to server API. Meaning of some AndStatus Timelines are changing over time. E.g. even for me it's unclear yet, if "Unread notifications" timeline notifies "the account" (as it was implemented quite long ago) or it should rather notify My Actor who happens to be linked to an account on some server... I clarify this for myself also, and make corresponding changes in the app...