The login button become "processing" and gray and no response#1390
Labels
No labels
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✅ Fixed
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🌐 Translation
🌠 Long-term
🎉 Feature
🎯 Enhancement
🏗️ Build
🐛 Bug
👋 Good-first-issue
💀 Deprecation
💡 Suggestion
💬 Discussion
💭 Brainstorming
💰 Sponsored
💻 UI/UX
📄 Documentation
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
📡 Needs-feedback
📱 F-droid
📸 Release
🔒 Security
🔙 Backport
🔙 Has-backport
🔙 Needs-backport
🔙 Regression
🔭 Cannot-reproduce
🗄️ Repository
🗒️ Changelog
🗓️ Summary
🤾 Google-play
🥑 Ready
🧪 Testing
🧺 Cleanup
🧺 Needs-cleanup
🧾 Confirmed
🩹 External-dependecy
🪒 Refactor
🪜 Upstream
🙇♂️ Needs-help
🚀 Improvement
🚨 Investigate
🛡️ Blocked
🛰️ API-dependency
🟦 Website
No project
No assignees
2 participants Notifications
Due date No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#1390
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
# Describe your matter briefly
Input correct or wrong password, the login button become gray and no response
What did you expect?
Login in or show wrong password
Some additional details
The version of Gitea you are using: Codeberg
The version of GitNex you are using: 5.5.0
Source of installation (Play Store, F-Droid, APK): F-Droid
Current android version and phone model/manufacturer: Android Emulator
The type of certificate your instance is using (self-signed, signed): signed
How you used to log in (via password or token): password
We would appreciate some screenshots or stacktrace's, but this is also not required.
Please log in with a token instead of a username and password. The username/password feature is no longer maintained, and I honestly don't have much time for it, as every Gitea/Forgejo release requires testing and debugging.
This feature will be removed from the app in the near future.
If you experience issues with the token as well, please post them here, and we will work through them. I will keep the issue open until I receive your feedback.