facing some issue after creating public app even after providing all the access.
Have you made any changes to your repo? (Renamed your account, renamed your repo, renamed or moved your entrypoint file)
I had the same issue
- I was trying to deploy my Streamlit application.
- First, I had the entire application in a single file, which was very messy.
- When I deployed, it worked fine.
- Then I refactored the code, and it showed me the error
You do not have access to this app or it does not exist - I then created a new repository with the initial one-file application. Then again, it worked fine.
- Can anyone explain what mistake I would have made?
@Rithik_Raj I’m not able to view either repo. I get a 404. Are they private?
I’m sorry. I had to delete them for administrative purposes. But I did find what was wrong.
In the refactored code, I had mistakenly left a st.write() funtion in a file that is not in the root folder. Once I removed it, the app deployed without any issues.
But I was able to run the application without any issues in my local system before removing that. Why is that?
I don’t understand the full picture well enough to say.
Taking a very wild guess here, there may be some difference between the working directory used locally vs on Community Cloud. Community Cloud always executes streamlit run from the root of your repository, even if your entrypoint file is in a child directory. This can change how some paths are handled if you CD to the child directory and execute streamlit run from there. (Feel free to switch to your other thread that you opened so we don’t have two conversations running about the same thing.)