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. [iOS] Upload to App Store : embeded framework problem

[iOS] Upload to App Store : embeded framework problem

Scheduled Pinned Locked Moved Solved Mobile and Embedded
2 Posts 1 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.
  • V Offline
    V Offline
    Vi67
    wrote on last edited by
    #1

    Hello,

    It's not the first time that I'm using Qt with other external frameworks. And usually it works fine with the qmake line :

    LIBS += -F/PATH/TO/YOUR/FRAMEWORKS/DIR -framework Name1 - framework Name2
    

    It was working even when I uploaded to App Store.

    But today, I'm working with aws-sdk-ios frameworks (from Amazon).

    This framework need to be "embeded" in xcode project. Then I followed those 4 steps.
    It's also possible to embed them easier with this script (but I don't use it, to be sure that my bug don't come from that).

    It's works fine when I test the application in iOS Simulator. But When I try to send the .ipa to App Store (with Organizer or Application Loader), I get this error :
    No suitable application records were found. Verify your bundle identifier 'com.amazonaws.sdk.ios.AWSCognitoIdentityProviderASF' is correct.

    I tried many things from this great summary. But nothing helps.

    This problem doesn't look very common. I think the problem comes from xcode configuration made by Qt.

    There are screenshots from the last steps :

    0_1518623687930_photo_2018-02-14_14-32-44.jpg

    Then I click to upload, and...

    0_1518623724785_photo_2018-02-14_14-34-38.jpg

    Anyone have any thoughts on this ?
    Thanks

    1 Reply Last reply
    0
    • V Offline
      V Offline
      Vi67
      wrote on last edited by
      #2

      Finally I found the fix. It was because of something that has nothing to do with this topic. I mechanically edited a key in Info.plist ... I'll never touch again CFBundleExecutable :D

      <key>CFBundleExecutable</key>
      <string>$(EXECUTABLE_NAME)</string>
      
      1 Reply Last reply
      1

      • Login

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