Developer Questions
How to request `EscrowCreate` Sequence number for `EscrowFinish` payload?
ChatGPT would like to apologize for the confusion, so how to request Sequence number for EscrowFinish, wherein the following code successfully connects and signs anEscrowCreate, after which the suggested sdk.getTransaction(txid) line throws undefined:
Error: access_denied
Hey, I've read the docs and all I can find on this error. I am currently using your test code to make sure there was no other issues and I still get the the error.
Uncaught Error: Cannot find module 'crypto-js' at n (xumm-sdk.min.js:1:155)
The module 'crypto-js' is installed in node_modules but no matter what I've tried for about a month and a half now trying to generate xrpl.org escrow condition and fulfillment always references xumm-sdk throwing Uncaught Error: Cannot find module 'crypto-js' at n (xumm-sdk.min.js:1:155) when running:
Decoding JWT from XummPkce
I have followed the XummPkce tutorial here https://github.com/XRPL-Labs/XummPkce/blob/main/sample/jsmodule.html . When you call the XUMM state after being signed in, you can access a JWT token. Decoded on jwt.io , it contains information about the signed payload, the user's wallet, payload etc. What is the intended usage of this? I want to decode it & authenticate this information, so if possible, how can I go about that?
After change settings webhook not working
Could you check why webhooks not working? Where I could check response code?
LocalStorage usage
Hello. Is localStorage API available inside your iframe (xApp)?
I'm fetching runtime.xapp value and i use this value in clientside getting Hydration failed issue.
I'm using xumm:1.2.0 SDK and using that I'm fetching runtime.xapp value in client-side code. But if I use that xapp Boolean value getting Hydration failed issue. Could you please help me to resolve this issue.
dashboard login issue
im not able to login to developers dashboard
Xumm QR Scanning returns opened: true twice
While integrating XUMM with my react app, what I did was created a websocket connection that listens to the events.
Expired transactions
Hello. I'm stumbling upon an issue where transactions generated through the Xumm SDK are failing shortly if not immediately after being generated. The request itself is not failing as the QR code and websocket data are being generated properly, however, the socket sends an { expired: true } event shortly after the transaction is created. This is only happening in some transactions we generate and our team is wondering if this is a normal occurrence with the SDK and just something we should account for or if there is something not being submitted properly along the request