I am looking for the latest version of JSON-Framework for ios 5.0. I like this becouse is very easy to use (you can see here)
I have found this but in the oficial web, all is deprecated.
(Here is an image, i can post any image yet)
Any idea?
JSON-Framework is available on Github here, and it is still being updated
But you don't need to use it ion iOS 5 at all, because Apple introduced native JSON parsing using the NSJsonSerialization class (documentation here). Most developers would recommend moving to Apple's native implementation unless you had a specific reason for not doing so, and then falling back to a library like JSON-Framework for older OS versions.
Related
Running Xcode version 8.2.1, Swift 3, and Cocoapods version 1.1.1 and I can't for the life of me figure out how to resolve this issue. I need to use the analytics library but can't get past this error in the UIViewController+SEGScreen.m class:
Without forking, is there another solution here?
What exactly do you need to figure out? The API is not available when targeting iOS extensions. There is no solution but fixing the API. If this is an open source, the fix looks really simple (wrapping in a custom macro such #ifdef TARGET_EXTENSION). If not, time to use a properly written analytics framework, that takes into account all aspects of iOS development, not the most trivial ones only.
I'm trying to link to the Firebase SDK (v2.5.0) within my OS X framework, but it keeps telling me I am trying to link to a framework built for iOS.
It seems to state pretty clearly on the Firebase docs that the iOS framework can be used to build OS X clients as well, so does anyone know what I am doing wrong here?
ld: in /[...]/Firebase.framework/Firebase(Firebase.o), building for OSX, but linking in object file built for iOS, for architecture x86_64
As of 2.4.0 (changelog), Firebase no longer ships a single binary for iOS and OSX, but instead has multiple frameworks (Firebase.framework for iOS, FirebaseOSX.framework for OSX). Similarly, the iOS Cocoapod is named Firebase, while the OSX Cocoapod is named FirebaseOSX. This is due to several changes in our build process, such as adding bitcode support (which only makes sense on iOS).
We still build and release iOS and OSX through these channels, and continue to support OSX, though it's not heavily advertised (as you noticed). As mentioned, if you don't use Cocoapods, using https://cdn.firebase.com/ObjC/FirebasePlatform.framework-major.minor.patch.zip will get you the framework, then follow the Alternative Setup instructions for including it in your project.
You need to add some dependencies in your project's Build Phases:
libicucore.dylib
libc++.dylib
CFNetwork.framework
Security.framework
SystemConfiguration.framework
See the Apple docs on how to add these if you haven't done this before.
Ok, this is a bit weird.. But after digging around in the pod specs I noticed that the FirebaseOSX podspec links to a different url than the iOS pod (FirebaseOSX.framework and an older version).
So I decided to copy the framework url from the Firebase site, and change the name and try that, and it downloaded a OSX framework for me. This is really weird, because I can't for the life of me understand that I should do like that based on what I can read on the Firebase site, so I can't really consider this the official way as it doesn't really make any sense. But it seems to work for now..
So for v2.5.0 the url is:
https://cdn.firebase.com/ObjC/FirebaseOSX.framework-2.5.0.zip
I've just downloaded a PARSE Starter Project, as well a the latest Facebook SDK.
I've followed all the steps from Parse and Facebook tutorials on how to get started, and I had to solve a lot of issues linked to the bridging header.
However, now that everything should work fine, I got a problem: ParseFacebookUtils.Framework has a
#import <FacebookSDK/FacebookSDK.h>
statement.
However, latest Facebook SDKs do not have this framework anymore.
Is there a way I can solve this issue?
Yes, the Parse framework supports both, the 3.x versions of the Facebook SDK and the 4.x versions.
If you chose to use the 4.x versions, use the ParseFacebookUtilsV4.framework instead of ParseFacebookUtils.framework which only supports 3.x of the Facebook SDKs
I used to use MGTwitterEngine as my main twitter library for iOS, however, the last commit to the project's master branch is more than one year old (at the time of this writing) and the documentation is not that great. Now I am starting a new project and would like to get rid of the "clunky" MGTwitterEngine, what are other twitter libraries out there for iOS? Which are your favorites and why?
I found the following so far:
MPOAuth
ShareKit (provides a lot more than just Twitter sharing)
Apple announced in the WWDC keynote that Twitter access will be built into the OS in iOS 5, so assuming that means built-in API access its likely that all third-party Twitter libraries are being left to wither. Those who develop for iOS have access to the beta APIs, so even though we can't say anything for sure about future API releases, they could (NDA notwithstanding).
That being said, I'd add DDSocialClient to the list. Like ShareKit it does a whole lot more than Twitter, but it's much less prescriptive on user interface. It restricts itself mostly to the nuts and bolts of the service integration. Whether you think that's liberating or just more work is probably a judgment call.
iOS5 is coming out soon but i'm using MGTwitterEngine and it works like a charm. http://mattgemmell.com/2008/02/22/mgtwitterengine-twitter-from-cocoa
Also you can try sharekit but I dont like it as much.
The concern is guaranteeing compatibility with the Sqlite Header file compiled into the iPhone app. What if the header file used at compile time is from a newer version then the dynamic library installed on the iPhone? This could be due to the app running on an older or newer iPhone OS version then the app was built with. Is it safe to use the Sqlite dynamic library on the iPhone? Or should we always statically link. BTW: Would rather not use Core Data.
SQLite is very careful about api compatibility. I think there are some very old apis that are marked as deprecated and non-functional but AFAIK they can still be called. That said, why not just include the amalgamation?
The sqlite docs seem to recommend checking that the header file version is the same as the library version at: http://www.sqlite.org/c3ref/libversion.html. Worried because it doesn't seem like sqlite provides a contract/guarantee that things will keep working across versions. Besides deprecation there could be other types of incompatibility, regarding behavior or object size that could lead to crashes. As far the amalgamation that would add an additional 680K or so to the app. A pretty big hit for a mobile app.
First of all, the iPhone environment is tightly controlled by Apple, so you don't have to worry about a wide variety of SQLite libraries being installed on devices.
Second, when you use Xcode to link to a library you can choose to link against sqlite, sqlite3, sqlite3.6, etc. That way, if you are using a feature and cannot use anything earlier than 3.6, you can specify so in your app.
Third, SQLite is a stable project and you can trust that the authors won't make radical changes to the API without warning. If you link against sqlite3 you should be safe, unless you are doing some really weird.
Fourth, if you are doing something really weird, that relies on a quirk of a specific version of SQLite, then you should probably statically link to the library or stop doing that really weird thing.
In conclusion, yes, it is totally safe and recommended to dynamically link to the sqlite library on the iPhone, unless you are doing something really weird.