Yeah, nothing seemed to work. I even tried explicitly defining the env variable like “EnV_VAR yanr dev” but it didn’t work. I think it added to the env variable of the system but not the running app
It seems like after some rather lengthy amount of time – minutes? hours? – the secrets do start to work.
I feel like the Java and JavaFX replits are just abandoned. There’s never any support here from replit engineers, it’s really frustrating.
I’ve liked using replit for my class this semester, it has some real advantages – but I don’t think I’ll be using it in the future for a Java-based class, it’s just not worth the heartache.
Hi @mprogers sorry to hear this. I use Java repls with my classes too and secrets haven’t caused a headache yet. However maybe there is a reason for this and I’ve just been fortunate so far.
I’ve passed on this topic to support so they can respond. Sorry to ask but if there are any other outstanding Java issues that you’ve previously posted about could you link them in this topic?
As I noted, after some lengthy period of time the secrets do start to work.
I’ve already filed bug reports on a few other problems (just search on my name). A few that come to mind are … the autoformat/indent button not always showing up, no JavaDoc auto-generation, (not really a bug), the inability to debug in JavaFX, and autocompletion just not working some of the time.
I also made several feature requests - the ability to modify a Teams for Education project once its been published and have those changes pushed to my students; the ability to integrate GitHub Copilot (which is free for teachers, as opposed to Replit’s $olution); the ability to color the currently executing line so I can see it when debugging.
Anyways, these are already in the system, I’ll just wait for them to be addressed. [Tbh, I was really hoping that Replit.com would announce VSC integration during their Developer Day announcements, but I don’t think that happened …]
Secrets should be accessible to the program as soon as they are saved. The only caveat is the shell, which you will need to close and reopen in order for the environment variables to be accessible.
People who run your repl from the cover page or fork your repl can’t access its secrets. If the repl has a website and they access the website, they can then, but not otherwise.