-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DiagnoseReportUploadError #12913
Comments
Hey @biller-aivy 👋 thanks for raising this! Do you see any logs that stand out in |
just: 2023-07-10T09:18:51.485Z|info : amplify diagnose core {"send-report":true,"debug":true,"yes":false} The end of the line is no copy issue, this is 1:1 in the log |
I happened to see the same error when there was no env name. @biller-aivy could you make sure there's an env name? If you need more help, we are happy to set up a call with you. |
I just used
So I guess, yes there is a env name?! |
Hey @biller-aivy apologies for the delay here but thank you for your continued patience. I'm going to mark this as a bug to add |
Closing the issue, if you have any information that would enable us in reproducing this please feel free in reaching out to us. |
|
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.1.1
What operating system are you using?
macOS
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Describe the bug
Expected behavior
Reproduction steps
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: