getting error purchasing item // closed
chazzledazzle10 opened this issue · comments
hey guys please help me out ive been stuck for so long i dont know what to do. so this is my code for the purchase button down
and this is the result from the command line debugger when im using my phone
so i think its not connecting to the android/google api and the response.status code is 1 which i have been trying to figure out what it means?
please someone help
i will also add that in the connected function i have tried queryskudetails and query product details and they both make no differenced what so ever.
Some stuff I noticed:
- are you using 2.0-rc1 of this plugin? the older ones won't work
- do you have all the signals connected?
- in _on_connected, you call your own signal function?
instead, you need to call querySkuDetails() with the same parameters, and remove queryPurchases, it doesn't exist in 2.0
calling it before purchase is required - all of this expects the IAP set up correctly with Google in the dev console and you need (!) to at least once upload a build to it (Testing Track is fine) and run the purchase from it (so, install it from Google and run), so it acknowledges that this iap is active. Just running it locally will not work, at least once you must run in from Google.
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:893202463;
mso-list-template-ids:-1;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->Hey thank you for the advise but I sorted this out. Im currently logged out of Github and cant comment. Sent from Mail for Windows From: NianoTTSent: 18 May 2023 16:33To: godotengine/godot-google-play-billingCc: chazzledazzle10; AuthorSubject: Re: [godotengine/godot-google-play-billing] getting error purchasing item (Issue #40) Some stuff I noticed:are you using 2.0-rc1 of this plugin? the older ones won't workdo you have all the signals connected?in _on_connected, you call your own signal function?instead, you need to call querySkuDetails() with the same parameters, and remove queryPurchases, it doesn't exist in 2.0calling it before purchase is requiredall of this expects the IAP set up correctly with Google in the dev console and you need (!) to at least once upload a build to it (Testing Track is fine) and run the purchase from it (so, install it from Google and run), so it acknowledges that this iap is active. Just running it locally will not work, at least once you must run in from Google.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
Hey thank you for the advise but I sorted this out.
👍
If you got it working you can close the issue as it's not a bug in the plugin then.
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->Hi mate, thank you for getting back. I will mark it as soved soon, just out with the family at the moment. Thanks. Sent from Mail for Windows From: NianoTTSent: 19 May 2023 12:50To: godotengine/godot-google-play-billingCc: chazzledazzle10; AuthorSubject: Re: [godotengine/godot-google-play-billing] getting error purchasing item (Issue #40) Hey thank you for the advise but I sorted this out.👍If you got it working you can close the issue as it's not a bug in the plugin then.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
Hey thank you for the advise but I sorted this out.
👍
If you got it working you can close the issue as it's not a bug in the plugin then.
Hi mate ive just logged back in. i cant see a way to close the thread?
Hey thank you for the advise but I sorted this out.
👍
If you got it working you can close the issue as it's not a bug in the plugin then.Hi mate ive just logged back in. i cant see a way to close the thread?
On Desktop, at the very bottom right next to "Comment" is a "Close Issue" button.