Something which is a bit ambiguous in the documentation is what happens when a call to registerToken fails. Will the Iterable SDK automatically retry to register this token later (e.g. upon regaining reachability or resuming from background), or is it up to the client developer to implement retry upon failure?

Because the email is a readonly value.
If a user log out account(email), and log in another email, how can i register the new email to iterable?

Some functions don't require their second parameter; for instance, trackPushOpen:dataFields: can have an override trackPushOpen: which calls trackPushOpen:userInfo dataFields:nil

Additionally, add nullability annotations

NSURLConnection is deprecated as of iOS 9, and its functionality has been replaced/improved by NSURLSession

I'm trying to install via cocoapods but files seem to be missing. For instance, IterableConfig.h and .m, and many others.

Am I misunderstanding something?

There are a few ways you can call registerToken:appName:pushServicePlatform:onSuccess:onFailure and get neither callback

Would be nice to have cocoapods support.

For starters a podspec file would be nice.
Example: https://github.com/achainan/WebView/blob/master/ACWebViewController.podspec
Details: https://guides.cocoapods.org/syntax/podspec.html

Thanks!

Pods/Iterable-iOS-SDK/swift-sdk/IterableConstants.h:12:41: Pointer is missing a nullability type specifier (_Nonnull, _Nullable, or _Null_unspecified)

Using 6.0.4.

I've created a binding library for IterableSDK.
Objective C has some method that cannot be converted into C#

This problem was caused by Objective-C letting multiple functions have same parameter types. This binding moves the userId parameter after the NSDictionary launchOptions to avoid that problem.

The binding works perfectly fine, but I was wondering if you guys could take a look at this as well.

https://github.com/Jjastiny/IterableIOSBindings

Releases are missing the resulting artifact (static library) to be imported in project via an artifactory manager.

the Apple docs state that the push token is 32 bytes

however, it also warns "APNs device tokens are of variable length. Do not hardcode their size."
https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/ApplePushService.html#//apple_ref/doc/uid/TP40008194-CH100-SW12

seems WWDC2015 announced the tokens were going to be upped to 100 bytes: http://odecee.com.au/wwdc-2015-big-changes-to-apple-push-notifications/

Some errors can be handled better than they currently are; through docs, nullable annotations, and NSError.

Currently, there is only one log level, error (from NSLog).

Switch to using asl/syslog for configurable log levels.

Currently, a lot of debug/info level information is printed. Additionally, there is logging of tokens and other identifiers. These should be removed when building for production.

It would be nice to have handlers other than the default logs