Fix: getrandom
dependency issue in WASM build
#213
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
The
ic-crypto-getrandom-for-wasm
package, which is a workaround for thegetrandom
dependency issues in WASM environments, doesn't work in all cases. Sometimes, just including the package inCargo.toml
isn't enough.This PR provides a fix that changes how this package is consumed...
To register this new custom implementation, call the function inside of your canister's
init
method or wherever canister initialization happens, with conditional compilation, like this:Changes
ic-crypto-getrandom-for-wasm::register_custom_getrandom
function.Closes
NOTE