Developer Questions
createAndSubscribe payload resolving before being signed
I am following the https://xumm.readme.io/recipes/xumm-sdk-with-jwt in a XAPP, and I want to run a function after the payload is signed. The payload logs 'resolved' before the transaction is actually signed. Is this intended? Do I need to poll the backend to see if it has been signed manually?
Error Unable to set account Sequence, please check that you are connected to the Internet
Hi Team. I'm getting Error Unable to set account Sequence for all my NFT transactions . I'm using devnet wss://s.devnet.rippletest.net:51233
Get QR code instead of popup window with xumm.authorize().
I am using the PKCE flow for login (xumm.authorize()), but it opens up a popup window with the QR code.
Is there a way to just get the QR code image that I can show on my frontend instead of opening a popup with other info?
Thanks
Error connecting to Ripple API: Error: Error code 603, see XUMM Dev Console
Hi,
Xapp
How can i deploy my custom app in XUMM xapp on testnet
Xumm oath in swift app
Hi Weitze
Can't set up xApp
Hi. I'm trying to set up xApp on a Typescript project but to no avail.
Can't connect react native app to xumm
I am making a react native app which has the simple functionality to send and receive xrp by connecting my app to the Xaman Wallet.
However I cant figure as to how can I connect my react native app to the xaman wallet. I tried registering my app on the developer console and added a redirect url. I then opened the same url through my app however every time the url opens I get an error, which is Error: access_denied Invalid client/redirect url. I have cross checked my api key and matched the url on the developer console with the one in my app. I have been stuck on this any kind of help or pointers will be appreciated.
Cheers
keep getting a invalid API key/secret but they match when I node deplo-commands this happens
PS C:\Users\socia> node "C:\Users\socia\Desktop\XRPL-DEXBot-main\deploy-commands.js"
C:\Users\socia\node_modules\xumm-sdk\dist\src\Meta.js:51
throw new Error('Invalid API Key and/or API Secret. Use dotenv or constructor params.');
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