from “@amityco/ts-sdk”: “~6.17.3”,
to: “@amityco/ts-sdk”: “~6.30.0”,
and started to receive CORS errors when testing on from localhost, whit previous version it was working ok…
Access to XMLHttpRequest at ‘https://api.us.amity.co/api/v1/markers/userMarker’ from origin ‘https://localhost:5173’ has been blocked by CORS policy: The value of the ‘Access-Control-Allow-Origin’ header in the response must not be the wildcard ‘*’ when the request’s credentials mode is ‘include’. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
Can you please advise or point me to the right documentation ?
Thank you for information that you provide @lorandd , Could you please send us the Request Header details you’re using when calling this endpoint? This will help us investigate the issue further. Thank you!
I’m not calling that API directly, somewhere in the UiKit is called probably
I have integrated UiKit into a react app which was working correctly and then I wanted to upgrade to this version and i get this erro in the console and the UI is not loading
Please check the Request Headers in the Network tab of your browser’s developer tools. To do this, open the Inspect tool, go to the Network tab, This should help us identify the issue more clearly.
see attached, if you are looking for authorization header that is there and that authorization header is ok as it works with the https://api.us.amity.co/api/v5/sessions API call
Hello @lorandd , Could you please confirm if you have axios configured within your own app, or are you solely using our UIKit?
If you do use axios, could you kindly check if withCredentials is set to true in your default axios configuration? This will help us ensure everything is set up correctly.
As I said earlier I’m not calling the endpoint directly. That endpoint is called from UiKit so it doesn’t matter what I used outside UiKit, no?
But I’m using axios and have the withCredentials = true because I need it to call my API, but with the UiKit integration, it doesn’t work.
I have a working version of UiKit with an older version, but after the upgrade, it doesn’t work anymore so it is most likely something in the new version of UiKIt
Hello @lorandd , We’re pleased to inform you that this issue has been addressed in TS SDK v6.32.1. Please pull the latest code update and test again. If the issue persists, please let us know.
Wow! How is this only being fixed now? Was it never reported before?
Also, don’t you need to update the UI Kit to use this version of the TS SDK to ensure this fix is applied in the UI Kit? because the issue is from the UiKit. I haven’t noticed any version update for the UI Kit yet.
Hello, following your report of the TS SDK issue, our team has addressed it in the updated SDK.
As UIKit is open source, you are welcome to update to the latest SDK version at your convenience. If the issue continues, please let us know. We appreciate your feedback on the UIKit update and will share it with our team.
ok, but I don’t get it… there is an issue in the UiKit and you guys are not updating the UiKit to fix it? so basically the UiKit is useless without this fix as it simply doesn’t load the UI … or nobody is using the UiKit anymore?
