🚀 Unexpected non-whitespace character after JSON at position 2654
Trying to deploy using
wasp deploy fly deploy which has worked just fine for me several times already this morning. Now getting this very vague error right after the secrets list is displayed in console. Anyone seen this? Is there just something weird going on with Fly?4 Replies
Hi @yaboybloo. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources do not contain specific information about the error message "🚀 Unexpected non-whitespace character after JSON at position 2654" when running wasp deploy fly deploy. There are several discussions about Fly deployment issues, vague or confusing errors, and suggestions for improving error handling and reporting in the Wasp CLI, but this particular JSON parsing error is not mentioned.
Some users have reported that Fly can be flaky and that errors may sometimes be resolved by retrying the command or ensuring that your environment (such as secrets and environment variables) is set up correctly. If the error persists, it may be related to a temporary issue with Fly or a malformed response from their API, but this is not confirmed in the sources.
If you continue to encounter this error, you might consider:
- Retrying the deployment after a short wait.
- Ensuring your Wasp CLI is up to date, as some deployment issues have been fixed in recent releases (Wasp 0.12.4 release notes).
- Checking for any malformed secrets or environment variables that could be causing JSON parsing issues.
- Reviewing the output for any additional clues or context.
If the problem continues, you may want to open an issue on the Wasp GitHub or ask in the Wasp Discord for more targeted help, as others may have encountered and resolved this specific error recently.
Again, the knowledge sources do not provide a direct answer to this error message.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @yaboybloo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai it looks like just waiting a bit worked. How can I mark this as resolved?
Wohooo @yaboybloo, you just became a Waspeteer level 1!
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm glad to hear that waiting resolved your issue! Based on the knowledge sources, there isn't a formal process described for marking a deployment issue as "resolved" within the Wasp CLI or its deployment workflow. If you reported this issue in a public forum (like Discord or GitHub), you can reply to your own thread or issue and let others know that the problem is resolved. This helps the community and maintainers track the status of issues and may assist others who encounter similar problems.
If you haven't posted publicly, no further action is needed—just continue using Wasp as usual. If you encounter further issues, feel free to reach out again!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @yaboybloo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?