Campfire on Android crashes while sending from Spark Balance

[BaliDog]

Can I report an issue here, to be addressed in a future update (hopefully)?

Using Campfire on Android, I cannot send from the Spark address. To send from the Spare address I have to send to my own transparent address first, then wait. Then send. Even then, I cannot seem to send more that 5 Firo in one Tx due to a 'mempool' error.

And weirdly, I sent a 16 Firo transaction yesterday, and it sent this amount in three batches - taken from the three most recent amounts sent to the transparent balance from the Spark balance.

Is there a glitch in the wallet, or does this issue arise because not enough people are using Spark?

[BaliDog]

Thanks, but the link did not work:

"Not Found

The requested URL was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."

[justanwar]

@BaliDog Please do not engage with the scammer.

[justanwar]

@BaliDog In Campfire, please do the following:

1. Clear electrumx cache
2. In the Network screen, click on Resync
3. In the Network screen, click on the three dots and do Rescan blockchain

And try sending again.

You shouldn't need to send to transparent first, unless you are sending to an exchange address.

[BaliDog]

Thanks Justan, Rescanning blockchain now. Taking a while. Hours do you reckon? Days or will it be over shortly? In any case when done will give it a test and let you know how it went.  Thanks again, Mr B. Dog 14 Jan 2025, 19:16 by ***@***.***:

…

@BaliDog <https://github.com/BaliDog>> In Campfire, please do the following: Clear electrumx cache In the Network screen, click on Resync In the Network screen, click on the three dots and do > Rescan blockchain And try sending again. You shouldn't need to send to transparent first, unless you are sending to an exchange address. — Reply to this email directly, > view it on GitHub <#8 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AIY2B4V4SWTLTDOSAVYY7D32KTBWBAVCNFSM6AAAAABVEJMIY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBZGI3TONZTGU>> . You are receiving this because you were mentioned.> Message ID: > <firoorg/campfire/issues/8/2589277735> @> github> .> com>

[BaliDog]

Hi Justan, Did all that, and the wallet still crashes when trying to send from Spark balance to Spark address. 14 Jan 2025, 19:16 by ***@***.***:

…

@BaliDog <https://github.com/BaliDog>> In Campfire, please do the following: Clear electrumx cache In the Network screen, click on Resync In the Network screen, click on the three dots and do > Rescan blockchain And try sending again. You shouldn't need to send to transparent first, unless you are sending to an exchange address. — Reply to this email directly, > view it on GitHub <#8 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AIY2B4V4SWTLTDOSAVYY7D32KTBWBAVCNFSM6AAAAABVEJMIY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBZGI3TONZTGU>> . You are receiving this because you were mentioned.> Message ID: > <firoorg/campfire/issues/8/2589277735> @> github> .> com>

[justanwar]

What is the version of Campfire you are using?

[BaliDog]

2.0.3 14 Jan 2025, 20:02 by ***@***.***:

…

What is the version of Campfire you are using? — Reply to this email directly, > view it on GitHub <#8 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AIY2B4RXUDBUAQWASLJZEOL2KTHCRAVCNFSM6AAAAABVEJMIY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBZGM3DMNZXGA>> . You are receiving this because you were mentioned.> Message ID: > <firoorg/campfire/issues/8/2589366770> @> github> .> com>

[justanwar]

Please try a resync or rescan again. Make note of the private balance before and after resync/rescan.

The mempool or crashes might be caused by the wallet trying to use a private balance that was already used but not marked as such by the Electrumx cache, hence why we cleared it and resync to it gets redownloaded.

[BaliDog]

Thanks Justan, There was no change before and after the resync and rescan. And once again the app crashed when it was preparing the transaction. Am running GrapheneOS on a Pixel, if that assists with the diagnosis. Many thanks, 17 Jan 2025, 04:43 by ***@***.***:

…

Please try a resync or rescan again. Make note of the private balance before and after resync/rescan. The mempool or crashes might be caused by the wallet trying to use a private balance that was already used but not marked as such by the Electrumx cache, hence why we cleared it and resync to it gets redownloaded. — Reply to this email directly, > view it on GitHub <#8 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AIY2B4TEH6PQ5KZ7H7SDPNL2K7VUHAVCNFSM6AAAAABVEJMIY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJWGMZTSMRTHE>> . You are receiving this because you were mentioned.> Message ID: > ***@***.***>