Error MD5100 - Marketplace Appstore workflow

[Patrick4]

Hello, My application is published this week and I am trying to access it through the Marketplace but it is giving me the following error MD5100. Can someone help me to understand what this error is?

[ShivikaK]

Hello @Patrick4

Thank you for raising this issue.

Can you attach a screenshot displaying the error along with your application ID?

Thanks, Shivika Khare Selling Partner API Developer Support

[Veodin]

We are seeing this same issue. Did you ever solve this Patrick?

[ShivikaK]

Hello @Veodin,

Can you share the case ID that was created when you submitted the app to be published?

Thanks, Shivika Khare Selling Partner API Developer Support

[Veodin]

The app is status is draft. It is not published yet. We are testing with the version=beta parameter.

On Wed, 7 Apr 2021 at 00:55, Shivika Khare @.***> wrote:

Hello @Veodin https://github.com/Veodin,

Can you share the case ID that was created when you submitted the app to be published?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/amzn/selling-partner-api-models/issues/1143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQALK3USCPUAVIOZKQZS3THONODANCNFSM4ZNNIHXQ .

[ShivikaK]

Hello @Veodin

Can you share your app ID so we can review the configuration? Do you have OAuth information added to the application?

Thanks, Shivika Khare Selling Partner API Developer Support

[Veodin]

Hi Shivika,

Yes, we have added the OAuth information to the application. The app ID is: amzn1.sp.solution.32b659b9-c356-4351-ab0a-ea50e7b592b1

On Wed, Apr 7, 2021 at 1:05 AM Shivika Khare @.***> wrote:

Hello @Veodin https://github.com/Veodin

Can you share your app ID so we can review the configuration? Do you have OAuth information added to the application?

Thanks, Shivika Khare Selling Partner API Developer Support

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/amzn/selling-partner-api-models/issues/1143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQALK4ZILQSJWIRRQBGBTTHOOT5ANCNFSM4ZNNIHXQ .

[ShivikaK]

Hello @Veodin

Your app setup looks proper. Can you share the OAuth authorization URL you constructed to test the workflow? Are you able to see the Consent page or does it throw an error prior to that?

Thanks, Shivika Khare Selling Partner API Developer Support

[Veodin]

https://sellercentral.amazon.co.uk/apps/authorize/consent?application_id=amzn1.sp.solution.32b659b9-c356-4351-ab0a-ea50e7b592b1&version=beta

We are able to see the consent page and amazon then redirects to our test web page correctly. It is after we send the user back to the callback URI that we receive the error message I posted above.

The callback URI that was generated during the last test we ran was: https://sellercentral.amazon.co.uk/apps/authorize/confirm/amzn1.sp.solution.32b659b9-c356-4351-ab0a-ea50e7b592b1?redirect_uri=https://connector.alphalogix.co.uk/&amazon_state=MTYxNzc1ODI1Mjc4NDtj77-9O0Pvv71qQUrvv73Mq--_vX3vv70z77-9JMOeRcuK77-9Je-_vRBSWGdydO-_vQsO77-9Awfvv71425LPgu-_vcOo77-9B--_vRjvv73vv73ona9J77-977-9TDw=&state=TEST&version=beta

[ShivikaK]

Hello @Veodin

This is the OAuth information added to your application as per our record -

"loginurl": "https: //amazon.alphalogix.co.uk/account/amazon", "redirecturls": "https: //amazon.alphalogix.co.uk"

Is this correct?

Additionally, it will be more convenient to work via a support case to resolve this issue. Please open a support case so we can further pursue the investigation.

Thanks, Shivika Khare Selling Partner API Developer Support

[Patrick4]

Hello, My problem was in the consent url. The content was exchanged between 'amazon_state' and 'state'. After correcting this I already got access.

[xslong]

Hi, @ShivikaK
I have the same problem, is it solved? Thanks

[pawan1793]

@xslong I got workaround... changed api type to SP API .... SP API + MWS was not working

[xslong]

Hello @pawan1793 Now the setting is SP API.

[xslong]

Hi, @ShivikaK I have the same problem, is it solved? Thanks

Found the reason, be sure to use other sellers for authorization.

[hrhearn7]

@ShivikaK Can you direct me as to what I need to put in the URI's? Right now I am in draft state. Working through the "Marketplace Appstore Workflow"

In the OAuth Login URI - I have this - and it gets me to the consent page https://sellercentral.amazon.com/apps/authorize/consent?application_id=amzn1.sp.solution.5ba0226e-999f-4a49-8adf-bf8cd388bc6e&version=beta

