Checks
- I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:
After the app has been updated, the next time it’s opened it shows the changelog (version history).
(See #2852)
Describe what you expected to happen:
I expect opening the app to have it authenticate me to give me access to my passwords. The changelog is a needless detour.
I appreciate the work that goes into developing the app without seeing the changelog. I can find the changelog myself, should I feel the need to read it.
What version of Keepass2Android are you using?
1.12-r5
Which version of Android are you on?
15
I was initially going to report this as a bug, but then I realized I’m in the beta program, so the issue could be specific to that. The unprompted version history at startup is an irritating interruption to using the app, and I could leave the beta program, if I knew that doing so gets rid of the interruption. (I’ve had no other issues with the beta AFAICR.)
What version of Keepass2Android are you using?
1.12-r5
Ah, apparently ”Show content warnings” on the app is the opposite of what’s ”Always expand posts marked with content warnings” in the web UI. I was confused because the former refers to the warning, whereas the latter refers to the content. There may be minor usability issue there, but I’ll leave it out of this one.
Sorry for the noise. To make up for it, #290 looks like a duplicate of this one and thus could possibly also be closed.
Leveä lumipalle liikennevalonappipurnukoiden edessä tässä risteyksessä.
Hi @amyblais,
I could post this on the feature idea forum, but I can’t figure out how the signup on the site works. When I click on ”Create an account”, I get a prompt to verify my email address, and having done that, a page saying ”Go back to Production to finish logging in”. I don’t know what ”Production” is, and at no point was there any actual way to set up a password, so I can’t log in.
Summary
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Environment Information
- Device Name: Samsung Galaxy A9
- OS Version: Android 10
- Mattermost App Version: 2.11.0
- Mattermost Server Version: 9.3.0
Steps to reproduce
- Receive a message notification on the Android app.
- Pull down the notifications.
- Expand the received notification.
Expected behavior
Have a ”Mark read” option underneath the expanded notification.
Observed behavior
No ”Mark read” option, only ”Reply”.
I was on my Android device, saving URLs pointing to individual comments in threads at Ubiquiti’s Unifi forums, but later returning to them on my desktop realized that the hash (fragment) portion had been dropped, so that the URLs only pointed to the opening post. Hence, just one link (pointing to the first post) had been saved. This is pretty useless for threads spanning multiple pages, where finding an individual comment is tough without the exact link.
Here’s a (random) example of a URL pointing to the second comment on the third page of one thread. Sharing it from any of Android, iPhone or desktop results in a link pointing to the first post instead.
Näyttää selaimessa vanhaa selkeämmältä ja paremmalta, mutta tästä puuttuu reseptiyhteenvedon tulostaminen, joka on yksi minulle tärkeimmistä toiminnoista vanhassa (ruukaan tulostaa yhteenvedon PDF-tiedostoon, jotta voin tarkistaa jäljellä olleet määrät ilman, että tarvitsee kirjautua). Se ei haittaisi, jos tämä uuden näkymä olisi tällaisenaan nätisti tulostuva, mutta tässä ei ilmeisesti ole tulostusta ajateltu vielä ollenkaan, vaan tulosteeseen tulee valikkoa ja muuta turhaa roskaa.
Not only did they make the perfect stereo for the Patrick Batemans out there, they also hired a psychopath to design the UI.
I’m affected by this. Storied from PBS appears the only one of my followed channels to exhibit this, though it may very well just be the only one with audio description tracks provided. For instance, this video has the first description at t=71 (”A huge orange eye opens”). As with Yuseldin’s example, the descriptive track is available, but not selected by default when I open the video in a browser.
