Unable to create buy intent

mvuori

He wrote "search"... One should always search previous discussions before posting a question....

SGaist

@PSI_lbc You can use http://dir.gmane.org/gmane.comp.lib.qt.user to search the archived messages.

PSI_lbc

Thx.. Searching now.

PSI_lbc

Nothing current for the issue I'm seeing.
Update: Reverted to previously known working versions on 2 different apps. Both are exhibiting similar issues.

The app goes through the purchase process of an in-app managed product. The app gets a success signal, but then the transaction is cancelled (by Google?) and the transaction then gets a failed signal. Even though the transaction failed, the in-app product cannot be purchased again. And yes the tranactions are finalized()

Even if the transaction was interrupted, the "success" signal is supposed to be resent when the store/product is created when the app starts up. No signal is sent at store creation by Google on subsequent app starts other than..

W/System.err(21678): org.json.JSONException: No value for orderId
W/System.err(21678): at org.json.JSONObject.get(JSONObject.java:355)
W/System.err(21678): at org.json.JSONObject.getString(JSONObject.java:515)
W/System.err(21678): at com.digia.qt5.android.purchasing.QtInAppPurchase.queryPurchasedProducts(QtInAppPurchase.java:191)
W/System.err(21678): at com.digia.qt5.android.purchasing.QtInAppPurchase.access$200(QtInAppPurchase.java:43)
W/System.err(21678): at com.digia.qt5.android.purchasing.QtInAppPurchase$1$1.run(QtInAppPurchase.java:90)
W/System.err(21678): at java.lang.Thread.run(Thread.java:841)

PSI_lbc

An e-mail that went out to Google Play developers..that I did not get..I do not use gmail. :-(

A guess would be that this affects everyone using the Qt Purchasing API.

So the Purchasing API code that assumes an orderID will exist in a reply from Google, when it does not, probably breaks something causing the Purchasing API to throw an error.

When can a fix be expected in the Qt Purchasing API ?

--begin e-mail--

    Hello Google Play Developer,

    Beginning June 20, 2016, we’ll be making a change to test purchases for one-time in-app purchases (IAPs).

    Previously, test purchases for one-time IAPs generated order IDs. Starting June 20, 2016, one-time IAPs will not generate order IDs and will not appear in the Merchant Center. This behavior already applies to subscription IAPs.

    You can learn more about testing in-app billing in the Android Developers Help Center (which will be updated with the information above on June 20).

    Thanks for supporting Google Play,

    The Google Play Team

--end e-mail--
link to a discussion in Korean regarding the problem...

SGaist

Such an email shouldn't be gmail dependent but it seems you're not the only one not having received it.

In any case, others concerned developers may have not received it yet. I'd recommend taking a look a the bug report system to see if it's something known, if not please consider opening a new report providing all the information you have about it. (that mail, the logs etc.) That will help get this fixed.

PSI_lbc

@SGaist

I could be mistaken, but if I remember correctly, Google forces you to use a gmail account when creating a Developer Console id. I have a gmail account for that purpose only. I never access gmail. Which I assume is why I never got the msg.

I opened a support request through my Qt Account.

SGaist

IIRC, you need a Google Account but it doesn't mean that you need a GMail account for that. In any case, it's a good thing you checked it.

There will likely be a bug report created for that, please post the link here so other people may find it more easily :)

PSI_lbc

QtQTBUG-54518

Qt Purchasing no longer works on Android

https://bugreports.qt.io/browse/QTBUG-54518?jql=project %3D QTBUG AND text ~ purchasing

Probably the same issue.

SGaist

Most likely yes.

Thanks for the link !

PSI_lbc

I've been notified that this is "resolved".

The "patch" involves about 4 lines of code. I assume the fixes are available on Git.

I was told a formal library release downloadable by the MaintenanceTool.app is 1-2 months away.

SGaist

Good :)

Thanks for the followup