Streamlit Cloud does does not allow main file path with emojis?

I created a multipage web app and I would like the Home page to have an emoji just like other pages. It works fine locally. However, when deploying the app to Streamlit Cloud, setting the main file path to :house:_Home.py throws an error “Internal server error: Unable to create GitHub deploy key. Please retry and contact support if it happens again”. Any advice? Thanks.
Screenshot_20220606_212103

Hi @giswqs,

This is a known issue, and we’ll have a fix out for this in the next day or two. I’ll update this topic once it’s released.

1 Like

@vdonato Sounds good. Thanks for the prompt response.

BTW, I have a homepage naming dilemma here. In order to have the short URL (e.g., https://share.streamlit.io/user/repo-name), then I have to name the main file as streamlit_app.py. However, the name (e.g., sttreamlit_app) showing up on the multipage app sidebar is not ideal. If I name the main file as Home.py, then the short URL https://share.streamlit.io/user/repo-name would be inaccessible. It would throw an error You do not have access to this app or it does not exist. I had to use the URL https://share.streamlit.io/user/repo-name/Home.py, which is also not ideal.

1 Like

@giswqs Heads up that the fix is now deployed so should be live (I was able to successfully deploy an app with an emoji in the main module name).

Good point on the short-form URLs no longer being as nice when using a main module with a name other than streamlit_app.py. I’m not sure if there’s a good solution for this, unfortunately, but I also think that this issue will mostly go away in the future when apps are routed to via subdomain rather than URL path, so hopefully this will relatively quickly become a non-issue.

1 Like

@vdonato It no longer works. Do you have a new fix? Thanks.

Hi @giswqs,

Sorry for the delayed reply. I’ve been at a conference this week so haven’t been able to keep up with forum posts/emails.

I think I’ve discovered the root-cause of the issue and believe it has to do with apps with their own subdomains (unless you’re also seeing this as an issue with apps hosted at a given path, in which case I’ll have to reinvestigate).

I’ll relay this to the engineers that own this feature so that they can look into it further (also heads up that I’ll be out on vacation next week so will likely again be slow to respond).