Lightning Studio

Hi @gabriel, Please try the following steps: 1. Clear your browser cache and cookies to remove any outdated session data. 2. Log in again to ensure you have a valid session. 3. If the issue persists, try using a different browser such as Microsoft Edge or Google Chrome.

Hi Anirban, Thank you for reporting the issue. We're sorry you're experiencing an endless loading screen when trying to deploy a new component. This may be caused by a temporary glitch or a caching issue. To resolve it, please try the following steps: 1. Clear your browser cache and cookies to ensure there's no outdated session or script causing the problem. 2. logout and login to refresh the page and try again. 3. Try using a different browser (e.g., Microsoft Edge or Google Chrome) to rule out browser-specific issues. 4. Check your internet connection to ensure it's stable during the deployment process. If the issue still persists, please provide the following details so we can investigate further: 1. Any error messages in the browser console (press F12 > Console tab). 2. A screenshot (if possible) of the loading screen w console error (Github). We understand the urgency and are here to help you get back on track as quickly as possible.

Thank you for your valuable feedback — we're glad to hear you're enjoying the tool! You're absolutely right; the ability to cancel or stop a deployment is an important feature, especially when processes hang or take longer than expected. We understand how useful the previous Ctrl + Q shortcut was, and we appreciate you bringing this to our attention. We’re currently working on reintroducing a cancel/stop deployment option in the new version. This feature is on our roadmap and will be available soon to improve your experience and control during deployment. Thank you again for your suggestion and support!

Thank you for taking the time to share your experience — we sincerely apologize for the frustration you've faced. We understand how disheartening it can be to lose your work, especially after putting in so much effort. You're right — since this is a runtime-based app and doesn’t store data locally, an active internet connection is required for most operations, including saving your work. When the connection is lost, the app currently shows a "No Internet" popup, but we understand that it should also handle save attempts more gracefully — ideally with clear error messages and a fallback mechanism. Your feedback is extremely valuable, and we're actively exploring ways to improve this — including adding features like local caching or auto-save for offline protection. In the meantime, we highly recommend regularly backing up your work, especially when dealing with longer or critical edits. We're truly sorry for the inconvenience this caused, and we hope to regain your trust as we continue to improve the experience.