-
Notifications
You must be signed in to change notification settings - Fork 986
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
App shows 'buy' for stickerpack user owns when pressing on sticker in chat (Infura - related?) #9886
Comments
This did not happen to me. It worked as expected on my end. I had purchased the sticker pack on a nightly build a few weeks ago and it restored great on the V1 RC. |
Other v1 issues that may be related to Infura:
|
I'm not sure if it's infura or not (for me there is nothing like Infura-related) Preconditions:
Reproduction:
However:
|
It's okay for me on iOS. On RC4 iOS, I have the Install button when I click on a Tozemoon sticker in chat. |
On RC4 I have this issue in both iOS (13.3) and Androids One note: If you open sticker market place from message input at least once then all fine when opening tozemoon sticker pack from chat, but it's until you re-login. |
…icker in chat Signed-off-by: Andrey Shovkoplyas <[email protected]>
Bug Report
Problem
App requires to buy stickerpack that was bought previously from "Tozemoon" sticker pack opened by tap on Tozemoon's sticker from inside chat view.
NOTE: It's all fine when I open sticker market place from message input sticker icon. And also if I done that - there is no issue. Until I re-login to account.
So for me now, with RC4 - there are no problems when I open Tozemoon sticker pack from message input sticker icon
But issue is when I logged in to account (with bought but not installed Tozemoon) -> open chat with Tozemoon sticker -> tap tozemoon sticker from chat view
Expected behavior
can install stickerpack
Actual behavior
Reproduction
Actual result: No Install button available but 20 SNT instead
Additional Information
Logs
stick-log.log
The text was updated successfully, but these errors were encountered: