Skip to content
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

Closed
2 tasks done
biller-aivy opened this issue Jul 7, 2023 · 7 comments
Closed
2 tasks done

DiagnoseReportUploadError #12913

biller-aivy opened this issue Jul 7, 2023 · 7 comments
Labels
diagnose not-reproducible Not able to reproduce the issue

Comments

@biller-aivy
Copy link

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

Bildschirmfoto 2023-07-07 um 10 24 13

Expected behavior

Reproduction steps

  • send me a mail where I can send the zip, than maybe you can check

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@biller-aivy biller-aivy added the pending-triage Issue is pending triage label Jul 7, 2023
@josefaidt
Copy link
Contributor

Hey @biller-aivy 👋 thanks for raising this! Do you see any logs that stand out in ~/.amplify/logs or is there a stack trace when you run the same command with --debug?

@josefaidt josefaidt added the pending-response Issue is pending response from the issue author label Jul 7, 2023
@biller-aivy
Copy link
Author

biller-aivy commented Jul 10, 2023

Hey @biller-aivy 👋 thanks for raising this! Do you see any logs that stand out in ~/.amplify/logs or is there a stack trace when you run the same command with --debug?

just:

2023-07-10T09:18:51.485Z|info : amplify diagnose core {"send-report":true,"debug":true,"yes":false}
2023-07-10T09:18:51.593Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({}


The end of the line is no copy issue, this is 1:1 in the log

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Jul 10, 2023
@josefaidt josefaidt added investigating This issue is being investigated diagnose labels Jul 13, 2023
@0618
Copy link
Contributor

0618 commented Aug 26, 2023

I happened to see the same error when there was no env name.

image

@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.

@biller-aivy
Copy link
Author

I just used

  • amplify diagnose --send-report --debug

So I guess, yes there is a env name?!

@josefaidt
Copy link
Contributor

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 --debug support to the diagnose tool in order to better understand the underlying errors.

@josefaidt josefaidt added bug Something isn't working and removed investigating This issue is being investigated pending-triage Issue is pending triage labels Oct 3, 2023
@ykethan ykethan added not-reproducible Not able to reproduce the issue and removed bug Something isn't working labels Oct 11, 2023
@ykethan
Copy link
Contributor

ykethan commented Oct 12, 2023

Closing the issue, if you have any information that would enable us in reproducing this please feel free in reaching out to us.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2023
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
diagnose not-reproducible Not able to reproduce the issue
Projects
None yet
Development

No branches or pull requests

4 participants