CORS error about flagsmith-js-client

[dabeeeenster]

Hi,

We would need more details on your integration. Can you confirm this is running against the hosted api at api.bullet-train.io?

Can you provide as much info as possible, including browser console logs etc?

[cuongqle]

Yes, my project is running against app.bullet-train.io

I am actually have not much information, but /identify endpoint seem does not get response, and i only able to see CORS error in the console. Seem /identify request has been rejected for that user, not too sure what exactly reason here?

Any provide is really appropriately!
Thanks/Cuong

[dabeeeenster]

We'd need to see explicit code and logs to be able to help I'm afraid.

[cuongqle]

Here are code what i have setup in my project, it written in typescript:

import bulletTrain from "bullet-train-client";

I have wrapped under my static method to catch exception from bullet to see what is exactly error has been throwed.

static identify(id) {
try {
bulletTrain.identify(id);
} catch (e) {
console.error('Error identifying: ', e); <==== this never reached
}
}

The above call send user Id, to ask bullet identify user, and if successed, user info (id / email) will be persisted into bullet.
But as far as i noticed, identify method has been rejected and the error catch never been reached,

I only noticed in console this error:
'https://api.bullet-train.io/api/v1/traits/' from origin 'https://mywebsite' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Which more info you need, just let me know?

Thanks/Cuong

[dabeeeenster]

Does this happen every time you make the call?

[cuongqle]

Yes, it happen every time.

[dabeeeenster]

Are you able to email [email protected] with details of the Environment API key etc and ideally a small piece of code that can be run by itself that reproduces this?

[kyle-ssg]

Additionally to this, it would be worth checking what ID identify is being called with, it could be that unsafe url characters are causing this.

[dabeeeenster]

Are you able to find the request object in the Chrome developer tools network tab, then right click and copy as cURL, then try and run it as a cURL request. Does that work or fail?