Mobile app closes the keyboard immediately when typing a custom instance URL

(#743) Bug Fixed mobile

Summary

Reporting bugs for the mobile client was put behind a paywall "during the beta period"? I have to pay you money to be able to report bugs for your software? This is really some next level stuff, even beats automatic "stale" issue closing, that some developers are practicing, for reasons I'll never be able to understand. So I'm gonna post it here instead, because I am literally unable to use the client anymore due to recent bugs. I know you'll just close this issue immediately, probably even ban me or whatever, but I don't care, as I find this a really bad decision and a shady practice, and I will speak up about this. I'm sure you can forward this to whoever is working on the Flutter client, if you care. And if I get banned for this, so be it. The actual issue: There is no way to change the server on the mobile client if you cannot connect to the one you've set up already. I changed my domain name, so I needed to change it in the client itself. But I wasn't able, so I deleted app's data. But now I cannot login to my server with the newest mobile client right now, because the keyboard is getting opened and closed immediately after I tap the string field (no, changing the keyboard doesn't help). This problem wasn't present a few versions before. This is on de-googled version, tested on Android 15 (crDroid, Redmi Note 12 4G). 623656484-3fbfd3df-a6d3-4d9a-9f73-a7ba88d288ea.mp4 Whoever is in charge of this, do you really think it's a good idea that people can't report that? I believe beta testers should be paid money for their work, in general, but since this is an open-source software, it's only fair to do testing and reporting for free in exchange to build a better software, open and accessible for everyone. But you're actually ASKING the people who report bugs to pay you money? Ridiculous. This makes me want to support you financially less, not more. There is no justification for this. You could literally just ignore any bug reports on the github repo, but you've chose to deliberately close the issues instead and made sure to let people know about the private server for the paid subscribers. This is just wrong. Do what you will with this.

Steps to reproduce

  1. Install and open latest de-googled Flutter client for Android via Obtainium
  2. be unable to type in the link to a custom server
  3. go to fluxerapp/flutter_client
  4. be unable to report a bug in any way (unless you pay money to get access to the Fluxer server for the flutter client)

Environment

Version: flutter client OSS v1.0.0-beta.36 OS: crDroid 11.2 (Android 15) Device: Redmi Note 12 4G (23021RAA2Y)
623656484-3fbfd3df-a6d3-4d9a-9f73-a7ba88d288ea.mp4 | 7.2 MB

Merged posts

These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.

Merged from #734 [Mobile App] Cannot change instance url

RexSystemoriginally by @Sollace on GitHub

Report details

Summary

Reporting here as there's no option to report bugs to the fluxer_client repo. When trying to type into the Instance URL field the keyboard is closed immediately and the text box is unfocused preventing you from typing.

Steps to reproduce

  1. Install the arm64-v8a-betafcm-release.apk APK from here
  2. At the bottom of the login screen tap on "Connect to a different instance"
  3. Tap on the text field under "Instance URL"

Environment

Android App (V1.0.0 Beta 36) Testing using arm64-v8a-betafcm-release.apk from here

3 comments

Sign in with Fluxer to comment and vote.
Comment by @Jiralite
RexSystem 1 vote Merged from #734 originally by @Jiralite on GitHub
Email bugs@fluxer.app–this repository is not the right place.
Comment by Hampus
HampusStaff 1 vote originally by @hampus-fluxer on GitHub
You can report bugs to bugs@fluxer.app just as well as you could on GitHub if you're not in the private Mobile community at this time. This is just a temporary way for us to limit our workload, since most people would be experiencing the very same bugs that we're all aware of with a small sample size, for this very early limited alpha. We're not asking for anyone to pay us to submit bug reports. Your issue is currently a violation of our repository's code of conduct.
Comment by Hampus
HampusStaff 1 vote originally by @hampus-fluxer on GitHub
Friendly reminder for the future that there are way more successful techniques to have a productive discussion with someone online or in person than immediately assuming bad intent. Could it be possible that there is a reason for us temporarily limiting our workload as a very small team to not need to deal with the same types of reports over and over again whilst we're working towards something more fleshed out? Could it be possible that we're actually accepting alternative routes to send us bug reports? There are many ways to assume good intent, or at least not assume bad intent, before deciding to be aggressive.