when I tried to include RestKit to my project in iOS 7 Platform, I got error <RestKit/RestKit.h> file not found..
I followed this tutorial http://www.raywenderlich.com/13097/intro-to-restkit-tutorial
and I did exactly the same thing, but I used iOS 7 as my base platform..
I tried the example project inside restKit folder, but used iOS 7,
then I got same error...
Is there any compatibility issue in iOS 7?
if yes, can anyone recommend me alternate framework?
after strugling...
i solved it by compiling Restkit in its own project,,, then continue including to my own project
and its work..
The tutorial you followed is really old. You should look at this for a guide on how to install RestKit. Ensure you're using the most recent version (don't start using 0.10 now...). The base RestKit Github page contains a number of examples and the code contains lots of tests that you can look at.
RestKit should basically always be included in your project as a reference to the RestKit project. The current version doesn't have any compatibility issues.
Related
I am struggling with a problem while using Gitlab CI/CD.
I am using for my project two of my external frameworks. The project builds without errors but when running the pipeline I'm getting an error that says
This Copy Files build phase contains a reference to a missing file 'xxxxxx.framework'.
My project looks like bellow
This is en error I'm getting:
When I add framework file not the framework project then CI/CD will pass BUT then I'm getting the error when trying to archive project
Building for iOS, but the linked framework 'xxxxxx.framework' was built for iOS Simulator.
I don't know how to solve those problems to get everything work.
Thanks for any kind of help.
Regards
In case anyone is having this problem and is cloning a git repository that has submodules, be sure include the submodules when cloning.
Most probably what you will need out of these 2 options is to use the x.framework one. The error
Building for iOS, but the linked framework 'xxxxxx.framework' was built for iOS Simulator.
as it says, comes from the fact that the framework is only built for iOS Simulator.
Why is that?
Well, the iOS Simulator runs on x86_64 architecture (as OS X does), while iOS runs on arm architecture. So you'll have to compile the frameworks for both architectures. Fortunately, there is a way to do this, and basically what you need to achieve is to create a fat binary of the framework.
There is a script here from Sundeep Gupta https://gist.github.com/sundeepgupta/3ad9c6106e2cd9f51c68cf9f475191fa which can be used to compile the frameworks for both, iOS Simulator and iOS target architectures. There are also several different resources on the internet which explain what steps you need to make in order to create fat binaries.
I just updated to Xcode 9 last week, and I've been looking for a way to get around this error:
Module compiled with Swift 3.1 cannot be imported in Swift 4.0
Each time a new version of Xcode is released that includes a new version of Swift, I have to wait for the RealmSwift project to be updated in order to build and run my project. I am aware that this has to do with Swift's ABI stability, but I also see others who seem to know how to get around this until a compatible version of Realm comes out. Currently, I am running 2.8.0, which was the current release as of last night. My dependency manager of choice is Carthage, but similar questions usually involve CocoaPods, which does not help me very much.
Can anyone offer some clear instructions for unfamiliar ones like me so I can keep working on my project now and when future versions come out? Thank you.
When using beta versions of Xcode which there are not prebuilt binaries for you need to pass --no-use-binaries to carthage bootstrap so that Carthage builds all of the dependencies from source.
Using xcode 5 with my upgraded iOS 6 to iOS 7 app, I have run into issues with upgrading third party frameworks and adding third party frameworks which 'break' other seemingly unrelated frameworks. For example, I tried to upgrade the Crittercism framework which was already included in my project and it broke my Stackmob framework with the result that the project build failing because it couldn't find the Stackmob framework even though it was in the same location before the Crittercism upgrade. I had to remove the Stackmob framework first, then upgrade Crittercism, then reinstall the Stackmob framework, then the build succeeded. Another example, is when I tried to install the Parse framework. That broke my PushIOManager framework resulting in the project build failing since it was unable to find the PushIOManager framework even though it was in the same location as before I did the Parse installation. This is after doing clean and builds on the project. This does not seem to be happening with the built-in frameworks when I add them to the project. What's weird, is that I tried doing all this on an iOS 6 copy of the app using xcode 4.6 and everything worked fine, no issues whatsoever. I was just wondering if anyone else is running into similarly strange issues with their upgraded iOS 7 app and xcode 5. Or if this is just some weird stuff that's unique to my app.
I have a project that has a dependency on a static library. In Xcode 3.2.3 the project that builds the library is setup as a direct dependency in the target settings so that the library is built whenever the main project is built.
I can't for the life of me figure out how this is supposed to work in Xcode 4. I haven't changed any project/target settings but the dependent library will not build. Has anyone successfully setup library dependencies so that they automatically build in Xcode 4?
Without breaking NDA, I highly recommend watching the WWDC 2010 videos for session 308 - Developing Your App with Xcode 4 and session 314 - Building and Distributing Your App with Xcode 4. Setting up dependencies in Xcode 4 is demonstrated in these videos.
If those videos are unable to answer your specific questions, I recommend heading over to the Apple Developer Forums to ask the engineers themselves.
I write article on topic. Check this out.
I'm new to iPhone dev and am using sqlite3 but there seem to be two different sqlite libraries available: libsqlite3.0.dylib and libsqlite3.dylib
Which is the best to use? What's the difference?
Any help appreciated.
The libsqlite3.dylib library will be a symbolic link to the latest version supported in your Xcode installation. So whenever you install the latest Xcode and recompile your app, you'll get the latest 3.x library installed for free.
This can include both performance and feature enhancements, but can also include new bugs. You could pick the specific version, i.e. libsqlite3.0.dylib, if you want to play it safe.
The iPhone OS X contains 3, however there is an issue with Tiger having a different version. If that's what you're using then it's worth getting the latest version and upgrading to avoid issues.