aws / aws/amazon-q-connectjs

[Bug report]: library api calls always fails and response is CORS error

Open
#47 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
14
Forks
11
PR merge metrics
No merged PRs in 30d

Description

After invoking and initializing the CCP component in my app, I initialize the amazon-q-connect client.
The API calls like getRecommendations and Qsearch, fail. It is due to CORS handling.
I believe it was working before, also noting that it works fine when disabling the CORS errors in the browser (Chrome)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure after initializing the CCP component and the amazon-q-connect client, calling getRecommendations and Qsearch in Chrome with CORS restrictions enabled. Capture the failing requests and responses, then compare them with a successful run where browser CORS errors are disabled. Done means both API calls work normally without disabling browser security.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.