bundle format unrecognized, invalid, or unsuitable

后端 未结 6 2324
野性不改
野性不改 2021-02-19 22:11

Xcode:8.1

language:Objective-C

I can run the project on my iPhone, but can\'t run on the simulator.

I tried:

1)deleting all data of the

相关标签:
6条回答
  • 2021-02-19 22:29

    This is not the solution for topic-starter, however in my case I've recieved this error about 'bundle format unrecognized, invalid, or unsuitable' during CocoaPods post-build embed frameworks action on attempt to sign any framework. More of that, the issue was reproduced only when running build on Jenkins.

    The reason was really stupid. Jenkins was using the custom output directory, which did include space char in the middle. The CP post-build generated script doesn't handle paths with spaces properly, so the codesign tool actually was not fed with the correct path to framework.

    SOLUTION: double check you have no spaces in your path :)

    Hope this will help somebody to save some time :)

    0 讨论(0)
  • 2021-02-19 22:31

    I was seeing a similar issue with CocoaPods 0.39.0, in the end I solved it by modifying my pod spec:

    Commenting out

    s.resource_bundles = {
      'DHSErdi' => ['Pod/Assets/*.png']
    }
    

    And adding this

    s.resources = ['Pod/Assets/*.xib', 'Pod/Assets/*.png', 'Pod/Assets/*.jpg', 'Pod/Assets/*.html', 'Pod/Assets/javascript/dist/**/*.js','Pod/Assets/javascript/src/**/*.html']
    
    0 讨论(0)
  • 2021-02-19 22:37

    I had the same problem. I did the following steps, and it sovled. Select Pods in the navigation --> TARGETS --> your FDTakeResources --> Signing(Enable Development Signing) --> Identity(Choose Info.plist File). Then I can run it on my simulator.

    0 讨论(0)
  • 2021-02-19 22:47

    Are you using CocoaPods? Updating CocoaPods itself + then all the pods worked from me.

    Note: this is right after the Xcode autoupdate today.

    0 讨论(0)
  • 2021-02-19 22:48

    One other thing to watch out for is if something is getting put into the output folder that should not be there or removed from that output folder. For example, in our old builds we put our documentation into the output folder that now gets signed. Now we can't do that, we have to put it alongside the signed output folder. Moving that out solved the unrecognized bundle format error. Hope this helps someone.

    0 讨论(0)
  • 2021-02-19 22:50

    For those for whom updating Cocoapods or reverting Xcode to 8.0 is not an option, here is a solution that worked for me:

    1. Right click on Pods in the Project Navigator
    2. Click New File...
    3. Select Property List
    4. Save the file under the name Pods-Info.plist (for example) and leave it empty
    5. Select Pods in the Project Navigator
    6. Select the Pods project, then Build Settings
    7. Search for Info.plist
    8. Set the value of Info.plist File to Pods-Info.plist
    0 讨论(0)
提交回复
热议问题