Login problem - iOS for self hosted instances

💬 Mobile
1

Hi,

my colleague and I can not login to Retool via the iOS mobile app (v3.183.0 - build 2132 for me).
It is for a self hosted instance(s) and works on the Android app and on the web browser (same device) without a problem.

Steps to reproduce:

  1. Selecting the self hosted option and entering http/https, the IP / domain name (and the port)
  2. After clicking on the login button the correct login screen appears as overlay.
  3. After entering the username and password the overlay disappears, but the app stays in the screen from before (basic screen when starting the app).

2nd problem:
As I do not have correct DNS resolution in the internal network (as I have a different VPN config), I select http and the IP (no special port in this case). I get then an immediate error message after applying the setting, that the network request failed.
I can still use the login button, which send me to the correct instance though, which then results in the problem above.

We tested that with multiple devices and multiple differently set up self hosted instances, always with the same result. While Android and/or web browser access always worked.

Are there any known problems / solutions?

1 Like
2

Hey @micha Welcome to the community,

  1. App Version: Ensure that you are using the latest version of the iOS app, as updates often include bug fixes.
  2. WebView Login: If your mobile devices have limited memory, consider enabling WebView Login in your organization's Beta settings. This option can reduce memory usage and improve login stability.
  3. Network Configuration: Since you mentioned issues with DNS resolution on your internal network, you might be facing connectivity issues. Ensure that your self-hosted Retool instance is accessible over the network you are connected to. If you have a VPN, check that it does not interfere with the connection to your self-hosted instance.
  4. Test on a Different Network: Try accessing the app using a different network connection to see if the issue persists. This can help identify if the problem is network-related.
  5. Error Messages: If you're receiving specific error messages, those can provide clues about the issue. For instance, network timeouts or connection refused errors usually indicate configuration problems that need to be addressed.

It might be work,

5 Likes
3

Hey, thanks for your response, but I think most of your points I already addressed:

  1. that is the case, I mentioned the app version as well
  2. nice suggestion in general, but did not help here (and my test device is an iPhone 14 Pro, so probably not a memory issue)
  3. It is accessible, thats why I mentioned it works on the web browser on the same device and the login screen appears in the app too
  4. Mentioned as well, tried several different self hosted instances on different networks - all showed the same behavior
  5. I mentioned the error message for the 2nd problem above, the first problem does not show any error message