opening a LN channel with asset with media file breaks acceptor's node

[LastDegenBtc]

Bug description

i created a serie of 10 collectibles on one wallet.
i sent one to a second wallet using the basic rgb invoice from the second wallet.
"waiting for confirmation" was very long in the first wallet.
it went ok in first wallet.
didn't see anything in the second wallet , after a while, i closed the wallet and restart.
now get an error .

joined the link to the log files as proposed by the wallet .

OS version

ubuntu 24.04

App version

0.1.3

RLN node connection type

Embedded

Bitcoin network

Testnet

Installation method

AppImage/DMG

Logs and debug data

iriswallet-logs-1742933761-0.1.3-testnet.zip

[zoedberg]

Thanks for reporting this. Your description doesn't match with what I see in the logs. It seems you opened a channel with a UDA asset with a media file and that's the cause of the issue. This is a known issue that we didn't find the time to fix yet. For now you can manually fix it by taking the exact file you used to issue the UDA asset and put in the directory of the node that was acting as the channel acceptor. The exact location where you should put the file is: ~/.local/share/rgb/iriswallet/dataldktestnet/<rgb-lib_dir>/media_files/ (by inspecting the logs it seems that in your case <rgb-lib_dir> is ac4b5cb9). The file must be renamed to its hash, that you can get by doing sha256sum <file_path> (or you can take the file from the media directory of the node you used to open the channel).

[LastDegenBtc]

thank you . I will try that . even if uda is not you priority, it's great it works too !

…

On Wednesday, March 26th, 2025 at 5:07 PM, Zoe Faltibà ***@***.***> wrote: Thanks for reporting this. Your description doesn't match with what I see in the logs. It seems you opened a channel with a UDA asset with a media file and that's the cause of the issue. This is a known issue that we didn't find the time to fix yet. For now you can manually fix it by taking the exact file you used to issue the UDA asset and put in the directory of the node that was acting as the channel acceptor. The exact location where you should put the file is: ~/.local/share/rgb/iriswallet/dataldktestnet/<rgb-lib_dir>/media_files/ (by inspecting the logs it seems that in your case <rgb-lib_dir> is ac4b5cb9). The file must be renamed to its hash, that you can get by doing sha256sum <file_path> (or you can take the file from the media directory of the node you used to open the channel). — Reply to this email directly, [view it on GitHub](#11 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AWPJTWTQKL7TF5P5CJZPMJ32WK7DVAVCNFSM6AAAAABZYSYN2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJUHE3DANJWGU). You are receiving this because you were mentioned.Message ID: ***@***.***> [zoedberg]zoedberg left a comment [(RGB-Tools/iris-wallet-desktop#11)](#11 (comment)) Thanks for reporting this. Your description doesn't match with what I see in the logs. It seems you opened a channel with a UDA asset with a media file and that's the cause of the issue. This is a known issue that we didn't find the time to fix yet. For now you can manually fix it by taking the exact file you used to issue the UDA asset and put in the directory of the node that was acting as the channel acceptor. The exact location where you should put the file is: ~/.local/share/rgb/iriswallet/dataldktestnet/<rgb-lib_dir>/media_files/ (by inspecting the logs it seems that in your case <rgb-lib_dir> is ac4b5cb9). The file must be renamed to its hash, that you can get by doing sha256sum <file_path> (or you can take the file from the media directory of the node you used to open the channel). — Reply to this email directly, [view it on GitHub](#11 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AWPJTWTQKL7TF5P5CJZPMJ32WK7DVAVCNFSM6AAAAABZYSYN2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONJUHE3DANJWGU). You are receiving this because you were mentioned.Message ID: ***@***.***>