Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting this fail during build time ever since I updated to new xcode. #136

Closed
farhan-syed opened this issue Nov 2, 2016 · 13 comments
Closed
Labels

Comments

@farhan-syed
Copy link

farhan-syed commented Nov 2, 2016

getting this error when running app, it fails during buildtime.

/Users/USER/Library/Developer/Xcode/DerivedData/APPNAME-cqrknuczxqiiuxcvjlupnrmizjox/Build/Products/Debug-iphonesimulator/TOCropViewControllerBundle.bundle: bundle format unrecognized, invalid, or unsuitable
Command /usr/bin/codesign failed with exit code 1

Is it because there is a bundle within the cocoapods 'pods' folder?

CodeSign /Users/USER/Library/Developer/Xcode/DerivedData/APPNAME-cqrknuczxqiiuxcvjlupnrmizjox/Build/Products/Debug-iphonesimulator/TOCropViewControllerBundle.bundle
    cd /Users/USER/APPNAME/Pods
    export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

Signing Identity:     "-"

    /usr/bin/codesign --force --sign - --timestamp=none /Users/USER/Library/Developer/Xcode/DerivedData/APPNAME-cqrknuczxqiiuxcvjlupnrmizjox/Build/Products/Debug-iphonesimulator/TOCropViewControllerBundle.bundle

Also noticed this in the Pods Target
screen shot 2016-11-02 at 10 36 28 am

I'm up to date with 2.0.11

@TimOliver
Copy link
Owner

Someone else just reported a similar issue, but they were able to resolve it themselves: #135

I use this library in one of my own apps and I'm not having any trouble with integrating it via CocoaPods, so there's not a lot I can do to help, sorry.

Make sure your CocoaPods is up to date, you've run pod update, and if worse comes to worse, de-integrate and run pod install again. :)

@farhan-syed
Copy link
Author

@TimOliver how should i go about deintegrating? pod update didnt work for me.

@farhan-syed
Copy link
Author

@TimOliver I de-integrated it then i did a pod install and still doesn't work.

@farhan-syed
Copy link
Author

I noticed in my project I dont have the info.plist like there is shown in the TOCropViewController on Github.

@TimOliver
Copy link
Owner

Hmm, I'm getting the feeling this is a CocoaPods specific issue, and not one unique to this library.

I Googled that error message and discovered that apparently clearing Xcode's Derived Data folder will fix it.

http://stackoverflow.com/questions/7339600/object-file-format-unrecognized-invalid-or-unsuitable-xcode-error/33108691#33108691

@farhan-syed
Copy link
Author

i deleted the Derived Data folder, and the initial error is gone and now this error is appearing:

No visible @interface for 'TOCropViewController' declares the selector 'setAspectRatioLocked:'

@TimOliver
Copy link
Owner

Cool! Sounds like that fixed the issue. :)

That's because it doesn't. The property was renamed to 'aspectRatioLockEnabled'. You might need to go through and review your implementation code since the API may have changed a bit.

In any case, the crash is gone, so I think this issue is resolved. :)

@farhan-syed
Copy link
Author

@TimOliver Ohh didn't realize, its because I'm on the newer version.

Appreciate your advice and time!

@farhan-syed
Copy link
Author

farhan-syed commented Nov 3, 2016

@TimOliver alright so now after i looked over the API and I changed the necessary errors.

I am back to square one. Same error i had in the beginning.

`/Users/USER/Library/Developer/Xcode/DerivedData/APPNAME-cqrknuczxqiiuxcvjlupnrmizjox/Build/Products/Debug-iphonesimulator/TOCropViewControllerBundle.bundle: bundle format unrecognized, invalid, or unsuitable
Command /usr/bin/codesign failed with exit code 1`

`CodeSign /Users/USER/Library/Developer/Xcode/DerivedData/APPNAME-cqrknuczxqiiuxcvjlupnrmizjox/Build/Products/Debug-iphonesimulator/TOCropViewControllerBundle.bundle
    cd /Users/USER/APPNAME/Pods
    export CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

Signing Identity:     "-"

    /usr/bin/codesign --force --sign - --timestamp=none /Users/USER/Library/Developer/Xcode/DerivedData/APPNAME-cqrknuczxqiiuxcvjlupnrmizjox/Build/Products/Debug-iphonesimulator/TOCropViewControllerBundle.bundle`

@farhan-syed
Copy link
Author

@TimOliver So what I ended up doing, and I want to make sure this is okay with you is i ended up deleting the
TOCropViewController-ToCropViewControllerBundle that was located under Pods target
and now my application builds successfully

screen shot 2016-11-02 at 10 36 28 am

@TimOliver
Copy link
Owner

Hmmm..... this is really weird. This seems to be entirely an issue with the way CocoaPods is installing the library. I can't replicate it on my own machine so there's not much I can do.

If you're actually able to reliably reproduce this issue, it might be best to report this as an issue to the CocoaPods repo.

@farhan-syed
Copy link
Author

Is it okay that I deleted the bundle as I showed above? Just want to make
sure.

On Thursday, November 3, 2016, Tim Oliver notifications@github.com wrote:

Hmmm..... this is really weird. This seems to be entirely an issue with
the way CocoaPods is installing the library. I can't replicate it on my own
machine so there's not much I can do.

If you're actually able to reliably reproduce this issue, it might be best
to report this as an issue to the CocoaPods repo
https://github.com/CocoaPods/CocoaPods.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#136 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJI091CifqQv4PwGx3lMoDIcYVpB7arGks5q6chJgaJpZM4KniU_
.

Farhan Syed
Founder of BrandSpace

@TimOliver
Copy link
Owner

Oh yeah, it's fine! Of course! (You'll need to test to make sure it actually still works though)

The only downside to that is if you do another CocoaPods update, the problem will come back again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants