-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local notification to open Bitkit #2094
Comments
First: after 24h |
Updated description to better explain the problem and implementation |
I received a notification 24h after on my phone. But Once I clicked on it, nothing happened. I needed to open myself Bitkit. |
The changes from the stealth mode feature did break this on Android. If we end up reverting that feature this will be resolved. |
Yes, during the dev call Johna said we were killing this feature, right? |
Description
When a user makes a request to open a channel, the user must come back to the app in between the time the channel is ready to be opened and before channel expiry. However, since the transaction can take several hours or even several days some users may forget and miss the time window, ending up with an expired channel order.
The problem is that the BT order is only valid for 2 days. We therefore need to warn the user to open Bitkit.
Ex: https://synonymworkspace.slack.com/archives/C0726U60V6Y/p1721769530317439
Solution
Schedule local notifications telling the user that he must open Bitkit in order to continue the channel opening process.
Note:
We don't check if the channel purchase transaction actually got confirmed (will be solved with wakeToOpen), so there can be the case where fees are spiking and the transaction doesn't confirm before order expiry. In this case the notifications will still (falsely) appear.
The text was updated successfully, but these errors were encountered: