GitHub - shovanj/aws-sdk-ios: Official mirror of version 2 of the AWS Mobile SDK for iOS. For more information, see our web site:

#Version 2 of the AWS SDK for iOS

Version 2 of the AWS Mobile SDK for iOS has reached General Availability (GA) and is no longer in Developer Preview. Version 1 is deprecated as of September 29, 2014, and will continue to be available until December 31, 2014, in our aws-sdk-ios-v1 repository. If you are building new apps, we recommend you use Version 2.

##Highlights

Amazon Cognito – A simple user identity and synchronization service that helps you securely manage and synchronize app data for your users across their mobile devices. With Amazon Cognito, you can save any kind of data, such as app preferences or game state, in the AWS cloud without writing any backend code or managing any infrastructure.
Amazon Mobile Analytics – A service for collecting, visualizing, and understanding app usage data at scale. Amazon Mobile Analytics reports are typically updated within 60 minutes of data being received. Amazon Mobile Analytics is built to scale with the business and can collect and process billions of events from millions of endpoints.
Amazon Kinesis Recorder – Enables you to reliably record data to an Amazon Kinesis data stream from your mobile app. Kinesis Recorder batches requests to handle intermittent network connections, and it enables you to record events even when the device is offline.
Amazon DynamoDB Object Mapper - We have made it easier to use DynamoDB from the AWS SDK for iOS by providing the DynamoDB Object Mapper for iOS. The DynamoDB Object Mapper makes it easy to set up connections to a DynamoDB database and supports high-level operations like creating, getting, querying, updating, and deleting records.
Amazon S3 Transfer Manager - We have rebuilt the S3TransferManager to utilize BFTask in the AWS SDK for iOS. It has a clean interface, and all of the operations are now asynchronous.
ARC support - The AWS SDK for iOS is now ARC enabled from the ground up to improve overall memory management.
BFTask support - With native BFTask support in the AWS SDK for iOS, you can chain async requests instead of nesting them. This makes the logic cleaner while keeping the code more readable.
Conforming Objective-C recommendations - The AWS SDK for iOS conforms to Objective-C best practices. The SDK returns NSErrors instead of throwing exceptions. iOS developers will now feel at home when using the AWS Mobile SDK.
Official CocoaPods support - Including the AWS SDK for iOS in your project is now easier than ever. You just need to add pod 'AWS<#ServiceName#>' to your Podfile.

##Setting Up

To get started with the AWS SDK for iOS, you can set up the SDK and start building a new project, or you can integrate the SDK in an existing project. You can also run the samples to get a sense of how the SDK works.

The AWS Mobile SDK for iOS supports the following versions of software:

Xcode 5 and later
iOS 7 and later

You can check out the SDK source code.

##Include the SDK for iOS in an Existing Application

The sample apps are standalone projects that are already set up for you. You can also integrate the SDK for iOS with an existing application. If you have an existing app in which you'd like to use AWS, there are two ways to import the AWS Mobile SDK for iOS into your project:

###CocoaPods

The AWS Mobile SDK for iOS is available through CocoaPods. If you have not installed CocoaPods, install CocoaPods by running the command:
```
 $ sudo gem install cocoapods
 $ pod setup
```

In your project directory (the directory where your *.xcodeproj file is), create a plain text file named Podfile (without any file extension) and add the following lines.

 source 'https://github.com/CocoaPods/Specs.git'
 
 pod 'AWSCore'
 pod 'AWSAutoScaling'
 pod 'AWSCloudWatch'
 pod 'AWSDynamoDB'
 pod 'AWSEC2'
 pod 'AWSElasticLoadBalancing'
 pod 'AWSKinesis'
 pod 'AWSS3'
 pod 'AWSSES'
 pod 'AWSSimpleDB'
 pod 'AWSSNS'
 pod 'AWSSQS'
 pod 'AWSCognito'

Then run the following command:
```
 $ pod install
```
Open up *.xcworkspace with Xcode and start using the SDK.

Note: Do NOT use *.xcodeproj. If you open up a project file instead of a workspace, you receive an error:
```
 ld: library not found for -lPods-AWSiOSSDKv2
 clang: error: linker command failed with exit code 1 (use -v to see invocation)
```

###Frameworks

Download the SDK from our AWS Mobile SDK page. The SDK is stored in a compressed file archive named aws-ios-sdk-#.#.# (where #.#.# represents the version number, so for version 2.0.0, the filename is aws-ios-sdk-2.0.0).

Note: The size of AWSiOSSDKv2.framework is > 65MB; however, it does not add > 65MB to your app binary when imported to your project because:
- Only objects that you use in your app are included in your app binary from the framework
  
  AWSiOSSDKv2.framework contains a static library, and object code in the library is incorporated in your app binary file at build time. When the -ObjC and -all_load linker flags are NOT used, Xcode is smart enough to figure out what objects from the framework are necessary for your app and include just those objects. AWSiOSSDKv2.framework is packaged so that you do not need to include these linker flags. (If you are using a third-party framework that requires you to include the -ObjC or -all_load linker flags, you can use -force_load instead to include those frameworks.)
  
  For example, if you only use Amazon DynamoDB in your app and none of the other supported services, your app won't include object code for those other services. Unless you use every single object from the framework, only a portion of the code from the framework will be included in your app.
- The framework contains five architectures, while apps on a device need at most three
  
  We currently compile the AWS Mobile SDK for iOS for five architectures: armv7, armv7s, arm64, i386, and x86_64. If you want to optimize your app for 64-bit devices including iPhone 6 and iPhone 5S, you need to build your app with arm64 support. 32-bit iOS devices that the AWS SDK for iOS supports use the armv7 and armv7s architectures.
  
  The 64-bit iPhone simulators use x86_64, and 32-bit simulators use i386 because they run on the Mac. We support these architectures so that the developers can run their apps with our framework on the simulator for testing. x86_64 and i386 support is essential for testing, but the code is unnecessary for apps on the App Store. Even if you use every single object from the AWS Mobile SDK, the app that you submit to Apple never includes about two fifths of the code included in the framework.
- Apps on the App Store are compressed
  
  After you submit your app to Apple, it is encrypted for DRM purposes and re-compressed. This leads to an even smaller footprint.
With your project open in Xcode, Control+click Frameworks and then click Add files to "<project name>"....
In Finder, navigate to the AWS<#ServiceName#>.framework files and select them.
- AWSCore.framework
- AWSAutoScaling.framework
- AWSCloudWatch.framework
- AWSDynamoDB.framework
- AWSEC2.framework
- AWSElasticLoadBalancing.framework
- AWSKinesis.framework
- AWSS3.framework
- AWSSES.framework
- AWSSimpleDB.framework
- AWSSNS.framework
- AWSSQS.framework
- extras/AWSCognito.framework - for Amazon Cognito Sync
Click Add.
Following the same procedure, add the following frameworks, located in the third-party directory, into your project.
- Bolts.framework (If your application uses the Facebook SDK, you may not need this framework, as it's already included with the Facebook SDK.)
- FMDB.framework
- GZIP.framework
- Mantle.framework
- Reachability.framework
- TMCache.framework
- UICKeyChainStore.framework
- XMLDictionary.framework
Drag and drop the following JSON files, located in the service-definitions directory, into your project.
- autoscaling-2011-01-01.json
- cognito-identity-2014-06-30.json
- cognito-sync-2014-06-30.json
- dynamodb-2012-08-10.json
- ec2-2014-06-15.json
- elasticloadbalancing-2012-06-01.json
- email-2010-12-01.json
- kinesis-2013-12-02.json
- mobileanalytics-2014-06-30.json
- monitoring-2010-08-01.json
- s3-2006-03-01.json
- sdb-2009-04-15.json
- sns-2010-03-31.json
- sqs-2012-11-05.json
- sts-2011-06-15.json
Open a target for your project, select Build Phases, expand Link Binary With Libraries, click the + button, and add libsqlite3.dylib, libz.dylib, and SystemConfiguration.framework.

##Update the SDK to a Newer Version

When we release a new version of the SDK, you can pick up the changes as described below.

###CocoaPods

Run the following command in your project directory. CocoaPods automatically picks up the new changes.
```
 $ pod update
```
Note: If your pod is having an issue, you can delete Podfile.lock and Pods/ then run pod install to cleanly install the SDK.

###Frameworks

In Xcode select the following frameworks and hit delete on your keyboard. Then select Move to Trash:
- AWSCore.framework
- AWSAutoScaling.framework
- AWSCloudWatch.framework
- AWSDynamoDB.framework
- AWSEC2.framework
- AWSElasticLoadBalancing.framework
- AWSKinesis.framework
- AWSS3.framework
- AWSSES.framework
- AWSSimpleDB.framework
- AWSSNS.framework
- AWSSQS.framework
- AWSCognito.framework
- Bolts.framework
- FMDB.framework
- GZIP.framework
- Mantle.framework
- Reachability.framework
- TMCache.framework
- UICKeyChainStore.framework
- XMLDictionary.framework
Also, delete the JSON files:
- autoscaling-2011-01-01.json
- cognito-identity-2014-06-30.json
- cognito-sync-2014-06-30.json
- dynamodb-2012-08-10.json
- ec2-2014-06-15.json
- elasticloadbalancing-2012-06-01.json
- email-2010-12-01.json
- kinesis-2013-12-02.json
- mobileanalytics-2014-06-30.json
- monitoring-2010-08-01.json
- s3-2006-03-01.json
- sdb-2009-04-15.json
- sns-2010-03-31.json
- sqs-2012-11-05.json
- sts-2011-06-15.json
Follow the installation process above to include the new version of the SDK.

##Getting Started with Swift

Create an Objective-C bridging header file using Xcode.
In the bridging header, import the appropriate headers for the services you are using. The header file import convention is #import <AWSServiceName/AWSServiceName.h>, as in the following examples:
```
 #import <AWSCore/AWSCore.h>
 #import <AWSS3/AWSS3.h>
 #import <AWSDynamoDB/AWSDynamoDB.h>
 #import <AWSSQS/AWSSQS.h>
 #import <AWSSNS/AWSSNS.h>
 #import <AWSCognito/AWSCognito.h>
```
From Your Target > Build Settings > Objective-C Bridging Header, point Objective-C Bridging Header to the bridging header you just created.
Import the AWSCore header in the application delegate.
```
 #import <AWSCore/AWSCore.h>
```

Create a default service configuration by adding the following code snippet in the application:didFinishLaunchingWithOptions: application delegate method.

 let credentialsProvider = AWSCognitoCredentialsProvider(
     regionType: CognitoRegionType,
     identityPoolId: CognitoIdentityPoolId)
 let configuration = AWSServiceConfiguration(
     region: DefaultServiceRegionType,
     credentialsProvider: credentialsProvider)
 AWSServiceManager.defaultServiceManager().defaultServiceConfiguration = configuration

Make a call to the AWS services.

 let dynamoDB = AWSDynamoDB.defaultDynamoDB()
 let listTableInput = AWSDynamoDBListTablesInput()
 dynamoDB.listTables(listTableInput).continueWithBlock{ (task: BFTask!) -> AnyObject! in
     let listTablesOutput = task.result as AWSDynamoDBListTablesOutput

     for tableName : AnyObject in listTablesOutput.tableNames {
         println("\(tableName)")
     }

     return nil
 }

Note: Most of the service client classes have a singleton method to get a default client. The naming convention is + defaultSERVICENAME (e.g. + defaultDynamoDB in the above code snippet). This singleton method creates a service client with defaultServiceConfiguration, which you set up in step 5, and maintains a strong reference to the client.

##Getting Started with Objective-C

Import the AWSCore header in the application delegate.
```
 #import <AWSCore/AWSCore.h>
```

Create a default service configuration by adding the following code snippet in the application:didFinishLaunchingWithOptions: application delegate method.

 AWSCognitoCredentialsProvider *credentialsProvider = [[AWSCognitoCredentialsProvider alloc] initWithRegionType:CognitoRegionType
                                                                                                 identityPoolId:CognitoIdentityPoolId];
 AWSServiceConfiguration *configuration = [[AWSServiceConfiguration alloc] initWithRegion:DefaultServiceRegionType
                                                                      credentialsProvider:credentialsProvider];
 AWSServiceManager.defaultServiceManager.defaultServiceConfiguration = configuration;

Import the appropriate headers for the services you are using. The header file import convention is #import <AWSServiceName/AWSServiceName.h>, as in the following examples:

 #import <AWSCore/AWSCore.h>
 #import <AWSS3/AWSS3.h>
 #import <AWSDynamoDB/AWSDynamoDB.h>
 #import <AWSSQS/AWSSQS.h>
 #import <AWSSNS/AWSSNS.h>
 #import <AWSCognito/AWSCognito.h>

Make a call to the AWS services.

 AWSS3TransferManager *transferManager = [AWSS3Transfermanager defaultS3TransferManager];
 AWSS3TransferManagerUploadRequest *uploadRequest = [AWSS3TransferManagerUploadRequest new];
 uploadRequest.bucket = yourBucket;
 uploadRequest.key = yourKey;
 uploadRequest.body = yourDataURL;
 uploadRequest.contentLength = [NSNumber numberWithUnsignedLongLong:fileSize];

 [[transferManager upload:uploadRequest] continueWithBlock:^id(BFTask *task) {
 	// Do something with the response
     return nil;
 }];

Note: Most of the service client classes have a singleton method to get a default client. The naming convention is + defaultSERVICENAME (e.g. + defaultS3TransferManager in the above code snippet). This singleton method creates a service client with defaultServiceConfiguration, which you set up in step 5, and maintains a strong reference to the client.

##BFTask

With native BFTask support in the SDK for iOS, you can chain async requests instead of nesting them. It makes the logic cleaner, while keeping the code more readable. Read this blog post to learn how to use BFTask.

##Logging

Changing log levels during development may make debugging easier. You can change the log level by importing AWSCore.h and calling:

Swift

AWSLogger.defaultLogger().logLevel = .Verbose

The following logging level options are available:

.None
.Error (This is the default. Only error logs are printed to the console.)
.Warn
.Info
.Debug
.Verbose

Objective-C

[AWSLogger defaultLogger].logLevel = AWSLogLevelVerbose;

The following logging level options are available:

AWSLogLevelNone
AWSLogLevelError (This is the default. Only error logs are printed to the console.)
AWSLogLevelWarn
AWSLogLevelInfo
AWSLogLevelDebug
AWSLogLevelVerbose

##Sample Apps

The AWS SDK for iOS includes sample apps that demonstrate common use cases.

###Cognito Sync Sample (Objective-C)

This sample demonstrates how to securely manage and sync your mobile app data and create unique identities via login providers including Facebook, Google, and Login with Amazon.