createWebView works the same whether your Portal was built from a Client API Key, a
Client Session Token, or
Client Auth credentials. The injected provider holds no credential of its own:
RPC goes to the gateway you configured, and every signing request is bridged back to the native SDK,
which resolves the bearer token per request. No API key or session token is ever exposed to the page.PortalWebView Fragment and adds it to the view.
autoApprove: true if you want the web view to auto-approve transactions.
Optional Parameters
Following are the optional parameters that you can pass to customize the injected provider in the WebView further- chainId: Chain id you want to run the dapp on, by default it is
eip155:11155111 - eip6963Icon: A string representing the Base64-encoded icon for EIP-6963 compliance
- eip6963Name: A string representing the name for EIP-6963 compliance.
- eip6963Rdns: A reverse DNS string for identifying the application in EIP-6963-compliant contexts.
- eip6963Uuid: A unique identifier string for EIP-6963 compliance.