-
Notifications
You must be signed in to change notification settings - Fork 460
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
URI from encode URL does not work most of the time when clicked on Phantom and Solflare #241
Comments
خوب به نظر شما چه باید بکنم
در تاریخ چهارشنبه ۲۸ اوت ۲۰۲۴، ۱۲:۱۴ Suraksha Motilal <
***@***.***> نوشت:
… The URI does not work properly where it fails to open the payment screen
at times, and fails constantly on specific phones.
More info:
I have created a URI from Solana pay's encode URL function which returns a
URL in this format:
*solana:WALLETADDRESS?amount=0.0001&reference=WALLETADDRESS&label=label&message=message&memo=memo*
I removed the wallet address for privacy reasons.
Using 2 different phones:
Samsung S22- it opens up with payment screen in phantom sometimes and
fails other times, in which it only shows the home screen. Works all the
time in Solflare.
IMG_20240828_102817.jpg (view on web)
<https://github.com/user-attachments/assets/5bfc9fb1-fd65-4ade-affc-28a350bbbeaa>
IMG_20240828_102722.jpg (view on web)
<https://github.com/user-attachments/assets/0d94c5d2-d9c7-4ecb-baa6-a1633742138f>
Xiaomi Poco X3 Pro- it does not open at all in Phantom (home screen issue
where payment screen does not show up but stays on home page). Solflare
returns this error:
IMG_20240828_102734.jpg (view on web)
<https://github.com/user-attachments/assets/9cc78548-0464-4b73-92f3-b5d42f4bf016>
There seems to be an issue where this URI is not supported by all phones.
Not only that, the unreliability of this link is an issue.
The qr code, when scanned by the supported wallet apps, always works and
shows the payment screen.
—
Reply to this email directly, view it on GitHub
<#241>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXBABQSQDEL6JZOHCH62BT3ZTWEWLAVCNFSM6AAAAABNHY2ERSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4TCNBWGA4DAOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I want the payment screen to pop up in my desired wallet app when I click that link. It does not pop up the way it is intended to. |
خوب من چکار باید بکنم
در تاریخ چهارشنبه ۲۸ اوت ۲۰۲۴، ۱۲:۴۲ Suraksha Motilal <
***@***.***> نوشت:
… I want the payment screen to pop up in my desired wallet app when I click
that link. It does not pop up the way it is intended to.
Yet it works perfectly if I scan the qr code. Clicking the raw link itself
does not do the same.
—
Reply to this email directly, view it on GitHub
<#241 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXBABQQIPMFOE2QRN6MABXDZTWH6VAVCNFSM6AAAAABNHY2ERSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJUG43TCNRQGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The URI does not work properly where it fails to open the payment screen at times, and fails constantly on specific phones.
More info:
I have created a URI from Solana pay's encode URL function which returns a URL in this format:
solana:WALLETADDRESS?amount=0.0001&reference=WALLETADDRESS&label=label&message=message&memo=memo
I removed the wallet address for privacy reasons.
Using 2 different phones:
Samsung S22- it opens up with payment screen in phantom sometimes and fails other times, in which it only shows the home screen. Works all the time in Solflare.
Xiaomi Poco X3 Pro- it does not open at all in Phantom (home screen issue where payment screen does not show up but stays on home page). Solflare returns this error:
There seems to be an issue where this URI is not supported by all phones. Not only that, the unreliability of this link is an issue.
The qr code, when scanned by the supported wallet apps, always works and shows the payment screen.
The text was updated successfully, but these errors were encountered: