Show a button/link for the app’s last update as part of the error screen

[hollownights]

Checklist

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I have read and understood the AI policy. The content of this request is not generated by AI.

Feature description

When there is an app update that the user has not yet installed, and it happens for the app to throw an error, also show a message and a button to download the app’s last update as part of the error screen.

Why do you want this feature?

There is always a bunch of issues opened here after some problem that makes the app unusable, but a lot of them are opened after the issue has already been solved and an update is available. This change may help alleviate this annoyance.

Additional information

No response

It seems to me it doesn't have sense at least in a way you put it. There is already version field available. For normal users who use only stable versions it is enough. When user explicitly uses nightly or nightly refactor they should be able to mention it (btw if the user doesn't mention it is still part of the version reported in a package name). Information is already available and it is much eaisier to compare version strings than update date strings (which IIUC your proposal will be floating due to different users install app in different dates)

[hollownights]

Hi! No, that is not what I'm proposing. I'm not proposing a new field in the error log, but a message and a button on the error screen. Something like:

An error has occurred, but there is a new version of NewPipe that may solve this problem. Click the button below to download it:

[Update the app]

Any other message already shown on the error screen

[Report]
[Retry]
[View in browser]

Hi! No, that is not what what I'm proposing. I'm not proposing a new field in the error log, but a message and a button on the error screen. Something like:

An error has occurred, but there is a new version of NewPipe that may solve this problem. Click the button below to download it:
[Update the app]
Any other message already shown on the error screen
[Report]
[Retry]
[View in browser]

So you propose to add check for updates feature (already available in settings) to error screen?

If user already enabled check for updates it is useless. If is not enabled we could add there "manual" button check for updates. Correct?

[hollownights]

So you propose to add check for updates feature (already available in settings) to error screen?

Exactly.

If user already enabled check for updates it is useless.

It is not. People are bombarded by notifications, and they just zone out from them after some time ("some time" that happened maybe 10 years ago), so a lot of the time people just don't know there is an update available.

If is not enabled we could add there "manual" button check for updates.

Indeed. If the automatic "Updates" check is disabled in settings, and considering people may leave it disabled due to privacy concerns, this check on the error screen should also have to be manually triggered there:

(Only if the automatic check for updates is disabled)
An error has occurred, but there may be a new version of NewPipe that may solve this problem. Click the button below to check for it:

[Check for updates]

(If the automatic check for updates is enabled, check for updates and, if there is one, show this)
An error has occurred, but there is a new version of NewPipe that may solve this problem. Click the button below to download it:

[Update the app]

Any other message already shown on the error screen

[Report]
[Retry]
[View in browser]

[absurdlylongusername]

This feature is intended for people who can't read and to prevent them from opening issues that have been solved in later versions, just to make things easier on the maintainers.

I have no problem with such a feature.

Looks promising. I am going to try implement it once finish small backlog

[hollownights]

This feature is intended for people who can't read [...]

Had not even thought about this, but this rings more true than we may take at face value. Here, all the communications and the issue-opening process are done in english, and in english only. This new message, though, being inside the app, would get translated to however many languages the app is translated to, which may contribute to its intended purpose.

[hollownights]

Giving a little more thought to this and how to make people less prone to report errors when there is no need to do it, I think that even reorganizing the buttons could help a bit. Like this:

(Only if the automatic check for updates is disabled)
An error has occurred, but there may be a new version of NewPipe that may solve this problem. Click the button below to check for it:

[Check for updates]

(If the automatic check for updates is enabled, check for updates and, if there is one, show this)
An error has occurred, but there is a new version of NewPipe that may solve this problem. Click the button below to download it:

[Update the app]

[Retry]
[View in browser]

Error details
Any other error message already shown on the error screen

[Report]

Or another layout (Now I'm convinced this is the best one):

Any error message already shown on the error screen

(Only if the automatic check for updates is disabled)
There may be a new version of NewPipe that may solve this problem. Click the button below to check for it:

[Check for updates]

(If the automatic check for updates is enabled, check for updates and, if there is one, show this)
There is a new version of NewPipe that may solve this problem. Click the button below to download it:

[Update the app]

[Retry]
[View in browser]

[Report]

[hollownights]

Seems like #13320 is gonna be the next big thing. Can this change be fast-forwarded a little bit and make into 0.28.4 (to be released before everyone is facing that issue)?

Hmmm... Well, #13320 doesn't throw an error, so this change wouldn't help right now. Sorry about that.