Reported by: Talha
Description
When opening the QR code scanner to invite/bind a new contact, previously added social bindings are unexpectedly showing up as a Social Connection Request modal. This request popup should not appear at this stage — it seems like a stale or duplicate binding request is being surfaced when the user navigates to the QR scan screen.
Steps to Reproduce
- Open the MetaState app and navigate to the home screen.
- Tap the INVITE button on the Social Binding section (or the SCAN button).
- Observe that a "Social Connection Request" modal appears immediately — showing a previously added contact (e.g. "Talha 5 wants to establish a social connection with you") before the QR code is even scanned.
- The "Your QR-Code" screen also displays, showing your QR code for scanning.
Expected Behavior
Opening the QR code screen should simply display the user's QR code for a new binding. No previously processed or already-accepted Social Connection Request should surface at this point.
Supporting Media



Device
- Device: Mobile
- OS: iOS / Android
- Feature Area: Social Binding — QR Code Scanner
Additional Context
The user already has 7 social binding contacts. It appears that a pending or previously received binding request is not being cleared/dismissed after acceptance, causing it to re-surface when navigating to the QR scan screen.
Description
When opening the QR code scanner to invite/bind a new contact, previously added social bindings are unexpectedly showing up as a Social Connection Request modal. This request popup should not appear at this stage — it seems like a stale or duplicate binding request is being surfaced when the user navigates to the QR scan screen.
Steps to Reproduce
Expected Behavior
Opening the QR code screen should simply display the user's QR code for a new binding. No previously processed or already-accepted Social Connection Request should surface at this point.
Supporting Media
Device
Additional Context
The user already has 7 social binding contacts. It appears that a pending or previously received binding request is not being cleared/dismissed after acceptance, causing it to re-surface when navigating to the QR scan screen.