Infinite spinning circle

[NateNate60]

Similar symptoms to #143, but the install is not a fresh install. I installed the spark-wallet package on my Ubuntu 20.04 server running bog-standard Bitcoin Core and C-Lightning.

~/.spark-wallet/config contains the following:

ln-path=/home/nate/.lightning
login=[username]:[password]
port=9737

When running, the program DOES seem to be giving 200: OK, but in the browser and Android app, it never progresses past the spinning tricolour circle.

HTTPS server running on https://0.0.0.0:9737
POST /rpc 200 3.641 ms - 581
POST /rpc 200 13.721 ms - 317
POST /rpc 200 26.136 ms - -
POST /rpc 200 3.507 ms - -
POST /rpc 200 3.337 ms - -
GET /worker.js 304 6.713 ms - -
POST /rpc 200 4.188 ms - -
POST /rpc 200 5.350 ms - -
POST /rpc 200 3.059 ms - 581
POST /rpc 200 6.034 ms - 317
POST /rpc 200 3.119 ms - -
POST /rpc 200 2.425 ms - 581
POST /rpc 200 3.731 ms - -
POST /rpc 200 3.385 ms - -
POST /rpc 200 7.714 ms - 317
POST /rpc 200 2.889 ms - 581
GET /stream?access-key=[         ACCESS KEY         ] 200 11.112 ms - -
^C
nate@nates-server:~$

[shesek]

Can you check the browser developer console (Ctrl-Shift-I) and see if there are any errors there?

If you're seeing t.amount_msat is undefined or Not a proper lightning payment request, then it was recently fixed and will shortly be released in v0.2.16.

Would be great if you could confirm if its that or something else. :) Thanks!

[shesek]

I released v0.2.16, can you check if that fixes your issue?

[NateNate60]

I will go install v0.2.16 and see if the issue is fixed and update again.

[NateNate60]

It appears to still be happening

[shesek]

Can you try doing a hard refresh with Ctrl-Shift-R and see if that changes anything? Your browser might still have the v0.2.15 assets cached.

[NateNate60]

This works, but my Android phone appears to still be having this problem, even after a re-install from Google Play. I solved this by manually installing through the APK file provided in this repository's Releases, and it seems to work now. What that probably means is that the updated package has not been pushed to the Play Store yet, or the update is not yet live. I also had to manually re-install it on my Windows PC.

So for those stumbling on this thread in the future, the solution is to re-install everything (NOT from Google Play) and force-reload your browsers.

[shesek]

Which version do you have installed from Google Play? I published v0.2.16 there, but it takes a little while to get fully rolled out.

[NateNate60]

I sideloaded 0.2.16 from the Releases tab of this repo. I didn't wait for Google Play to push the update from 0.2.15 to 0.2.16