Open mirabilos opened 2 years ago
Hi
Please update your client first. The latest RN client version is 4.21. The fdroid version is not maintained at the moment. If you don't want to use google play you can download the .apk directly from our repository's releases page - https://github.com/RocketChat/Rocket.Chat.ReactNative/releases
Thanks.
Debdut Chakraborty dixit:
Please update your client first. The latest RN client version is 4.21.
This is not possible because that version does not exist in a Free Software version.
The fdroid version is not maintained at the moment.
That’s the only FOSS version of that client so please do ensure compatibility with F-Droid clients, server-side. It can’t be that hard.
If you don't want to use google play you can download the .apk directly from our repository's releases page - https://github.com/RocketChat/Rocket.Chat.ReactNative/releases
That’s also nōn-free, containing proprietary components and possibly spyware. This will be hard to make compliant with IT security policies.
bye, //mirabilos -- Infrastrukturexperte • tarent solutions GmbH Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/ Telephon +49 228 54881-393 • Fax: +49 228 54881-235 HRB AG Bonn 5168 • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Same problem from our side. Is there any intention to support the FOSS version? As @mirabilos described, there are security concerns when closedsource libraries are in use.
Best regards.
Description:
The latest available Open Source client, which is version 4.12.1 due to https://github.com/RocketChat/Rocket.Chat.ReactNative/issues/3462, shows the error message “Oops! This is not a Rocket.Chat server. Contact your server admin.” after having logged me out automatically last weekend.
Network or something does not seem to be an issue, as an HTTPS request from the same Android device to the same server indicates a working connection.
Steps to reproduce:
https://chat.tarent.de
Expected behavior:
Connection (given a valid login).
Actual behavior:
The error message shown above. Ah, you want a screenshot… sure:
Server Setup Information:
Client Setup Information
Additional context
Relevant logs:
See above, @tarentadmin might help if needed. But you ought to be able to reproduce this problem locally?