Xcode has a powerful static code analyzer, really simple to use: just open your project, ’Product’ > ’Analyze’ or simply hit ⇧⌘B:
The static analyzer can detect potential memory leaks, unused ivars, variables used but never read, dead code path etc… It can prevents a whole class of errors while sanitising your code.
2. Analyze from the command line
Launching the static analyze in command-line with Xcode 5.1 is really simple:
Then, you will have the analysis result in your terminal window:
Just a detail: if you’re using a scheme based approach (contrary to the traditional pre-Xcode 4 target / configuration), you don’t need to set in the command line options which configuration you want to use. Well used, the scheme approach dispenses you to think in term of Release / Debug configurations: the archive scheme will used the Release configuration, because obviously you want to deliver your app compiled in Release; the Debug scheme will use the Debug configuration, and the analyze scheme is based on the Debug configuration because Release optimisation could alter the static code analyse. If you want to check on what configurations your schemes are based, just click on the current scheme name in Xcode status bar
Then ’Manage Schemes…’
Viewing analysis results from the terminal is not very practical. To have a better rendering of the issues, we are going to use the last version of Clang Static Analyzer. The advantage of using this analyzer is that it’s often newer than the analyzer provided with Xcode, and thus can contain bug fixes, new checks, or simply better analysis.
includes about 9 months of change to Clang itself (improved C++11/14 support, etc.)
more precise modelling of Objective-C properties, which enables the analyzer to find more bugs.
includes a new "missing call to super" warning, which looks for common pattern in iOS/OSX APIs that require chaining a call to a super class’s implementation of a method.
accepts -arch arm64 (which may be passed by Xcode 5.0), but for the time being analyses code in such cases as -arch armv7s.
many sundry fixes, improvements to C++ support, etc.
To install it, just download the last version checker-276.tar.bz2 and unzip it. In the checker-276 folder, you will find two important scripts: scan-build and scan-view.
To launch an analyse, just write the same command line as previously, prefixed with scan-build:
The report is HTML-based and offers a detailed view on each potential bug:
3. Analyze from the Jenkins
Launching analysis from the command line is cool, but what’s cooler is to have your Jenkins do it automatically for you while you drink a coffe (or play ping-pong). There is a Clang Scan-Build Plugin that can be used, but unfortunately, as of 14 April 2014, the plugin only supports Xcode 4.
To support Xcode 5, we’ll have to make small modifications to the plugin and recompile it. Fortunately, it’s not as complicated as it sounds.
First thing is to install Maven on your OSX (if you don’t already have it - OSX prior to Mavericks/10.9 actually comes with Maven 3 built in). To install it, simply use Homebrew:
This way, you’ll be able to specify your xcodeproj and a scheme in the Jenkins plugin configuration.
Next, recompile the plugin: open a terminal, go in your working copy of the plugin and type
mvn install
Or, if you want to skip tests
mvn -Dmaven.test.skip=true install
Then after the compilation success, a target folder has been created; you will find inside the plugin installer file, clang-scanbuild-plugin.hpi, (which is simply a jar file). To install this modified plugin, copy it directly in the Jenkins plugins folder (on your Jenkins server), usually under ~/.jenkins/plugins. Restart Jenkins, go to the plugins configuration page to check that your new plugin is installed (goto your Jenkins server homepage, then select ’Manage Jenkins’, then ’Manage Plugins’ and click on the ’Installed’ tabs):
Now that the plugin is ready, we’re going to install the Clang Static Analyzer on our Jenkins machine. Just unzip checker-276.tar.bz2 on your custom binaries location: for instance, I unzip mine under /usr/local/Cellar/scan-build/ to not mess with the system binaries.
Then we need to tell Jenkins where to find the static analyzer:
Go to your Jenkins server homepage, then select ’Manage Jenkins’
In the Clang Static Analyzer section, click on ’Clang Static Analyzer installations…’
Type ’scan-build’ in the Name text field, and /usr/local/Cellar/scan-build in the ’Installation directory’ field (this is the folder containing the scan-build binary on the Jenkins server)
Finally, it’s time to create a job for the analysis. If your iOS job is already using the Warnings Plugin, I advise to create create a dedicated job for the static analyze, because the warnings raised by the static analysis will be also counted by the warning plugin as "standard" warninngs.
So, create a new job for this build, and add a build step ’Clang Scan-build’:
Then add a post build action, ’Publish Clang scan-build reports’:
You can customize the stable / unstable build threshold, for instance 5 means that over 5 issues, your build will be considered as instable. Go crazy and set it to 0!
Finally, launch your first build. Open the job logs, and check the command line used at the beginning of the job:
EXECUTING COMMAND:[/usr/local/Cellar/scan-build/scan-build, -k, -v, -v, -o, /Users/jenkins/.jenkins/jobs/Meon/workspace/clangScanBuildReports, xcodebuild, -scheme, Meon, -configuration, Debug, -sdk, iphonesimulator7.1, clean, analyze]
[iOS] $ /usr/local/Cellar/scan-build/scan-build -k -v -v -o /Users/jenkins/.jenkins/jobs/Meon/workspace/clangScanBuildReports xcodebuild -scheme Meon -configuration Debug -sdk iphonesimulator7.1 clean analyze
scan-build: Using ’/usr/local/Cellar/scan-build/bin/clang’ for static analysis
scan-build: Emitting reports for this run to ’/Users/jenkins/.jenkins/jobs/Meon/workspace/clangScanBuildReports/2014-04-15-184221-65970-1’.
User defaults from command line:
PBXBuildsContinueAfterErrors = YES
Build settings from command line:
CLANG_ANALYZER_EXEC = /usr/local/Cellar/scan-build/bin/clang
CLANG_ANALYZER_OTHER_FLAGS =
CLANG_ANALYZER_OUTPUT = plist-html
CLANG_ANALYZER_OUTPUT_DIR = /Users/jenkins/.jenkins/jobs/Meon/workspace/clangScanBuildReports/2014-04-15-184221-65970-1
RUN_CLANG_STATIC_ANALYZER = YES
SDKROOT = iphonesimulator7.1
=== CLEAN TARGET Meon OF PROJECT Meon WITH CONFIGURATION Debug ===
Check dependencies
…
Extracted from the logs, you can see the command line call:
Which is exactly what we want. After a few builds, you will have this nice graph on your jobs homepage:
If you select a particular job, you will see the list of each issues reported by the analyzer. At the end of each line, you have a link to the detail analysis for this particular issue: it is simply the same HTML report that you would have with scan-view but this time, it’s integrated in the Jenkins jobs page.
Unfortunately, if you click on a bug detail, you will see a 404 page instead of the bug report. To fix it, copy the scan build output to a folder named ‘clangScanBuildReports’ inside the build directory (you can copy only the html files). For instance, in my case, I’ve added another build step after the static anlysis that will do:
The Heartbleed bug allows anyone on the Internet to read the memory of the systems
protected by the vulnerable versions of the OpenSSL software. This compromises
the secret keys used to identify the service providers and to encrypt the traffic,
the names and passwords of the users and the actual content. This allows attackers
to eavesdrop on communications, steal data directly from the services and users
and to impersonate services and users.
I want to take a moment to point at the marketing aspects of it: how
the knowledge about Heartbleed managed to spread within a day and move,
literally, hundreds of thousands of people to remediate the problem.
Heartbleed is much better marketed than typical for the OSS community, principally
because it has a name, a logo, and a dedicated web presence.
All of this means that applying the OpenSSL patch is only the starting point
on the multi-step path of Heartbleed recovery. Website operators should strongly
consider replacing their X.509 certificates after applying the update and getting
all users and administrators to change passwords as well. While it’s possible that
none of this data has been compromised, there’s no way to rule it out, either.
A lot of the narratives around Heartbleed have viewed this bug through a worst-case lens,
supposing that it might have been used for some time, and that there might be tricks
to obtain private keys somewhat reliably with it. At least the first half of that scenario
is starting to look likely.
Matthew Sullivan posted a blog post earlier today about using CVE-2014-0160
to hijack user sessions from vulnerable servers. I altered the proof of concept
code written by Jared Stafford to continuously query a given server for memory
chunks and parse those chunks for session ids.
The researchers who discovered the vulnerability, however, were less optimistic
about the risks, saying the bug makes it possible for attackers to surreptitiously
bypass virtually all TLS protections and to retrieve sensitive data residing
in the memory of computers or servers running OpenSSL-powered software.
"We attacked ourselves from outside, without leaving a trace," they wrote.
"Without using any privileged information or credentials we were able steal
from ourselves the secret keys used for our X.509 certificates,
user names and passwords, instant messages, emails and business
critical documents and communication."
Finally, given the growing public awareness of this bug, it’s probable
that phishers and other scam artists will take full advantage of the
situation. Avoid responding to emailed invitations to reset your password;
rather, visit the site manually, either using a trusted bookmark or
searching for the site in question.
The Heartbleed vulnerability is one of the worst Internet security problems we have seen.
I’ll be writing more about what we can learn from Heartbleed and the response to it.
For now, here is a quick checklist of what you can do to protect yourself.
Well, it’s more a wish list than real predictions about what will be announced in June, at the WWDC 2014. Let’s go!
iPhone 6 with a 5 inches screen
Having a new iPhone with a bigger screen is an evidence. What the physical screen size could be? And maybe more important (for a developer), what would be the screen size in pixel? Let’s imagine that the number of pixels will be the same as the current iPhone 5x line: 640 pixels by 1136 pixels: no need to redesign apps, the whole UI will be simply bigger. Given this, a safe bet would be also that this new iPhone will use the same PPI (pixel-per-inch) as the current iPad Air: 264 ppi.
A pixel-width of 640 with a 264 ppi give us a 640 / 264 = 2.424 inches width; and we get 1136 / 264 = 4.303 inches for the height.
Our new screen will measure 2.424 inches by 4.303 inches, by consequence a 4.94 inches diagonal… Let’s simply say: a 5 inches screen.
Get a paper, a rule and draw a 2.424 inches by 4.303 inches (6.2 cm by 10.9 cm): it’s big, but not insanely big… Of course, you have to add extra space for the home button and the phone bevels: I can really see the iPhone 6, top of the iPhone line, with a screen this big.
But a 640 x 1136 pixels screen is a very very conservative number of pixels, especially regarding the current Android phones: the Nexus 5 has a 1080 x 1920 pixels screen, with a 445 ppi density. If you look at high-definition smartphone displays, you will get 3 different sizes: 720px by 1280px, 800px by 1280px and 1080px by 1920px, with a maximum ppi of 468 for the HTC One: all these sizes will introduces a kind of fragmentation if chosen for the iPhone 6 (even with AutoLayout), and some additional effort for developers.
In my dream: the iPhone 6 has a 1280 px by 2272 px screen, double the pixel size in width and height of the current iPhone 5s. No need to redesign apps, just get @4x resources and done. But certainly not this year.
New Apple TV
This WWDC will introduce the App Store for Apple TV, with a dedicated gamepad. Based on the iOS 8 beta SDK, developers will be able to develop apps for the Apple TV, and the Apple TV will receive a Back to the Mac treatment: Game Center, Push Notifications etc… The Apple TV will become a true home media center: video game console, VOD, apps, a Siri driven UI, etc… it’s the Apple Bandai Pippin on steroids!
Why do I think this year will be the Apple TV’s year ? Basically, four things:
1. iOS 7 Game Controller: iOS 7 has seen the introduction of a Game Controller framework, making it easy to discover game controllers connected to a Mac or iOS device. Apple has even created specifications for distinct kinds of MFi game controllers with many common characteristics that must be implemented strictly according to the specification.
Allowing gamepad accessories just for iPhone and iPad seems to me too limited and I dream for an Apple console, with a dedicated gamepad and an unlimited App Store.
2. Amazon Fire TV:
Few days ago, Amazon announces the Amazon Fire TV, available in the US for $99:
Over 200,000 TV episodes and movies, and over a hundred games (Minecraft-Pocket Edition, The Walking Dead, Monsters University etc…),
Voice search,
Fast quad-core processor, 2 GB of memory, dedicated GPU, plus 1080p HD video and Dolby Digital Plus surround sound
In my mind, the Amazon Fire TV is a direct Apple TV concurrent, and Apple has to respond to this threat with a better Apple TV.
3. A7 aka Cyclone:
Apple has undoubtedly great plans for the A7, the CPU used in the iPhone 5s. This analyse by AnandTech shows that the A7 has a bright future and this future could be the Apple TV.
Cyclone is a bold move by Apple, but not one that is without its challenges. I still
find that there are almost no applications on iOS that really take advantage of the
CPU power underneath the hood. More than anything Apple needs first party software
that really demonstrates what’s possible.
…
Looking at Cyclone makes one thing very clear: the rest of the players in the ultra
mobile CPU space didn’t aim high enough. I wonder what happens next round.
4. PrimeSense bought by Apple:
Apple has recently bought PrimeSense, an Israeli company which provided 3D sensors for the first generation Microsoft Kinect. Seems like a really good fit for the Apple TV team…
iOS APIs
WWDC 2014 will usually introduce new APIs for iOS 8. If you look at the current iOS 7 private frameworks headers, you will find some interesting ones:
OAuth: wouldn’t it be cool to have this, built-in in the system as as public API?
VectorKit: how about an object-based for vectorial stuff (animations, 3D etc…); everything you need to re-build the Maps app.
RemoteUI: do you remember the Ole BegemannRemote View Controllers saga (part 1, part 2, part 3)? It could be really useful to easily share data and even UI between apps: think about a mini Drop box explorer in your app for instance… Data sharing between apps is the most obvious low-hanging fruit to me, so I expect Apple to address this in iOS 8.
UI is the crown jewels of iOS, and developers want more and more built-in UI components. Regarding AFNetworking and SDWebImage, I find it sad that we still need a third party framework to deal easily with HTTP request, and web-based images. Come on Apple, bring-us something like Requests for iOS 8!
Developers tools: Xcode 6
Better developer tools for better apps!
For WWDC 2014, I see: an enhanced version of XCTest with code coverage for instance; some new tools à laRevealApp, and finally a better Xcode editor / refactor, à laAppCode.
Since Xcode 4, Apple has really improved the Xcode tests tools; and even introduced last year the XCTest framework, a new test framework for Xcode. Currently, XCTest is not really more useful than the venerable SenTestingKit; but I bet Apple has great ambitions for XCTest. Why no add code coverage this year for instance?
Apple has to integrate RevealApp in Xcode. RevealApp has save me many times on really difficult UI bugs: it’s an indispensable addition to the iOS developer arsenal. RevealApp gives you a visual representation of the views hierarchies of your app, and you can event interact with:
XCode 6, the same Xcode with some good stuff from AppCode.
Objective-C
I do not expect big news in the Objective-C land, apart new features to deal with dependencies. EmbraceCocoaPods (the current de-facto standard dependency manager), and include it in OSX / iOS developers tools.
Using emojis in Django model fields is really easy. If you’re using SQLite as a database, you’ve nothing additional to do. You can save emojis in TextField or CharField without any problem. If you’re using a MySQL database, this article is for you, you’ll need some work to insure that every text field can use emojis. Finally, if you’re using a PostgreSQL database, I won’t be able to help you! I still haven’t switch to PostgreSQL (even if it is Two Scoops of Django’s recommendation)… So this article is really about saving emojis in a Django app backed by MySQL.
A Basic sample app
Let’s say we have a very simple Django app to manage comments.
Our model will be a Comment class, with two fields: a text field and an author field. In Django world, this translates in a models.py file like this:
from django.db import models
class Comment(models.Model):
text = models.TextField(max_length=2048, blank=True)
author = models.CharField(max_length=128, blank=True)
We have also a view that will display a list of comments, in views.py:
from django.views.generic import ListView
from .models import Comment
class CommentsView(ListView):
model = Comment
context_object_name = ’comments’
With the associated template in templates/comments/comment_list.html:
If you open the admin page, and create a new comment containing an emoji:
Django will throw an exception:
Incorrect string value: ’\xF0\x9F\x90\xAF’ for column ’text’ at row 1
That’s not good!
Solution
One of the most useful pointer to solve this issue is this very detailed post blog by Mathias Bynens. Adapted to our Django app, here are the simple steps to support emojis.
1. Switching from MySQL’s utf8 to utf8mb4
If you log to MySQL, and type this:
SHOW VARIABLES WHERE Variable_name LIKE 'character\_set\_%' OR Variable_name LIKE 'collation%';
So, first, we’re going to change the character set and collation properties of the database, tables, and columns, to use utf8mb4 instead of utf8.
# For each database:
ALTER DATABASE database_name CHARACTER SET = utf8mb4 COLLATE utf8mb4_unicode_ci;
# For each table:
ALTER TABLE table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
# For each column:
ALTER TABLE table_name CHANGE column_name column_name VARCHAR(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL;
# (Don’t blindly copy-paste this! The exact statement depends on the column type, maximum length, and other properties. The above line is just an example for a `VARCHAR` column.)
You will need to adjust this snippet, in particular adapt the database name and table name to your needs. In our case, this becomes:
ALTER DATABASE example CHARACTER SET = utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE comments_comment CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
ALTER TABLE comments_comment CHANGE text text LONGTEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL;
If you’ve installed Xcode 5.1 and want to install some of your favorite Python or Ruby toys on your OSX, you could have a bad surprise. For instance, if you try to install Fabric after upgrading to Xcode 5.1, you will fail!
Installation:
pip install Fabric
Results:
…
creating build/temp.macosx-10.9-intel-2.7/src
cc -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -Wall -Wstrict-prototypes -Wshorten-64-to-32 -fwrapv -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe -std=c99 -O3 -fomit-frame-pointer -Isrc/ -I/usr/include/ -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c src/_fastmath.c -o build/temp.macosx-10.9-intel-2.7/src/_fastmath.o
clang: error: unknown argument: ’-mno-fused-madd’ [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
error: command ’cc’ failed with exit status 1
The installation of Fabric failed because Fabric (probably PyCrypto) is using an unused command line (-mno-fused-madd), and, as of Xcode 5.1, clang treats unrecognized command-line options as errors.
As of Apple LLVM compiler version 5.1 (clang-502) and later, the optimization level -O4 no longer implies
link time optimization (LTO). In order to build with LTO explicitly use the -flto option in addition to
the optimization level flag(15633276)
The Apple LLVM compiler in Xcode 5.1 treats unrecognized command-line options as errors. This issue has been
seen when building both Python native extensions and Ruby Gems, where some invalid compiler options are currently
specified.
Projects using invalid compiler options will need to be changed to remove those options.
To help ease that transition, the compiler will temporarily accept an option to downgrade the error to a warning:
Note: This option will not be supported in the future.
To workaround this issue, set the ARCHFLAGS environment variable to downgrade the error to a warning.
For example, you can install a Python native extension with:
Speaking of awesome video game soundtracks, I love musics in Meon. When working on Meon, we did the graphics ourselves, it was a lot of work, especially when Retina devices appeared. When we begun to work on the soundtracks, we decided to hire a real professional composer.
If you want to make a game, here is my best advice: hire professional graphics and music composers, don’t waste time and energy on graphics and musics, just work with people that know much about it than you. You will spend more money for sure, but the result will be greater.
I’m so glad we have found the right person for Meon soundtracks: Benjamin Devos. Benjamin has done a wonderful work, and the result is simply excellent.
Music, by derrickkendall - Aug 13, 2011:
The music is very catchy and unique, especially after level 10.
I enjoyed that. A nice puzzle game
I love that game, by Opuspop:
The music in this game is awesome, the graphics are really nice and the
puzzles addictive.
Thumbs up
Musique et gameplay magnifiques, by ogechter - Mar 21, 2013:
Tout est dans le titre.
Si je trouve la musique en MP3, je me la passe en boucle.
Fantabulous, Paisa-vasool…killer :), by connect2ajay - May 05, 2013:
Meon commends Respect for Awesome music, game play & cutie Meons ;)
To whosoever I’ve shown the game, becomes addicted, hence proved :)
Thank you Meon Team for this Gem of a Puzzle Game. Looking forward to Meon
2….Waaaaaooooo ;D
By way of RickDeckarD (thanks!): After Bit - The Legend of Zelda : A Link Between Worlds shows how Ryo Nagamatsu has transformed and renewed A link To The Past’s musics in this new Zelda opus. Wonderful graphics (undoubtedly the best 3D effects on the 3DS, you have to see it in real), and the soundtrack is simply superb, generous, marvelous, ingenious. Great reviews of this music by jeuxvideo.com (unfortunately only in french!)
If you want to listen to all the ’A Link Between Worlds’ soundtracks, here is a YouTube playlist:
Nintendo may have a little bit of trouble, under the attack of the iDevices, but boys, I will give 1000 iPhone games for only one 3DS game of the quality of A Link Between Worlds. If you think Nintendo is over, just borrow a 3DS and play a few minutes with this Zelda game.
Some interesting links abouth the making of this new masterpiece:
Affiliation is a simple way to make extra revenues with your app or with your web site in the iOS/OSX world: it provides a way to link to songs, apps, movies, ebooks, earning you commissions on sales. The good news is that affiliation on iTunes (including App Store, iBooks, and Mac App Store), is really easy to set-up. The bad news is that you will need a lot of audience before making real money. Here’s a quick presentation, since there have been some changes recently.
Assume you’ve released an iOS app. Somewhere in your app, you’re promoting another iOS app; it can be one of your app, or any app available on the App Store. The promoted app can be paid or completely free. The only requirement is that the promoted app is available on the App Store.
Your user has tapped a button in your app to download this app, he is redirected to the corresponding page in the App Store. At this point, you’re done: you sole job is to send customers to the App Store, by any means… Whether the user will buy the app that you’ve promoted or not is not relevant. At this moment, you’re the current affiliate on the App Store.
Starting from now, and during the next 24 hours, you will earn a 7% commission on each sale done by the user. The user can quit your app, quit the App Store etc, every time he buys something on the store, you will be given a tiny 7% commission for the next 24 hours.
See, seems interesting! I’m using an iOS app in this example but really you can use affiliation with video, book, ringtones, tones, Mac app, podcasts, audiobooks, everything that is sold through iTunes, the App Store, iBooks and Mac App Store. In fact, everything that you can link to is eligible to affiliation.
You will see, it’s all about links. Given a link to the App Store, just add a parameter to this link identifying you (the affiliate token) will suffice to give you revenues.
Things to know:
There is only one affiliate on the App Store at a given date: your interest is to send users from your app to the store (while not harassing them). That’s why there are a lot of apps that promoted content and uses (and abuses) Push Notifications, to remain the affiliate.
Really you’ll need a lot of audience to make money.
Until very recently, iTunes Affiliate Program was operated by two or three platforms (Linkshare, Tradedoubler) and you had to register to each program to get affiliation revenues from all over the world.
Before diving into the account creation, just a word about worldwide support. You will get revenues from customers residing in this 127 countries, but affiliates can be located in any countries:
PHG
Argentina
Armenia
Australia
Austria
Bahamas
Bahrain
Barbados
Belarus
Belgium
Bermuda
Bolivia
Botswana
Brazil
Bulgaria
Canada
Cayman Islands
Chile
Colombia
Costa Rica
Croatia
Cyprus
Czech Republic
Denmark
Dominica
Ecuador
Egypt
El Salvador
Estonia
Finland
France
Germany
Greece
Guatemala
Honduras
Hong Kong
Hungary
India
Indonesia
Ireland
Israel
Italy
Japan
Jordan
Kazakhstan
Kenya
Kuwait
Latvia
Lebanon
Lithuania
Luxembourg
Macau
Malaysia
Malta
Mauritius
Mexico
Moldova
Netherlands
New Zealand
Nicaragua
Nigeria
Norway
Oman
Panama
Paraguay
Peru
Philippines
Poland
Portugal
Qatar
Romania
Russia
Saudi Arabia
Singapore
Slovakia
Slovenia
South Africa
Spain
Sweden
Switzerland
Taiwan
Tanzania
Thailand
Trinidad and Tobago
Turkey
Uganda
Ukraine
United Arab Emirates
United Kingdom
United States
Uruguay
Uzbekistan
Venezuela
Vietnam
Yemen
Sign-in to the iTunes Affiliate Program
Warning : before creating your account, you should insure that you have a live app in the store, or a live web site. Your web site can’t be in beta, or in ’work in progress’ mode. It must be live, with real datas and content, otherwise your affiliation account creation will be rejected.
Now, you just have to wait a few days (usually 3 to 5 days) and wait for your account creation confirmation. If your web site / app is live, your account should be validated without problem.
Once you have been notified that your affiliate account have been accepted, you can go sign-in http://affiliate.itunes.apple.com/signin. In the email that you’ve received, you have been given an Affiliated ID (or Affiliate Token): you really just need this token to make money! Affiliated token looks something like 11lqRB (which’s Manbolo’s one).
In case you miss it, you will find yours in your PHG console on the top-right corner:
3. Linking
Now that you’ve your affiliate token, you can start making money. All that you’ve to do is simply adding this token to the end of any iTunes, App Store or iBooks Store links to be eligible for commissions.
https://itunes.apple.com/app/meon/id400274934?mt=8&uo=4 is the unaffiliated link, while https://itunes.apple.com/app/meon/id400274934?mt=8&uo=4&at=11lqRB is the affiliated ones, using our affiliate token 11lqRB.
Starting from iOS 6, you have the possibility to show, inside your app, an "iTunes controller": SKStoreProductViewController. The big advantage over the previous approach is that you user is not redirected to the App Store, he can buy apps (and other iTunes content) directly inside you app, and never quit it. Note that you can also write reviews without quitting the app.
Unfortunately, as of iOS 7.0.6, there is no way to pass an affiliate token to a SKStoreProductViewController. It’s rather surprising because the APIs use to initialise this view controller (just a dictionary) will be well fitted to add an affiliate token. That’s said, if you still want to use SKStoreProductViewController, here is how you would do it:
- (IBAction)buyApp:(id)sender
{
// The store id of the product that you want to promote.
NSString *storeId = @"417817520";
NSDictionary *parameters = @{SKStoreProductParameterITunesItemIdentifier: storeId};
SKStoreProductViewController *controller = [[SKStoreProductViewController alloc] init];
[controller loadProductWithParameters:parameters completionBlock:nil];
[self presentViewController:controller animated:YES completion:nil];
}
You can also use another parameter ct, the campaign text, that you can optionally add to any link in order to track sales from a specific marketing campaign. For example, the link below has added a campaign tracking parameter for a blog link. You can name the campaigns anything you choose, but the ct value may not be longer than 40 characters:
If you want to build a service base on affiliation, you will need to find links to useful content on iTunes. There are some tools and APIs to help you:
The lookup API is really useful: given an app id, you will get the description, URL of app icons, screenshots, price, average rating, user rating count etc… More information on the lookup API in Useful iTunes Web Services.
Enterprise Partner Feed
Apple gives you also a much more powerful tool: a direct access to the entire App Store metadata database, called Enterprise Partner Feed, or simply EPF. EPF provides a daily access to the iTunes content entire database (apps, movies song) and you can use this tool to build your killer app: it’s much more powerful than iTunes Search API but need more work.
EPF is daily updated, so you can use it to extract useful content and add affiliation. Note that any links extracted from the database must be used with an affiliate token.
Access on the database requires login credentials and an active partnership with the affiliate program. You can apply to get access by filling a request at http://itunesaffiliate.phgsupport.com/anonymous_requests/new (don’t send request to EPFrequest@apple.com, the mail is no longer in use). You will receive an answer in a few days.
I’ve been a huge fan of the first edition (targeted to Django 1.5), it has been (and still is) an invaluable companion in learning how to develop with Django. The first edition contains a lot of tips, tricks, patterns, code snippets, techniques and more important best practices: how to organize your settings, how to design your models, how to test your Django app etc…
In my opinion, this is not a book for starting to learn Django: it’s value is really in the knowlegde and experiences that Daniel and Audrey have learned over the years, it’s about best practices. If you’re new to Django, this book will be challenging, you should at least have gone through the Django tutorial.
If you work in a big company, chances are good that you’be been fighting your proxies IT guys, in particular if your proxy is a NTLM one.
You should configure your login/password proxy in the System configuration of OSX. That way, every OSX application can read your proxy settings and use it.
While this method is really simple, I’ve found a lot of applications that doesn’t work well with my company’s NTLM proxy, even if I’ve configured it in the System Preferences:
the iOS Simulator: doesn’t use the System proxy configuration (Xcode 5.0.2 /Mavericks),
Jenkins: can’t upgrade / download plugins through the web interface,
A lot of curl based tools: git clone https://github.com/AFNetworking/AFNetworking.git etc…,
cntlm is a simple command line that stands between your applications and the corporate proxy, adding NTLM authentication on-the-fly. Your OSX system uses a local proxy (by default localhost:3128) provided by cntlm and cntlm does the hard work of always adding the NTLM authentification. You can use cntlm in interactive mode i.e. in a shell that you launch and stop on demand, or install it to be started at launch with your session.
Installing and configuring cntlm is a matter of minute and, after, you will say goodbye to your proxy issues.
The best tutorial I’ve found on cntlm is from _oho: Howto Set Cntlm on Mac OS X. Installation and overview are simply described and there are some really good tip and tricks. If you work behind a corporate proxy, be sure to read it, your life will change!
If you download the reachability sample, and launch it on an iPhone 5s, with an active cellular connection, you will see this result:
Everything looks OK, the cellular connection is well recognized.
Now, if you modify the sample build settings to take advantage of 64-bit architectures
(Target > Build Settings > Architectures) from "Standard Architectures (armv7, armv7s)" to "Standard Architectures (including 64-bit) (armv7, armv7s, armv64)"
and run the sample, you should see this:
Reachability thinks that there is no active cellular connection! I think it’s a serious bug, I’ve certainly missed something but just recompiling Reachability for 64-bit shouldn’t produce a different result. I hope I’m wrong, but in the meantime I’ve filled a bug report (rdar://15880397) and you should too!
