OverviewFilesCommitsIssuesDocsReleasesPeers

hyper-wallet-desktop commits / 046b8c7

Disable native notifications after transaction to prevent UI hang
Native libnotify was causing "Failed to connect to proxy" errors that made the UI unresponsive after sending transactions. The notification system was timing out and blocking the renderer. The success toast message provides sufficient user feedback. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
046b8c76f8c521db53edb37948d6aeea7a26bf15
by plankatron <fleeky@gmail.com> · 2026-01-29T17:26:14.000Z

Changed files (1) +11 -10

desktop/wallet.js +11 -10
……@@ -2917,16 +2917,17 @@ async function executeSend() {
29172917 showSuccess(`Transaction sent! Hash: ${data.hash.substring(0, 16)}...`)
29182918 usedMaxAmount = false // Reset flag after successful send
29192919
2920 // Show native notification (don't let this crash the app)
2921 try {
2922 showNotification(
2923 'Transaction Sent',
2924 `${amount} ${currentSendChain.toUpperCase()} sent successfully`,
2925 'success'
2926 )
2927 } catch (notifErr) {
2928 console.log('Notification failed (non-critical):', notifErr.message)
2929 }
2920 // DISABLED: Native notifications causing UI hang (libnotify proxy timeout)
2921 // The success toast message above provides sufficient feedback
2922 // try {
2923 // showNotification(
2924 // 'Transaction Sent',
2925 // `${amount} ${currentSendChain.toUpperCase()} sent successfully`,
2926 // 'success'
2927 // )
2928 // } catch (notifErr) {
2929 // console.log('Notification failed (non-critical):', notifErr.message)
2930 // }
29302931
29312932 // Refresh balances and transactions
29322933 setTimeout(() => {