But pressing the button comes back to the consent page.

What is the correct Value for "OAuth Redirect URI"? I put a value there now that is wrong because I was trying to test and now I cannot clear it out.

I need to try to publish this ASAP - but I want to get past this testing phase. I do have a case ID8294325061

[ShivikaK]

Hello @hrhearn7

The login URI is supposed to refer to the login page of your website during authorization. We recommend not to use the OAuth URL as login URI.

The redirect URI is used to redirect the browser to your application after authorization to receive the oauth information i.e. the SP API OAuth code which is required to get the long term LWA Refresh token along with additional parameters Amazon returns.

https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/developer-guide/SellingPartnerApiDeveloperGuide.md#step-4-amazon-sends-you-the-authorization-information

You can specify more than one redirect by including the redirect_uri parameter in the OAuth URL. If the redirect_uri parameter is not specified, it will default to the first OAuth Redirect URI you’ve defined during app registration.

Hope this helps clarify the confusion.

Thanks, Shivika Khare Selling Partner API Developer Support

[dkt2000]

@ShivikaK

When new seller authorize our app we getting following error.

Error Code: MD5100

and some time blank page.

Our case is is - 8416319541 , can you please check the issue.

[ests]

When you are debugging this particular issue it may be worth checking the "network" tab in browser's dev tools. In my case there was one 400 request, and in the response payload (JSON) you could see detailed error, f.i. "Invalid redirect URL received".

[WXinFfly]

Hello @hrhearn7

The login URI is supposed to refer to the login page of your website during authorization. We recommend not to use the OAuth URL as login URI.

The redirect URI is used to redirect the browser to your application after authorization to receive the oauth information i.e. the SP API OAuth code which is required to get the long term LWA Refresh token along with additional parameters Amazon returns.

https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/developer-guide/SellingPartnerApiDeveloperGuide.md#step-4-amazon-sends-you-the-authorization-information

You can specify more than one redirect by including the redirect_uri parameter in the OAuth URL. If the redirect_uri parameter is not specified, it will default to the first OAuth Redirect URI you’ve defined during app registration.

Hope this helps clarify the confusion.

Thanks, Shivika Khare Selling Partner API Developer Support

Hello. My app Id is amzn1.sellerapps.app.01bd19b4-07f6-47bd-97bc-c6d937760fd2. Why is this app under review? I opened a case in the store backstage and no one responded to me. What should I do?

[byzosoftware]

@deepaktech94 We are receiving the MD5100 error only when appending redirect_uri to the OAuth Url. If we don't specificy redirect_uri parameter everything works fine.

@ShivikaK Why is this? Is this a bug?

Anton

[ests]

@byzosoftware if you don't specify redirect_uri it will take the one you've configured in seller central. If you specify redirect_uri then you must ensure that it matches one of the URLs (if you added more than one) that were added. So for example if you added https://example.com/auth/callback but used &redirect_uri=http://example.com/auth/callback (note no https) in a query or anything other then it will fail with MD5100

[ShivikaK]

Hello @hrhearn7 The login URI is supposed to refer to the login page of your website during authorization. We recommend not to use the OAuth URL as login URI. The redirect URI is used to redirect the browser to your application after authorization to receive the oauth information i.e. the SP API OAuth code which is required to get the long term LWA Refresh token along with additional parameters Amazon returns. https://github.com/amzn/selling-partner-api-docs/blob/main/guides/en-US/developer-guide/SellingPartnerApiDeveloperGuide.md#step-4-amazon-sends-you-the-authorization-information You can specify more than one redirect by including the redirect_uri parameter in the OAuth URL. If the redirect_uri parameter is not specified, it will default to the first OAuth Redirect URI you’ve defined during app registration. Hope this helps clarify the confusion. Thanks, Shivika Khare Selling Partner API Developer Support

Hello. My app Id is amzn1.sellerapps.app.01bd19b4-07f6-47bd-97bc-c6d937760fd2. Why is this app under review? I opened a case in the store backstage and no one responded to me. What should I do?

Hello @WXinFfly

Please open a new issue for app publish queries as your question does not appear to be related to MD5100 error for which this github issue has been kept open.

Thanks, Shivika Khare Selling Partner API Developer Support

[ShivikaK]

@deepaktech94 We are receiving the MD5100 error only when appending redirect_uri to the OAuth Url. If we don't specificy redirect_uri parameter everything works fine.

