You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running EW version as is, causing runtime Errors e.g.
Error crypto.getRandomValues() not supported. See https://github.com/uuidjs/uuid#getrandomvalues-not-supported Error: crypto.getRandomValues() not supported. See https://github.com/uuidjs/uuid#getrandomvalues-not-supported%0A at m (main.js:1:2041)%0A at C (main.js:1:2439)%0A at Object.uuid (main.js:1:7729)%0A at a.decisionObj (main.js:1:70858)%0A at e.sendImpressionEvent (main.js:1:71159)%0A at e.decide (main.js:1:86430)%0A at main.js:1:87419%0A at Array.forEach ()%0A at e.decideForKeys (main.js:1:87390)%0A at e.decideAll (main.js:$
Is there an existing issue for this?
SDK Version
5.3.0
Current Behavior
Running EW version as is, causing runtime Errors e.g.
Error crypto.getRandomValues() not supported. See https://github.com/uuidjs/uuid#getrandomvalues-not-supported Error: crypto.getRandomValues() not supported. See https://github.com/uuidjs/uuid#getrandomvalues-not-supported%0A at m (main.js:1:2041)%0A at C (main.js:1:2439)%0A at Object.uuid (main.js:1:7729)%0A at a.decisionObj (main.js:1:70858)%0A at e.sendImpressionEvent (main.js:1:71159)%0A at e.decide (main.js:1:86430)%0A at main.js:1:87419%0A at Array.forEach ()%0A at e.decideForKeys (main.js:1:87390)%0A at e.decideAll (main.js:$
and similar about TextEncoder
Expected Behavior
Everything happens without errors
Steps To Reproduce
SDK Type
Edge/Lite
Node Version
No response
Browsers impacted
No response
Link
No response
Logs
No response
Severity
No response
Workaround/Solution
Hi Optimizely Team,
As Per: https://techdocs.akamai.com/edgeworkers/docs/specifications
https://github.com/perezd/node-murmurhash/blob/master/murmurhash.js#L4
Would you consider a proper workaround doing this in main.ts
Because for me this seem to be working fine
Recent Change
No response
Conflicts
No response
The text was updated successfully, but these errors were encountered: