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

Unable to list or create a shippinglabel #64

Open
Coffee-19 opened this issue Nov 12, 2024 · 7 comments
Open

Unable to list or create a shippinglabel #64

Coffee-19 opened this issue Nov 12, 2024 · 7 comments
Assignees
Labels
bug Something isn't working

Comments

@Coffee-19
Copy link

Hi SDCM team,
I encountered an issue while using the latest SDCM to list or create a shipping label.
Here is the SDCM exception log.

List Option shippinglabel

============================================================
SurfaceDevCenterManager Exception Log
Option: ListOption
Section: GetShippingLabels
Type: System.Text.Json.JsonException
Message: The JSON value could not be converted to System.String. Path: $.value[0].publishingSpecifications.visibleToAccounts[0] | LineNumber: 0 | BytePositionInLine: 196.
Inner Exception: Cannot get the value of a token type 'Number' as a string.
Correlation Id: cf5b4e6f-b686-4d21-9176-bdda9cdf0158

To Reproduce
SDCM -list shippinglabel -productid pid -submissionid sid -shippinglabelid slid
or
SDCM -create create_shippinglabel.json -productid pid -submissionid sid

Expected behavior
List a shipping label information or create a shipping label on the partner center

Desktop (please complete the following information)

  • OS: Win11 23H2
@Coffee-19 Coffee-19 added the bug Something isn't working label Nov 12, 2024
@Ben-Carpenter
Copy link
Contributor

@Coffee-19, do you have the latest release 1.2024.911.1?

@Ben-Carpenter Ben-Carpenter self-assigned this Nov 12, 2024
@Coffee-19
Copy link
Author

Coffee-19 commented Nov 13, 2024

Hi @Ben-Carpenter,
Yes, I am currently using the latest version 1.2024.911.1.
It works fine when using version 1.2023.221.1.

@Ben-Carpenter
Copy link
Contributor

Hi @Ben-Carpenter, Yes, I am currently using the latest version 1.2024.911.1. It works fine when using version 1.2023.221.1.

Okay, thanks for the info, we will take a look at see what we can find.

@SenaryNick
Copy link

@Ben-Carpenter I encountered the same issue using 1.2024.911.1. Here is my exception log:

**SurfaceDevCenterManager v1.0.0.1

List Option shippinglabel

============================================================
SurfaceDevCenterManager Exception Log
Option: ListOption
Section: GetShippingLabels
Type: System.Text.Json.JsonException
Message: The JSON value could not be converted to System.String. Path: $.publishingSpecifications.visibleToAccounts[0] | LineNumber: 0 | BytePositionInLine: 187.
Inner Exception: Cannot get the value of a token type 'Number' as a string.
Correlation Id: 7039b04f-d0e1-4246-905f-ac280d19611d

Correlation Id: 7039b04f-d0e1-4246-905f-ac280d19611d
Return: -1000 (PARTNER_CENTER_HTTP_EXCEPTION)**

@Ben-Carpenter
Copy link
Contributor

@Ben-Carpenter I encountered the same issue using 1.2024.911.1. Here is my exception log:

**SurfaceDevCenterManager v1.0.0.1

List Option shippinglabel

============================================================

SurfaceDevCenterManager Exception Log
Option: ListOption
Section: GetShippingLabels
Type: System.Text.Json.JsonException
Message: The JSON value could not be converted to System.String. Path: $.publishingSpecifications.visibleToAccounts[0] | LineNumber: 0 | BytePositionInLine: 187.
Inner Exception: Cannot get the value of a token type 'Number' as a string.
Correlation Id: 7039b04f-d0e1-4246-905f-ac280d19611d
Correlation Id: 7039b04f-d0e1-4246-905f-ac280d19611d Return: -1000 (PARTNER_CENTER_HTTP_EXCEPTION)**

@SenaryNick,

Thank you for your reply and comments. This is on our backlog to check out. Were you able to find a workaround in the meantime?

@SenaryNick
Copy link

@Ben-Carpenter No. I couldn't find a workaround.

@Ben-Carpenter
Copy link
Contributor

Ben-Carpenter commented Jan 9, 2025

@Ben-Carpenter No. I couldn't find a workaround.

@SenaryNick , sorry to hear. Please see comment from Coffee-19 on Nov 12, 2024 in this thread.

Yes, I am currently using the latest version 1.2024.911.1. It works fine when using version 1.2023.221.1.

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