You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening a Lightning invoice payment link from a browser on iOS does not trigger the Bitkit payment flow when Bitkit opens locked with either Face ID or PIN enabled. The issue was reproduced from both Safari and Chrome on iOS.
Manual invoice paste inside Bitkit still works, so the invoice itself appears valid. The same browser link also works when neither Face ID nor PIN app lock is enabled. The failure is specific to opening the lightning: payment link from the browser/deep-link path while app lock is enabled.
Expected behavior
When the user taps a lightning:<bolt11 invoice> link in Safari or Chrome, Bitkit should open, complete Face ID or PIN unlock if required, and continue into the payment flow for the invoice without requiring manual invoice paste.
Steps to Reproduce
Install/open Bitkit for iOS and enable Face ID or PIN app lock.
Ensure Bitkit is locked or backgrounded long enough to require Face ID or PIN unlock on next open.
Paste a valid BOLT11 Lightning invoice into the page.
Tap Open lightning link.
Complete Face ID or PIN unlock if prompted.
Observe that Bitkit does not continue to the payment flow for the invoice.
Paste the same invoice manually inside Bitkit and observe that manual paste works.
Logs / Screenshots / Recordings
ScreenRecording_05-25-2026.17-36-38_1.MP4
Bitkit Version
2.2.1
Device / OS
iPhone 13
Reproducibility
Always
Additional context
This may be related to how Bitkit stores or resumes incoming deep-link payloads when the app starts into a locked state. The browser link test page is available at https://synonymdev.github.io/bitkit-e2e-tests/ and generates lightning: links from pasted BOLT11 invoices.
Control case: the same browser lightning: link opens the payment flow correctly when neither Face ID nor PIN app lock is enabled.
What happened?
Opening a Lightning invoice payment link from a browser on iOS does not trigger the Bitkit payment flow when Bitkit opens locked with either Face ID or PIN enabled. The issue was reproduced from both Safari and Chrome on iOS.
Manual invoice paste inside Bitkit still works, so the invoice itself appears valid. The same browser link also works when neither Face ID nor PIN app lock is enabled. The failure is specific to opening the
lightning:payment link from the browser/deep-link path while app lock is enabled.Expected behavior
When the user taps a
lightning:<bolt11 invoice>link in Safari or Chrome, Bitkit should open, complete Face ID or PIN unlock if required, and continue into the payment flow for the invoice without requiring manual invoice paste.Steps to Reproduce
Logs / Screenshots / Recordings
ScreenRecording_05-25-2026.17-36-38_1.MP4
Bitkit Version
2.2.1
Device / OS
iPhone 13
Reproducibility
Always
Additional context
This may be related to how Bitkit stores or resumes incoming deep-link payloads when the app starts into a locked state. The browser link test page is available at https://synonymdev.github.io/bitkit-e2e-tests/ and generates
lightning:links from pasted BOLT11 invoices.Control case: the same browser
lightning:link opens the payment flow correctly when neither Face ID nor PIN app lock is enabled.