Skip to content
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

not working in extension manifest v3 #896

Closed
rajsko opened this issue Jul 21, 2024 · 6 comments
Closed

not working in extension manifest v3 #896

rajsko opened this issue Jul 21, 2024 · 6 comments
Assignees

Comments

@rajsko
Copy link

rajsko commented Jul 21, 2024

I did not manage to get mpartickle web sdk to run in chrome extension with manifest v3, which runs entirely in service worker that do no support XHR. The events are nor tracked an when I try to set identity only then I get error of Error creating XMLHttpRequest object.. I know you replace xhr with fetch during batching but probably xhr is not replaced everywhere. Am I doing something wrong or is this known issue?

@alexs-mparticle
Copy link
Collaborator

@rajsko Thanks for raising this issue. I'll discuss this with the team and see if we can reproduce. Out of curiosity, can you provide screen shots of any errors related to mParticle in your browser's Network tab or Console? This would help us with our investigation.

@alexs-mparticle alexs-mparticle self-assigned this Jul 22, 2024
@rajsko
Copy link
Author

rajsko commented Jul 22, 2024

Thanks for swift reply!
no error initially in console nor in network tab, only this gets logged after I try to call mParticle.Identity.login
Screenshot 2024-07-22 at 16 18 18

But I think this might help, this is the mparticle instance after initialization. I think some fields are missing like for example _APIClient.

Screenshot 2024-07-22 at 16 17 21

@alexs-mparticle
Copy link
Collaborator

Thank you for the screen shots. We don't have an ETA on the fix but we have begun investigating and will update this issue when we have a solution.

@rajsko
Copy link
Author

rajsko commented Jul 24, 2024

Thanks, though you be able to clarify the ETA horizon in terms of days, weeks, or months?

@alexs-mparticle
Copy link
Collaborator

We'll be investigating this issue within the next week and we'll be able to give you a more accurate estimate timeline then. It will likely be a few weeks before this is released and we'll tag this issue so you can be updated once it is live.

If you need this prioritized more urgently or would like a tracking ticket, please reach out to our Support Team at support@mparticle.com.

@alexs-mparticle
Copy link
Collaborator

Closing as this was fixed by #932, #919, #917, #908, #907, #905, #904 and #898

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants