Hi! I'm having the issue mentioned in this page: App's Public link requiring users to sign in to view the Application - #18 by mavenoid
When I share a public link to potential users, they're sent to a login screen. However, based on the replies from the previous topic, it appears as though the issue should have been previously resolved. I would appreciate any help resolving this issue! I am an admin and we have a free account, just for reference.
Hi @aestass,
Apologies for the issue. I was just looking into the other thread and found that in internal ticket was filed for it with our engineering team.
It seems to be a bug where certain components are not fully supported for public mobile apps and thus cause the app to switch from being public to needing a login.
I am checking internally right now to get more details and will hopefully have more info on a short term work around and getting this filed with that bug for our engineers to fix!
It seems that the 'comment' component was causing users to need to login so as to populate their profile for writing comments.
The other case was when users had an image from storage, but we may have fixed that.
Do you have a resource query that has user auth? If you can share an export JSON of your app I can clone it and test further to see what may be causing this 
Hi @Jack_T thanks for the help! I'm not using any comments but I do have an image capture that is being stored in an external S3 bucket. I don't think that should cause the app to require a login, but would love to hear your thoughts on it..
Of course no problem!
Thank you for the details @aestass, if there is a type of auth for the query/resource that is uploading the image to the S3 bucket then that would explain the app needing users to login to verify themselves for security purposes.
In the case that you don't have any auth on the query/resource, I will have to double check on how public mobile apps are set up to see if the login is something that you can change or if it is a hard rule.
Ok so got word back from Tess who was working on the thread you linked.
In the other case, they have a web app which was made public, and thus does not require login(barring the bug which was fixed).
From your screen shot it looks like you are working on a Retool Mobile app, which are unfortunately not able to be made public. Thus requiring users to login to join your org and use any apps that you build.
I check with the mobile team and it seems that currently with our build of mobile apps that it is not possible to make them public. But you may be able to still have your use case via building a web app, making it public and having users access it via the browser on their mobile divices.
Hope that clears things up!
Hi @Jack_T, thank you! That explains my confusion. I think the fundamental problem is the mobile app versus the web app.
