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. In app purchases on iOS / Qt 5.13.0 - provisioning problem

In app purchases on iOS / Qt 5.13.0 - provisioning problem

Scheduled Pinned Locked Moved Solved Mobile and Embedded
7 Posts 3 Posters 706 Views
  • 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.
  • SupernaurisS Offline
    SupernaurisS Offline
    Supernauris
    wrote on last edited by
    #1

    I am trying to set up in-app purchases on iOS and test it on a device, using Qt 5.13.0, following the instructions in https://doc.qt.io/qt-5/qtpurchasing-appstore.html#

    As the application starts I call QInAppStore::registerProduct two times (= once per product). As I see it, the phone should then ask me to log into the app store, so that the registerProduct calls can finish. The app store interface does not come up. Instead, after 20-25 seconds the QInAppStore emits productUnknown, for both of the products.

    My suspicion is that there is something wrong with my provisioning setup. I am using QtCreator, with Automatic signing checked in the project iOS preferences. I have also tried to use the provisioning profile I created for the purpose (instead of automatic signing), but this causes the build to fail with:

    Check dependencies
    Code Signing Error: Provisioning profile "[REDACTED]" doesn't include signing certificate "iPhone Developer: [REDACTED]".
    Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.4'
    Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 12.4'
    

    Any ideas on how to move forward?

    PS. Originally the productUnknown signal was emitted in about 3 seconds, but then I adjusted the apple bundle ids and product ids.

    1 Reply Last reply
    0
    • SupernaurisS Offline
      SupernaurisS Offline
      Supernauris
      wrote on last edited by
      #2

      I guess this could also be related to having something wrong in the shop/app/product setup. Does anybody know about a way to get more debug information about the issue?

      There are about 30 things that could go wrong, getting a single productUnknown signal does not give direction about where the problem could be.

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

        Hi and welcome to devnet,

        The QtPurchase module being pretty new, you will likely get more in depth answers by bringing your question on the interest mailing list. You'll find there QtPurchase's developers/maintainers.

        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
        • SupernaurisS Offline
          SupernaurisS Offline
          Supernauris
          wrote on last edited by
          #4

          I watched this video https://www.youtube.com/watch?v=YHGIij_stpk and found a few more things, which are not mentioned in link above. After taking those into account my app gets the productRegistered signal from QInAppStore.

          Here are some notes of the extra steps I took:

          1. Fill in all the tax, agreement etc. forms in the App store connect. This also changed some of the forms in my App store "new feature" dialogs.
          2. Turn on the "in app purchase entitlement" in XCode
          3. Updated the product ids to start with the exact application bundle id. If the bundle id is "com.abcde.MyApp", then the product ids have to be "com.abcde.MyApp.buy1" etc. Using "com.abcde.myapp.buy1" fails.

          I am not 100% certain if all of these are mandatory, since things started to work only after doing the last step.

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

            Glad you found out and thanks for sharing !

            Would you consider contributing an update to the documentation so it'll help other users of the module ?

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

            SupernaurisS 1 Reply Last reply
            0
            • SGaistS SGaist

              Glad you found out and thanks for sharing !

              Would you consider contributing an update to the documentation so it'll help other users of the module ?

              SupernaurisS Offline
              SupernaurisS Offline
              Supernauris
              wrote on last edited by
              #6

              @sgaist Maybe at some point. Also, note that I am not 100% sure of what the exact instructions should be - some parts are certainly necessary, while it others might not be.

              1 Reply Last reply
              0
              • Z Offline
                Z Offline
                ZoeyC
                wrote on last edited by
                #7
                This post is deleted!
                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