[Crash] Old Versions | Close Gracefully #113
Labels
No Label
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#113
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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)
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.
Ref for implementation
https://code.obermui.de/6543/Java_Version_x.y.z_tester/src/branch/master/src/com/company
@mmarif at witch point the app try to log in to an instance at first?
so the check is at first
Check LoginActivity.
https://gitea.com/gitnex/GitNex/pulls/147 close this