@ShivikaK Why is this? Is this a bug?

Anton

Hello @byzosoftware

As stated above, your redirect URI information should also be added to the application. Without specifying any redirect uri in OAuth URL, it directs it to the first URI added to the app. If you specify a redirect uri, the URI must match the URI added to the application.

Please let me know if issue still persists after making these corrections.

Thanks, Shivika Khare Selling Partner API Developer Support

[byzosoftware]

@ShivikaK we have added two url to the application. When we append one of the Urls as redirect_uri Parameter to the OAuth Url there is a MD5100 error. Only if we don't append the redirect_uri_Parameter it is working.

Seems to be a not intended behaviour?

Anton

[ShivikaK]

Hello @byzosoftware

It will be help me investigate this issue if you can share the OAuth authorization URL you have constructed which includes the redirect_uri parameter as well.

Thanks, Shivika Khare Selling Partner API Developer Support

[Sellcon]

Hello,

I am a developer and status of my app is published and I have third-party sellers connected to app. Type of my app is hybrid- MWS and SP-API. I had tried to use OAuth SP-API (now I use MWS) and I realized that I have to change my redirect_url. Could you tell me if I edit redirect_url my app will be pending again? Thanks I want to have published status and access all the time without reviewing.

[slopeofhope81]

Hi @ShivikaK

Could you help what the issue is? I spent about last three hours to debug but I am stilling getting MD5100.

My app id is: amzn1.sellerapps.app.083f9454-2663-4d72-a0c3-15a9cc692e28

Error Code: MD5100

I have created the support ticket on this. case_link

[albert2020]

Check whether the language in the application is set to the language of the relevant country. For example: Chinese, Japanese Cannot authorize Europe

[sellershubio]

Hello,

When we are trying to authorization in SP-API, we are getting the error: MD5100

App ID: amzn1.sellerapps.app.d530fe78-51c0-4a4b-8ce3-38f5502d0e24

Error Code: MD5100

[juncai-pan]

hello, I used SP Application to Auth, but get a MD5100 result, like this

App ID: amzn1.sp.solution.15891a75-4618-4351-98ae-65d242ac1073 Error Code: MD5100

we config the 'Auth redirect uri' of the application, but The 'Auth redirect uri' has not been triggered。 why we get this result(MD5100), we must marking the box "Enable OAuth from Appstore" in Edit App page?But donot have this checkbox now!

Looking forward to your feedback, thank you。

[getvicky83]

hello,

I am also getting Error Code: MD5100 I have raised caselog have sent outhURL and chasing for days but havenot got any response.

my developer account is hybrid of MWS and SPAPI, if i try to authenticate the seller's account, it errors. but if i try to authenticate our developer account it doesnot.

My app id : amzn1.sp.solution.2809da35-8fb2-4b0e-bc05-e1d7e590c0a4

looks like lots of people are getting MD5100 error, Is amazon going to put some proper error description?

[getvicky83]

my issues is resolved by engineering team. Looks like it was backend issue

[JungleBooks]

Amazon's back-end? or your application's back-end?

[AbePerl1]

Hello.

I am also getting the same error

App ID: amzn1.sp.solution.ebb92d36-2f9d-45e4-976c-14379ae1ad68

Error Code: MD5100

[getvicky83]

Amazon's back-end? or your application's back-end?

Amazon

[AbePerl1]

As a few developers above mention if we leave the redirect URI empty it works

redirect_uri=&amazon_state

[getvicky83]

As a few developers above mention if we leave the redirect URI empty it works

redirect_uri=&amazon_state whats your Outh URI look like

[a9korn]

Hello, the same problem with Error Code: MD 5100, in my case: my App was published and my own seller account got authorization normal, but each other got the error, tried more ways, also with empty uri (redirect_uri=&amazon_state) but still does not work. now I have opened case and waiting answer from Amazon. if someone has solved this problem - post how you did it.

[ZenSergius]

I had an error when a user tried to log in using vendorcentral URL:

Something went wrong
We are sorry but we encountered an error while processing your request.

Please also ensure that application ID and version match those used at the start of the OAuth workflow. Ensure that your workflow adds the version=beta parameter to the Amazon callback URI to indicate that the workflow is for authorising an application in draft status.

Please contact Selling Partner Support and provide them with the following information:

App ID: <some app id>

Error Code: MD5100

The problem was solved when I checked the "Vendor" option on the application edit page: Maybe this solution will help someone )

[github-actions[bot]]

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

[github-actions[bot]]

closed for inactivity