-
Notifications
You must be signed in to change notification settings - Fork 59
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
Purchase option is broken #1594
Comments
@dev-inside please update Grayjay to the latest version (v268) and see if the error occurs again. |
@Zvonimir-FUTO |
Will be fixed in the next release. You can also buy a license from our website: https://pay.futo.org/api/PaymentPortal |
This has been fixed in v276. |
Got the license but won't work on desktop or even the android version Here is the end of my log file after it just exit by it self: i StateSubscriptions:Channel Matthew Cox | Inside True Crime failed, substituting with cache --- End of inner exception stack trace --- --- End of inner exception stack trace --- |
I have uploaded from the android device the subscription list that seems to have an issue. Let me know what I need to give additionally |
@ClientIco These don't seem related to license. Could you open new issues for these at the following links? https://github.com/futo-org/Grayjay.Desktop/issues/ - for Desktop issue Also please provide more information so it is easier to troubleshoot and find where the issue is. |
What happened?
Hey,
first of all, I love your work and I wanted to share my appreciation by purchasing a license - like I did with the great FUTO-Keyboard <3
Anyway, when I try to purchase a license, I get the following error
GERMAN Translation:

"The required payment data cannot be retrieved."
Also the "0.0.0.0:43" in the end look like a misconfiguration of some sort.
Grayjay Version
268
What plugins are you seeing the problem on?
Other
Plugin Version
No response
When do you experience the issue?
Relevant log output
No response
The text was updated successfully, but these errors were encountered: