Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Unable to create buy intent
Forum Updated to NodeBB v4.3 + New Features

Unable to create buy intent

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
18 Posts 3 Posters 3.9k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    PSI_lbc
    wrote on last edited by
    #2

    The strange thing about this is that the purchase of in-app managed products used to work in my app. When it was a paid app.

    I the changed the app to from $3 to "FREE"..and changed the cost of the in-app-managed products.

    Now it does not work.

    Is this a Google Play thing or a bug in the Qt Purchasing API?

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #3

      Hi,

      I'd recommend bringing this question on the interest mailing list. You'll find there QtPurchasing's developers/maintainers. This forum is more user oriented.

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      P 1 Reply Last reply
      0
      • SGaistS SGaist

        Hi,

        I'd recommend bringing this question on the interest mailing list. You'll find there QtPurchasing's developers/maintainers. This forum is more user oriented.

        P Offline
        P Offline
        PSI_lbc
        wrote on last edited by
        #4

        @SGaist
        Thx. I must be a dummy. I can't figure out how to search the interest list.

        1 Reply Last reply
        0
        • P Offline
          P Offline
          PSI_lbc
          wrote on last edited by
          #5

          Here is output from the Google Play Store instantiation..

          W/ContextImpl(15516): Implicit intents with startService are not safe: Intent { act=com.android.vending.billing.InAppBillingService.BIND } android.content.ContextWrapper.bindService:517 com.digia.qt5.android.purchasing.QtInAppPurchase.initializeConnection:118 dalvik.system.NativeStart.run:-2
          W/System.err(15516): org.json.JSONException: No value for orderId
          W/System.err(15516): at org.json.JSONObject.get(JSONObject.java:355)
          W/System.err(15516): at org.json.JSONObject.getString(JSONObject.java:515)
          W/System.err(15516): at com.digia.qt5.android.purchasing.QtInAppPurchase.queryPurchasedProducts(QtInAppPurchase.java:191)
          W/System.err(15516): at com.digia.qt5.android.purchasing.QtInAppPurchase.access$200(QtInAppPurchase.java:43)
          W/System.err(15516): at com.digia.qt5.android.purchasing.QtInAppPurchase$1$1.run(QtInAppPurchase.java:90)
          W/System.err(15516): at java.lang.Thread.run(Thread.java:841)
          D/Qt (15516): qrc:/AppMain.qml:394 (onCompleted): qml: AppMain:: AppStore::onCompleted: *****************

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #6

            To search or to post on it ? To post a question you should first subscribe to the list.

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0
            • M Offline
              M Offline
              mvuori
              wrote on last edited by
              #7

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

              1 Reply Last reply
              0
              • SGaistS Offline
                SGaistS Offline
                SGaist
                Lifetime Qt Champion
                wrote on last edited by
                #8

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

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                P 1 Reply Last reply
                0
                • SGaistS SGaist

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

                  P Offline
                  P Offline
                  PSI_lbc
                  wrote on last edited by
                  #9

                  @SGaist

                  Thx.. Searching now.

                  P 1 Reply Last reply
                  0
                  • P PSI_lbc

                    @SGaist

                    Thx.. Searching now.

                    P Offline
                    P Offline
                    PSI_lbc
                    wrote on last edited by
                    #10

                    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)

                    P 1 Reply Last reply
                    0
                    • P 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)

                      P Offline
                      P Offline
                      PSI_lbc
                      wrote on last edited by PSI_lbc
                      #11

                      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...

                      1 Reply Last reply
                      0
                      • SGaistS Offline
                        SGaistS Offline
                        SGaist
                        Lifetime Qt Champion
                        wrote on last edited by
                        #12

                        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.

                        Interested in AI ? www.idiap.ch
                        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                        P 1 Reply Last reply
                        0
                        • SGaistS 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.

                          P Offline
                          P Offline
                          PSI_lbc
                          wrote on last edited by
                          #13

                          @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.

                          P 1 Reply Last reply
                          0
                          • SGaistS Offline
                            SGaistS Offline
                            SGaist
                            Lifetime Qt Champion
                            wrote on last edited by
                            #14

                            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 :)

                            Interested in AI ? www.idiap.ch
                            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                            1 Reply Last reply
                            0
                            • P 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.

                              P Offline
                              P Offline
                              PSI_lbc
                              wrote on last edited by PSI_lbc
                              #15
                              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.

                              1 Reply Last reply
                              0
                              • SGaistS Offline
                                SGaistS Offline
                                SGaist
                                Lifetime Qt Champion
                                wrote on last edited by
                                #16

                                Most likely yes.

                                Thanks for the link !

                                Interested in AI ? www.idiap.ch
                                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                                1 Reply Last reply
                                0
                                • P Offline
                                  P Offline
                                  PSI_lbc
                                  wrote on last edited by
                                  #17

                                  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.

                                  1 Reply Last reply
                                  0
                                  • SGaistS Offline
                                    SGaistS Offline
                                    SGaist
                                    Lifetime Qt Champion
                                    wrote on last edited by
                                    #18

                                    Good :)

                                    Thanks for the followup

                                    Interested in AI ? www.idiap.ch
                                    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                                    1 Reply Last reply
                                    0

                                    • Login

                                    • Login or register to search.
                                    • First post
                                      Last post
                                    0
                                    • Categories
                                    • Recent
                                    • Tags
                                    • Popular
                                    • Users
                                    • Groups
                                    • Search
                                    • Get Qt Extensions
                                    • Unsolved