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

File Upload Error Occurring Only When Switching to a Specific Instance #275

Closed
suzuki-ryuji opened this issue Jan 16, 2025 · 8 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@suzuki-ryuji
Copy link

I have a question regarding the error occurring during file uploads.

When the connection is set to a specific instance, two error messages appear during the file upload process.

For the first error, although the message suggests checking the CloudWatch logs, no detailed information is recorded in the logs. Therefore, I close the error popup and proceed to the next step.
20250116_01

However, in the case of the second error (details below), I am unable to proceed, and the file upload cannot be completed.

Details of the Second Error:
At "Step 5," when clicking the final "Submit" button, red text appears below the instance name with the following error message:
{ "Status": "Error", "Message": "Expecting value: line 1 column 1 (char 0)" }
20250116_02

These two errors do not occur when switching the configuration to a sandbox environment or other instances.

I have attached a screenshot of the error from the JavaScript console for your reference. Could you please review the details?
20250116_03
Additionally, the CSV file complies with AMC's requirements, and I have confirmed that it can be uploaded without any issues to multiple other instances.

These errors occur only when switching the upload destination to a specific instance.
When switching the upload destination to any other instance, uploading the same file succeeds without any issues.

Could you please clarify the cause of these problems and provide a solution?

@ianwow
Copy link
Member

ianwow commented Jan 16, 2025

Please complete the following information about the solution:

  • Version: [e.g. v1.0.0]

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0222) - amcufa v1.0.0. This is the base AWS CloudFormation template that defines resources and nested stacks for this solution.". If the description does not contain the version information, you can look at the mappings section of the template:

Mappings:
  Application:
    Solution:
      Id: "SO0222"
      Name: "amcufa"
      Version: "v1.0.0"
  • Region: [e.g. us-east-1]

@suzuki-ryuji
Copy link
Author

The version information for the solution is as follows:
Version: [v3.0.8]

@ianwow
Copy link
Member

ianwow commented Jan 17, 2025

What region? Knowing the region will enable me to confirm that you are using the correct Marketplace Id.

@suzuki-ryuji
Copy link
Author

The region for the solution is as follows:
us-east-1

@ianwow
Copy link
Member

ianwow commented Jan 21, 2025

Your screenshot shows that a marketplace ID for Japan is being used. Try changing that to the marketplace ID for USA, ATVPDKIKX0DER. That value can be set under the Settings page.

Reference:
https://advertising.amazon.com/API/docs/en-us/guides/traffic-events/getting-started#marketplaces

@suzuki-ryuji
Copy link
Author

On the settings page, I changed the marketplace ID to the US marketplace ID, ATVPDKIKX0DER, and tested it, but the same error message appeared, and I was unable to upload.

Image Image

@ianwow
Copy link
Member

ianwow commented Jan 23, 2025

I appreciate the detailed information you've provided. However, for your security, I recommend we continue this discussion in private. Please email amc-support@amazon.com and request to be put in contact with me, Ian Downard.

@ianwow ianwow self-assigned this Jan 24, 2025
@mikeols mikeols added the bug Something isn't working label Jan 29, 2025
@ianwow
Copy link
Member

ianwow commented Feb 14, 2025

This issue appears to have been the result of using LwA tokens from a developer account that lacked the permissions necessary to use the AMC Instance in question.

For now, I'll be closing this issue to keep our active issues list focused on current, unresolved problems. If you need further assistance in the future, feel free to open a new issue.

@ianwow ianwow closed this as completed Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants