kevin

+1

@ericcj - We tried that documentation, such as: ``` require 'aws-sdk-core' config.credentials_provider = Aws::STS::Client.new( region: AmzSpApi::SpConfiguration::AWS_REGION_MAP['na'], access_key_id: ENV['AMZ_SP_API_ACCESS_KEY'], secret_access_key: ENV['AMZ_SP_API_SECRET_KEY'] ).assume_role(role_arn: '*****', role_session_name: SecureRandom.uuid) ``` But, we got same error....

Just tried with `config.debugging = true`. Here are the relevant log ( I think ): ``` Calling API: AuthorizationApi.get_authorization_code ... Libcurl initialized ... effective_url=https://api.amazon.com/auth/o2/token response_code=200 return_code=ok total_time=2.760831 ... effective_url=https://sellingpartnerapi-na.amazon.com/authorization/v1/authorizationCode?sellingPartnerId=***&developerId=***&mwsAuthToken=amzn.mws.*** response_code=403...

Hi, we also use self-authorization. Yes, we: - try to migrate from MWS auth to the SP-API, and - we already have the refresh_token set in config. The problem is,...

@Trimakas - not yet. The product owner decides to setup seller account, and it's still on progress.

hi. no error. html.erb get picked up, and I see warns about `[warn] Code style issues found in the above file(s). Forgot to run Prettier?` Complete output: ``` Checking formatting......

@sj26 any update on this? i have same problem to solve. multiple chat rooms, when I moved to another room, then go back to the first one or previous room,...

Update for whoever had same problem with same scenario with multiple chat rooms: I ended up using javascript to prevent creating/subscribing to server when the existing subscription already existed: ```...

any update on this?

Guess this is solved by https://github.com/ngauthier/capybara-slow_finder_errors/commit/cf3da37b861a84c26d293fa2ca749e20a56f0d00