There’s a new Google Messages update page that takes up your phone’s entire display every time you open the app.
Granted, keeping your apps up to date is important, and this new system will help get that across to users. But we’re not sure annoying the hell out of the user about it is the best strategy.
That’s still (slightly) better than apps which force close when they’re not updated, and don’t allow you to do anything at all.
Firefox on Linux has done this to me a few times and cost me a lot of progress and time.
I never had this issue. What were you using deb, rpm, flatpak or snap version?
I had it this week on my Mint laptop, with the bundled Firefox. I hadn’t used the laptop for a few weeks, so I knew it needed updates, but I needed to get something done straight away.
I opened something in a new tab, and it opened as the restart to update tab. As well as breaking my train of thought, it restarted without opening the new link, but also warned me that it wouldn’t reopen any private browsing tabs and another type of tab that I can’t remember.
However they justify it, that’s bad design.
That’s not Firefox forcing you to update, you had Firefox open while you (/your package manager) was updating Firefox and after the update was done Firefox needs to be reopened. To prevent this you just have to …not update Firefox while it is running.
I didn’t say that it forced me to update. This set of replies is about apps that force close and don’t let you do anything.
My Firefox updated in the background, because that’s how I set my system up, but instead of letting me keep working and updating on the next app start, it forced me to stop what I was doing and update there and then, while telling me that it wouldn’t be restoring any private tabs that I had open.
As a contrast, I was also running Chrome. That also updated, but waited for an app close before completing the update. It didn’t interrupt me, and it didn’t lose any of my open tabs.
Firefox has it wrong in this case.
I’m not near my computer to confirm right now, but I think I installed it manually from the tar file. I think there was an issue with the flatpak version on Pop!_OS, but I can’t remember what, since it has been years since I originally encountered it. I can confirm tomorrow if you want.
It’s weird that someone downvoted your question. I upvoted it to put it back at one. Idk why people downvote questions so often on this platform.
I’m going to guess user error
It’s not. There are several threads about it online
Firefox flatpak version had a lot issues. It has improved a lot, still a long way to go.
I have exclusively used Firefox flatpak for the last year and updates has been quite smooth. Never had my session closed automatically(to my memory) due to an update, usually waits for me close the session and when I reopen its updated.
My experience is limited to Ubuntu.
Xbps on Void does it for sure.
What else is an app supposed to do if the server has been updated and is no longer compatible with the app version you are using?
if that happens occasionally, it’s fine. I’ve seen apps which update every other week and do this bullshit.