[Crash] Old Versions | Close Gracefully #113

Closed
opened 2020-06-03 16:05:53 +00:00 by 6543 · 5 comments
Member

A user told me the app crashes all the time ...

he uesd gitea version 1.7.x !

we should implement a routine wich check if gitnex is compatible with the version and if not, show a message what is going on at least.

-> "GitNex doesnt support this Version - pleas upgrade your Gitea as son as posible"

with an option to clear the data (so you can use other instances)

A user told me the app crashes all the time ... he uesd gitea version 1.7.x ! we should implement a routine wich check if gitnex is compatible with the version and if not, show a message what is going on at least. -> "GitNex doesnt support this Version - pleas upgrade your Gitea as son as posible" with an option to clear the data (so you can use other instances)
6543 added this to the 2.3.0 milestone 2020-06-03 16:05:53 +00:00
6543 added the
🚀 Improvement
Major-release
labels 2020-06-03 16:05:53 +00:00
6543 closed this issue 2020-06-03 16:05:53 +00:00
6543 self-assigned this 2020-06-03 16:06:33 +00:00
Owner

I am thinking as the changes in API occur rapidly, it's not easy to maintain backports.

Like I personally test on latest commit and latest stable version of Gitea. Means not easy to keep checking each request on different servers, even if can we still need different servers with different Gitea versions installed. Which will make things complicated.

So what I propose is that we keep last two stable version as supported. Like at this moment Gitea 1.8.x and 1.9.x and latest commit of course.
Once Gitea 1.10 come out, Gitea 1.8 will be removed from support.

For this I can think of to implement a check on the login screen what version of Gitea the user have and then show a popup/toast that your version is not supported please upgrade to latest version etc.

I am thinking as the changes in API occur rapidly, it's not easy to maintain backports. Like I personally test on latest commit and latest stable version of Gitea. Means not easy to keep checking each request on different servers, even if can we still need different servers with different Gitea versions installed. Which will make things complicated. So what I propose is that we keep last two stable version as supported. Like at this moment Gitea 1.8.x and 1.9.x and latest commit of course. Once Gitea 1.10 come out, Gitea 1.8 will be removed from support. For this I can think of to implement a check on the login screen what version of Gitea the user have and then show a popup/toast that your version is not supported please upgrade to latest version etc.
Owner
Ref for implementation https://code.obermui.de/6543/Java_Version_x.y.z_tester/src/branch/master/src/com/company
Author
Member

@mmarif at witch point the app try to log in to an instance at first?

so the check is at first

@mmarif at witch point the app try to log in to an instance at first? so the check is at first
Owner

Check LoginActivity.

Check LoginActivity.
Author
Member
https://gitea.com/gitnex/GitNex/pulls/147 close this
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitnex/GitNex#113
No description provided.