Oddbean new post about login | logout Humm.. I know mine has been slow for sure. I will run some tests on this.
Same problem for me with the latest versions, I use Minibits 0.1.8 and Amethyst 0.89.10 both from Github.
With disabled VPN for Minibits and Amethyst + diasabled accu optimization and disabled stop app activity when not used. It works for me😅
When Minibits is in killed state, in my tests the zap is paid reliably by ecash, however android suppresses or delays the nwc response sending - but not sure how Amethyst or others handle this case. Still, zap receipt is published from the server, so not missing.
But I don't see any transactions leaving minibits... And even after amethyst restart, no zaps are shown.
Do you have push notifications enabled and working?
I do receive notifications from minibits when opening the app and receiving, ntfy is installed
If you see them only when wallet is in active use, those are local ones, trigerred by the app itself. Check if you see the device token under the push notification switch in the Settings. https://image.nostr.build/3fb0945edb7e0a37a1950150df6b4962e96f5650e9f2097f0e1951cbd0d765d1.jpg For NWC to work when Minibits is killed or backgrounded, you'd need to be able to recieve them from the server, through firebase messaging - the same way push are delivered on incoming zaps no matter the state Minibits is in. Most android devices are supported, but there are some that don't: i.e. if you use a device that has no Google Play services installed (some chinese brands or privacy operating systems such as Graphene and similar). Those can not obtain the so called device token to which the messages are addressed.
okay so no NWC for us Graphene users :,( Not so cypherpunk if dependend on Google play services imho
For cypherpunks there is of course a fallback - if notification permission is not granted, NWC messages keep going over the standard websocket subscription. Now it is upon the real ones to kick their OS not to close it when the app is backgrounded and then open source that for all others.
nostr:nprofile1qqsvzkj6vkvxu745zdx7uw4c2f2d5hzafvzw0z60zmyzsdce9564rpgpz9mhxue69uhkummnw3ezuamfdejj7mtxgrd any thoughts on this?
You can install ntfy and rely on a non-google server, even self host it.
Thank you for headsup, checked ntfy, nice project. It would be unfortunately unusable for NWC use case, as the wallet do not have access to the received notifications. In case of NWC my server subscribes to encrypted NWC commands published to minibits relay, reencrypts them with own keys and routes them to the right device based on event recepient tag. They are not shown to the user, just used as data carrier passing the commands from relays to the device.
In minibits settings push notification is enabled, but there is no token specified. When I click the setting, it just forwards me to the os settings, but I cannot specify a new token for ntfy...
Token is obtained automatically on granting the permission and refrehed on wallet start - user is not involved in it. If it fails to do so, it means that the device has no Play services installed / available. I've released yesterday a small fix that will fallback to websocket nwc connection in that case (permission granted and device token missing). Unfortunately this is really a "demo" solution as it will work only when app is in the foreground (means zaps are sent from app on other device / pc).
Correct, no GPS installed, even when I manually dis/enable notifications it doesn't work. Would be great to get it to work with ntfy only. Thanks! 🖤
