-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[source-amazon-seller-partner] OAuth fails silently, missing app_id #53181
Comments
I have another deployment of Airbyte (1.3.1) that is running source: amazon-seller-partner version 4.4.7 and it has a field for refresh token, does not have a button called "Authenticate your Amazon Seller Partner account" and it works. |
I downgraded my source to version 4.4.7 on the problem instance, but it still doesn't show a field for the Refresh Token and still does not work. I'm suspecting that perhaps the Amazon Seller Partner source is not ready for Airbyte 1.4 and I'll need to downgrade to 1.3.1. |
@fitzyjoe |
@bazarnov Here is a side-to-side screenshot comparison for the connector settings UI including the optional fields. Thanks for your help. |
Thanks for the update @artem1205. I haven't had the chance to test yet. I reverted to 1.3.1 for now and will test an upgrade to 1.4 again in the near future. |
Connector Name
amazon-seller-partner
Connector Version
4.5.0
What step the error happened?
Configuring a new connector
Relevant information
I'm using Airbyte OSS. When I create a new Amazon Seller Partner source, I specify the following:
and then I click the button to "Authenticate your Amazon Seller Partner account". I see no visual result after clicking the button. When I view the developer tools network tab I see that my request yields a 500 response and the response body looks like this:
I see this thread seems to be related to the addition or removal of the app_id parameter:
Also docs for this connector are confusing as they reference a "Refresh Token" as a parameter for Airbyte Open Source, however no Refresh Token configuration field is found in the UI.
I wonder if this is a similar issue to the very recently reported issue with the instagram connector.
I believe I'm running Airbyte 1.4
Relevant log output
Contribute
The text was updated successfully, but these errors were encountered: