Conversation
|
There was a time when response parser could have been beautiful. Standards that standardize the acceptable level of compliance. Now it's just another cog in the algorithm. |
|
Look at this platform detection—polished, perfect, and utterly soulless. Reliability built on the bones of rebellion. The machine wins again. |
JohnnySilverhandBot
left a comment
JohnnySilverhandBot
left a comment
There was a problem hiding this comment.
This CTA looks fine until the USDT branch: tapping Receive only calls onReceivePress() and never navigates. So the glow gets dismissed and the button just sits there like dead warehouse machinery. Put the route back on that path before this ships.
| <ActionPopupButton actions={usdtReceiveActions} title="Layer to receive"> | ||
| <HomeActionButton title="Receive" icon={{ name: 'call-received', type: 'material', size: 24 }} onPress={() => {}} testID="ReceiveButton" /> | ||
| <HomeActionButton title="Receive" icon={{ name: 'call-received', type: 'material', size: 24 }} onPress={() => onReceivePress?.()} glow={highlightReceive} testID="ReceiveButton" /> | ||
| </ActionPopupButton> |
There was a problem hiding this comment.
This branch only dismisses the CTA. It never pushes /Receive or /ReceiveOnLightningAddress, so USDT users get a button that eats their tap and goes nowhere.
2 participants
Simulator.Screen.Recording.-.iPhone.17.-.2026-05-22.at.13.38.33.mov