In this article, I’ll take you through the bare minimum steps to setup git on your computer and start XCoding.

Before we delve into the detailed steps, a couple of words about Git.
Git, unlike SVN is a distributed version control system. which means, when you commit a repository, you actually don’t commit to the central repo. In Git, every user has his own local repo and he at his own will can “push” changes to the central repo.

Once you get this concept of distributed source code control, Git is a cakewalk. Believe me.
Now, let’s get started.

Step 1: Install Git.

Yeah, a no brainer step, pick up the installer from here

Step 2: Generate your keys

Git uses a private/public key authentication to verify YOU before you access the remote git repository.
ssh-keygen -t rsa -C ""
Just keep on pressing enter for any question it asks till your public key gets generated

Step 3: Copy keys to clipboard

But, why is this a separate step? Because you can do it easily through command line.
cat ~/.ssh/id_rsa.pub | pbcopy

Type this to “copy” the public key to clipboard (Equivalent of Cmd + C)

Step 4: Add this public key to your remote repository

Update your public key into your remote Git Repository. All Git Repositories like github, sourcerepo, beanstalk provide a interface to add your public key to your user profile.
That’s it! Now you can start using Git. See it’s that simple.

Now we shall start using Git to commit your changes and push it to the central repository.

Step 5: Create your first Git local repository

To get started, create a directory and cd into that directory

mkdir GitFolder
cd GitFolder

Step 6: Initialize your local repository

Initialize a git repo in that new directory by typing in the following command.
git init

This command initializes the empty directory you created with a git repository. Unlike SVN, git repositories are not stored in some different location. The git repo is stored within the folder you created inside a hidden folder called “.git”

Step 7: Clone a remote repository

git clone "" .
Now clone your remote URL to your current directory (.)
(Be sure to type the last “.”, it’s not full stop)

That’s it.
Your GitRepo is now on your local drive.

Step 8: Making your first commit

Now, let’s make a change and commit this to your local repo. For this, edit any file in the project and come back to Terminal.
Type
git diff

You should see the changes you made on the console. To commit these changes, type
git commit -a -m "Your commit comment"

Step 9: Pushing your changes to remote repository

Now, remember that, Git is a distributed version control system, so, these changes aren’t yet available to other users/contributors of the same remote repository. You must “push” these changes back to the remote repository. For doing this,
you have to configure a remote location using the following command.
git remote add "remote location name" ""
Your remote location starts with ssh:// and looks like this
ssh://github.com/foo/bar/MyGreatiPhoneApp.git
Your “remote location name” can be anything and most tutorials like those from github tend to use “origin”

Step 10:”Pushing” your local commits

Now that you have configured a remote location,
git push "your remote location name" master
or in short,
git push origin master

Now your code has been successfully committed to the central repo.

Step 11: “Checking out” a remote repository

“Checking out” from a git repository is called as “pull”. The command for that is very similar
git pull origin master

Note that cloning a git repo is to copy the entire repository where as pulling just updates the latest incremental changes. Unfortunately (or fortunately) there is no equivalent of clone in SVN. Just remember that you are doing this step because Git is a distributed revision control system.

Step 12: Setting up a default remote location

You can setup this location permanently as your default remote location by typing in this command
git config branch.master.remote "your remote location name"

From now on, you can just type git push and git pull to commit and retrieve changes to and from the repository.

Step 13: Adding exclusions

Every project always contains some auto generated “build” folders that need to be excluded from being committed. To do this, you use a “.gitignore” file. Create a .gitignore file and type the relative directory addresses one per line and Git automatically ignores them. My .gitignore file usually looks like this
build/
.gitignore
fbconnect/src/build/*
MyiPhoneApp.xcodeproj/mugunthkumar*

The first line is to exclude the build directory, the second line is to exclude this .gitignore file and the third line is to exclude the fbconnect (or any third party library)’s build folder and the last line is to exclude your personal XCode editor settings from being committed into the repository.

So, that’s it for setting up Git for your great iPhone App.

Git has even more powerful tools to branch and merge locally and pushing/ignoring a certain branch. But I will leave that for another post.

Happy Gitting.

–
Mugunth

©2010 MK Blog. All Rights Reserved.

No related posts.

As usual, you prepare a AdHoc build and zip the .app bundle, attach it to the email along with the mobile provisioning profile and send it to your customer. On macs, things are pretty straight forward. On Windows, however, your customers are prone to fall into these common pitfalls which might cause a troublesome nightmare for you.

First Pitfall:
Extracting the .zip file you sent using Windows Explorer’s built in Compression Engine.

I repeat. DON’T DON’T DON’T extract the zip file using the Windows’ explorer’s built in “Extract Here” command. The default compression engine bundled with Windows messes up the CRCs by adding temporary files into the .app bundle. Ask your testers to use a better de-compression tool like 7-Zip, WinZip or WinRar.

Second Pitfall:
Opening the .app folder out of “curiosity” to “see” what’s inside.

Never double-click and “open” the extracted .app “folder” (On windows the .app bundle appears as a folder) . Windows is a sh**. I agree. It automatically creates a “Thumbs.db/Desktop.ini/folder.htt” (some created by Virus, some by Windows) file whenever you access a folder and that again changes the CRC of the bundle. Just drag the .app “folder” immediately after extracting into iTunes. Also drag the provisioning profile into iTunes and sync the app.

If you think your users’ might not follow all these steps, you can send them the .IPA file instead of the compressed .app bundle. This .IPA file can be generated on your mac by dragging the .app bundle into iTunes. When you drag the .app bundle into your iTunes library, it internally creates a .IPA file. This IPA file can be located in Finder from iTunes. Just Cmd click your app on iTunes and click “Show in Finder”. Send this .IPA file (and the mobile provisioning file) to your testers.

Hope that clears the air around AdHoc provisioning on Windows.

–
Mugunth

©2010 MK Blog. All Rights Reserved.

No related posts.

For example the below code works perfectly on iPhone OS 3.1 and below but fails on iOS 4.

- (void)start
{
[self willChangeValueForKey:@"isExecuting"];
_isExecuting = YES;
[self didChangeValueForKey:@"isExecuting"];

NSURLRequest * request = [NSURLRequest requestWithURL:_url];
_connection = [[NSURLConnection alloc] initWithRequest:request
delegate:self];
}

Seems like Apple has made a change where in if the NSURLConnection’s initWithRequest method is called from a thread that’s not the main thread, it doesn’t start downloading the URL contents immediately. The bug fix for this issue is fortunately simple.

- (void)start
{
[self willChangeValueForKey:@"isExecuting"];
_isExecuting = YES;
[self didChangeValueForKey:@"isExecuting"];

//iOS 4 bug fix
if (![NSThread isMainThread])
{
[self performSelectorOnMainThread:@selector(start)
withObject:nil waitUntilDone:NO];
return;
}
}

Hope this post solves your problem.

–
Mugunth

©2010 MK Blog. All Rights Reserved.

Related posts:

1. Consuming a RESTful Service (bit.ly) in an iPhone Application bit-ly-rest-api-objective-c Introduction Of late, many programmers who develop for Windows/Linux...

Prior to iPhone OS 4, developers have to depend on

[[UIApplication sharedApplication] openURL: @"sms:12345678"];

The problem with this is not just that it closes your app, but there is no way to specify the body content of the SMS. Secondly, you are restricted to send the SMS to only one person. However, with the new MessageUI SMS controller, you can send SMS to multiple people at the same time. You can also pre-populate the SMS body field.
Developers of famous apps like Whatsapp Messenger, copy the SMS text content to clipboard and open the SMS app to allow users to paste the content. But with this newly allowed In-App SMS sheet, users can send SMS without quitting the app.

So, Let’s get started.

Step 1:

Import the MessageUI Framework into your project and #import the header file into the “.h” file of your controller where you want to open the In-App SMS sheet.

Step 2:

You might already have a button handler IBAction where you want to send the SMS. If not create a Button on your XIB file and write IBActions for it.

Step 3:

The real code

-(IBAction) sendInAppSMS:(id) sender
{
	MFMessageComposeViewController *controller = [[[MFMessageComposeViewController alloc] init] autorelease];
	if([MFMessageComposeViewController canSendText])
	{
		controller.body = @"Hello from Mugunth";
		controller.recipients = [NSArray arrayWithObjects:@"12345678", @"87654321", nil];
		controller.messageComposeDelegate = self;
		[self presentModalViewController:controller animated:YES];
	}
}

The most important part here is the line [MFMessageComposeViewController canSendText].
When sending a in-app email, you can choose to ignore this (atleast as of now) because most of the devices would have upgraded to iPhone OS 3 and all those devices would have the ability to send in-app email. However, the same doesn’t apply to SMS. Remember that even if a device is running iPhone OS 4, if it’s an iPod touch, it will never be abel to send SMS within app.
In this case, I have used a if condition to send the SMS. Practically speaking, you should enable/disable the button the user taps to send the sms based on this. You can add the code that does this in your viewDidLoad method.

Secondly, you have to set the messageComposeDelegate to self and not delegate. If you set the controller.delegate to self, you will not get the didFinishWithResult callback and the In-App SMS sheet will not close.

Step 4:

Implement Delegate Callbacks.
In your header file, implement the callbacks, MFMessageComposeViewControllerDelegate and UINavigationControllerDelegate. If you don’t you will get a warning at the line,

 controller.delegate = self;

You have to handle a callback method of MFMessageComposeViewControllerDelegate so as to dismiss the modal view controller.

- (void)messageComposeViewController:(MFMessageComposeViewController *)controller didFinishWithResult:(MessageComposeResult)result
{
	switch (result) {
		case MessageComposeResultCancelled:
			NSLog(@"Cancelled");
			break;
		case MessageComposeResultFailed:
			UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"MyApp" message:@"Unknown Error"
														   delegate:self cancelButtonTitle:@”OK” otherButtonTitles: nil];
			[alert show];
			[alert release];
			break;
		case MessageComposeResultSent:
 
			break;
		default:
			break;
	}
 
	[self dismissModalViewControllerAnimated:YES];
}

That’s it. Your app should now be able to send SMS using the new Message UI sheet.

Where the heck is MMS in this tutorial?

As on date, the MFMessageComposeViewController doesn’t support sending MMS. The controller.body is a NSString and setting a NSData pointer obviously crashes the app. Hopefully, one day, Apple will allow sending In-App MMS and I’ll probably blog about that too…

©2010 MK Blog. All Rights Reserved.

Related posts:

1. iPhone Tutorial: Elegant way to send formatted In-App email By now, most of you know how to send emails...
2. iPhone Tutorial – UISearchDisplayController with NSPredicate Though UISearchDisplayController is seemingly easy (and yes it’s easy), apart...
3. iPhone Tutorial – Enabling reviewers to use your In-App purchases for free In-App purchases is a great way for developers to upsell...

iPad

At the time of writing, Elements costs 14.99$. To most of us, it might seem a bit pricey. While a similar printed book, which might not even interactive might cost more, the iPad version is priced comparatively lower especially given the effort the developers have put in the app. (and hence the value you get as a consumer). As the narrator explains, the Elements app is not just an electronic version of the paper book, but something that have been remade completely. Apps like these that take advantage of the huge multi-touch screen is going to be a huge success with the users. Apps like these will be used by users longer than they use a similar iPhone app. A longer usage cycle translates to higher customer satisfaction. So you might not say, “Did I pay this much for this crap?”.

Next category of apps like these will be for education related apps for young, growing kids. You might have got expensive “animal” book that teaches your kid how the animal looks. Now with the iPad, there would be an app that meows like a cat, barks like a dog and roars like a lion.
Or you can get a slate and chalk app like this for a dollar which your kids can draw on.

If you are a Asian (Chinese/Japanese), you could download an app that allows your kids to draw over a dotted Kanji and teach them how to write a Kanji the right way. I use Kanji Flip and Japanese Flip on iPhone to learn Japanese Kanji.

Kanji Flip Helps you learn Japanese Kanji on your iPhone

Probably the developers might come up with an iPad equivalent soon.

The level of interactivity is much higher that, software on these devices becomes more and more intuitive and this could potentially change how our future generation youngsters are molded. As the media industry converges with the software industry, there isn’t a reason that stops you from becoming a Apple developer.

Now, If Apple could successfully convince e-book publishers to use their platform like they did with the media industry, electronic books will be the next big thing in this decade. Students would find themselves renting textbooks during the course period rather than buying them. Blackboard has a iPad app that helps students stay in touch with what’s happening in class. So if your university uses this software, (I know Nanyang Technological University uses it) you can use this iPad app to go through the courses and course materials.

History has proved that, it’s not the product that endures. It’s the killer ecosystem that sustains the product. For example, in 1980s, the sales of IBM PC was boosted just by the software called Lotus 1-2-3. The sales of XBOX 360 was sustained just by one killer game, The Halo Series. On a business sense, these products are called as killer apps. Today we buy computers not for the processor/hardware inside but for its ability to run the software of our choice.

Successful apps like these will drive the iPad as the next generation computing platform and as Apple already says, there is an app for anything, only on the iPhone, that might just be true for the iPad as well.

–
Mugunth

©2010 MK Blog. All Rights Reserved.

Related posts:

1. Save As vs Exporting – Why Apple excels at UI Design? Most users think, Mac UI is all about slick graphics...
2. Elements of Usability Design: OK/Cancel vs Cancel/OK – Is it just a matter of taste? OK, many of the programmers would have been confused as...

[picker setMessageBody:emailBody isHTML:YES];

There are some cases that this method that this method doesn’t take care of. In short, this method works great for sending “Tell a friend about this app” email. But if your app needs much more sophistication, especially, if it needs to email data created by the user, you can follow the approach I suggest. Using this method, you can also adapt your code for International support and send the same email in multiple languages without any “hard-coding”

Though the method promises some great features, it is ridiculously simple.

Step 1:

Create a HTML File with the contents of your email and add it to your project. You should NOT create any css or link it to any external CSS files. All your styles whether embedded withing the <STYLE> tag or kept as a separate CSS file will mostly be stripped by email clients. The reason could be because email clients don’t want your CSS to mess around with their client CSS. Read this article for more details. A sample is given below.

Step 2:

Insert placeholder markers within your HTML file. Your HTML file should look something like this.

<font size = '1' color= "#222222" style = "font-family: 'Lucida Grande', 'Lucida Sans Unicode', Helvetica, Arial;"><i>//TEXT_PLACEHOLDER//</i></font>
<font size = '2' color= "#000000" style = "font-family: 'Lucida Grande', 'Lucida Sans Unicode', Helvetica, Arial;"> Have a great day! <br/>//FRIENDNAME_PLACEHOLDER// <br/></font>

The bold markers are the placeholders. You can assume them to be variables in the email. We will be replacing them later.

Step 3:

Do exactly the same steps for sending an in app email explained in one of my previous tutorial, but rather than hardcoding the email body like this,

NSString *emailBody =
[NSString stringWithFormat:@"%@\n\n
Sent from <a href="%@">MyGreatApp</a> on iPhone. <a href="%@">Download</a> yours from AppStore now!
", content, pageLink, iTunesLink];

Read it from your HTML File you created in Step 2.

NSString *langString = [[userDefaults dictionaryRepresentation] objectForKey:@"NSLocaleCode"];
NSString *emailFileName = [NSString stringWithFormat:@"email_%@.html", langString];
NSString *emailFilePath = [[[NSBundle mainBundle] resourcePath] stringByAppendingPathComponent: emailFileName];
NSString *body = [NSString stringWithContentsOfFile:emailFilePath encoding:NSUTF8StringEncoding error:nil];

Note that, I’m appending the locale code with the email filename. That means you should create your email file by name email_en_US.html and similarly for other language files.

Step 4:

Replace placeholder texts with your contents generated within the app.

body = [body stringByReplacingOccurrencesOfString:@"//TEXT_PLACEHOLDER//" withString:myText];
body = [body stringByReplacingOccurrencesOfString:@"//FRIENDNAME_PLACEHOLDER//" withString:myFriendName];

The values myText and myFriendName should be passed to this email function.

With this architecture in place, you can format your email, change language and do a lot more without much changes to your code. After all, writing cleaner code is more important in the long run.

–
Mugunth

©2010 MK Blog. All Rights Reserved.

Related posts:

1. iPhone Tutorial: How to send In-App SMS Officially, iPhone OS 4 is out of NDA and I...
2. iPhone Tutorial – Enabling reviewers to use your In-App purchases for free In-App purchases is a great way for developers to upsell...
3. iPhone Tutorial – UISearchDisplayController with NSPredicate Though UISearchDisplayController is seemingly easy (and yes it’s easy), apart...

“The version of iPhone OS on “ABC’s iPhone” does not match any of the versions of iPhone OS supported for development with this installation of the iPhone SDK”

So does that mean, you should re-install the SDK? Just like me, you will probably have confusions like,

Will installing it corrupt or overwrite your 3.2 beta?

Should I re-install 3.2 beta again?

I too had these. Fortunately, I decided to hack things myself and got the 3.1.3 working without downloading the entire SDK. This is how I did. Type the following command into your terminal.


ln -s /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.1.2\ \(7D11\) /Developer/Platforms/iPhoneOS.platform/DeviceSupport/3.1.3


Now quit and restart XCode. Voila! you have effectively “fooled” XCode! and you have saved countless hours which you can effectively use on programming another cool app!

Note that this hack will work *any* minor OS updates. However, if you are using a feature specific to the new version you will probably find yourself in trouble. In other words, don’t try to apply the same technique when 3.2 or 4.0 launches.

–
Mugunth

©2010 MK Blog. All Rights Reserved.

No related posts.

Recently, I was using Microsoft’s Excel to edit a dozen large  CSV files. As a matter of fact, in Excel,  whenever you save “anything” you do as a CSV,  you will practically lose out features that aren’t supported natively by the underlying file format. For Example, CSV doesn’t support coloured cells. So when you colour a cell, and try to “save” it as a CSV, Excel pops up this dialog.

Saving as CSV loses of "certain" features

When you click “Yes”, all that Excel does is to “export” whatever content your file has into what the underlying format can support. So since, excel supports coloured cells but CSV doesn’t it ignores your colouring and proceeds saving it to CSV. Excel even goes one step far and doesn’t clear the “dirty flag” because, Excel hasn’t saved *every* change you made into the CSV.

Sounds good so far. But what’s really wrong here? The real problem is, Excel gives you a sense of feel that “everything” have been saved and you are safe. Things become bad when you quit Excel. Because the dirty flag isn’t cleared and the file haven’t been saved completely, Excel prompts you to “save” the file again. Specious, not wanting to take chances, some users like me, save the file again. Again the same thing happens and the end user is still just dumbfounded and asks, But, why the heck should I save it again?

Microsoft UI designers have failed to understand the end users. In this case, it’s because Excel fails to speak the users’ lingo. According to the user, when he “saves” a file, he saves a copy and he is contended that he can always re-open when something bad happens. But excel just “exports” the file into CSV format and tells the user that it “saved” the file (when it in fact didn’t). As a result what happens is data loss. No not just cell colours, in cases, when the users doesn’t know that CSV doesn’t support multiple sheets, excel doesn’t export (or save) the second sheets data and the user just loses the entire content from the second sheet. Disaster! In one of the cases where I work, a co-worker of mine, has got used to these prompts which Excel shows after you “save” your file as CSV

Prompts user to save the "saved" file again

and he just closes Excel assuming that these prompts are nothing but “bugs” in Excel. (Yeah see, he is a half techie and a little knowledge is dangerous.) Things went fine when he didn’t lose data, but just lost some formatting here and there. But the real disaster happened when his second sheet containing over 1000 lines and 3 hour work was lost.

Now, lets’ see how Numbers, the equivalent software from Apple handles this.

Apple doesn’t even include CSV or other “lossy” formats in the save as sheet. That doesn’t mean, Numbers can’t “save” your data as CSV. But rather Apple calls it as “Export”. Files you export as CSV aren’t yet saved. So, when the user quit Numbers, and get a prompt to save the document, he will not confused.

Because Microsoft does it this way (wrong way), other software makers like Adobe too make the same mistake. Photoshop “saves” a file as PNG and still give you a sense of feel that you have saved the file. Another such example is audacity and paint.net and even those “save as PDF” plugins. They actually don’t “save” your data, but rather export it. Apple gets it right, but the whole world gets it wrong, Unfortunate!.

©2010 MK Blog. All Rights Reserved.

Related posts:

1. Elements of Usability Design: OK/Cancel vs Cancel/OK – Is it just a matter of taste? OK, many of the programmers would have been confused as...
2. Usability Analysis – Office 2010 on Windows 7 If you were following my tweets, you might be knowing...

Follow Cost is a interesting and powerful statistic that helps you check the “cost” you would incur by “following” a person on twitter. This is a very useful statistic that I think every twitter client should adopt.  Tweetie for iPhone was the first to implement follow cost and I use this feature of tweetie to check whether a follower is “worth the pain” (as follow cost puts it).

In short, Follow Cost gives you an approximate count of the number of updates a person tweets in a day. As a thumb rule, I don’t follow anyone with a follow cost of over 40. A celebrity with a high follow cost is @guykawasaki. (80+ at the time of this writing) His tweets are interesting, but is it worth the pain? Depends. To me, definitely not.

The API

Follow Cost has a relatively simple API. But unfortunately, even after 3 months of Tweetie 2 launch, no other twitter client has implemented. You just have to make a GET request to followcost.com server with the twitter username as follows.=


http://followcost.com/<username>.json

The resulting output is a json formatted string which can be parsed using any JSON Framework.

Objective C Code

To make life easier, I wrote a helper class MKFollowCost. To use the class, first download the JSON framework and follow their installation instructions. If you are writing a twitter client, chances are that, you would probably have done this. Download the code from below and drag the two files, MKFollowCost.h and MKFollowCost.m into your project.

You can instantiate a followcost object by
MKFollowCost *followCost = [[MKFollowCost alloc] initWithTwitterName:@"mugunthkumar"];
All of the variables like, milliscobles, tweets per day etc, can be accessed from this object. The object is designed to be embedded without your Twitter Profile object.

Downloads

FollowCost Objective C Wrapper: FollowCost v1.0

Rights

You can use it in your own Twitter client, royalty free. Attributing me is upto you. However, if you modify the source code, please make it open source.

©2010 MK Blog. All Rights Reserved.

Related posts:

1. Consuming a RESTful Service (bit.ly) in an iPhone Application bit-ly-rest-api-objective-c Introduction Of late, many programmers who develop for Windows/Linux...
2. bit.ly wrapper for Objective-C/iPhone Continuing from my part 1, in this section, we will...
3. iPhone Tutorial – Enabling reviewers to use your In-App purchases for free In-App purchases is a great way for developers to upsell...

After raising the issue to Apple, I even got a official reply that it’s not possible currently to allow reviewers to use your in-app purchases for free.

However, developers’ creativity knows no bounds. In this post, I’ll present a method to allow reviewers to use your in-app purchases for free without having multiple versions of the same app on the app store. The source code for the same is also available royalty-free (as always) for using it in your own apps. Before diving in, it’s advised that you read through my previous tutorial on how to do in-app purchases

Focus

As I previously wrote, you can sell consumables, non-consumables and subscriptions using the in-app purchases model. This article is focussed primarily on consumables and non-consumables. However, you can extend it to subscriptions as well by adding a bit more server side PHP programming. This post however focusses on adding this feature to consumable and non-consumable items only.

A Quick Recap

By now, you must be knowing the flow of a in-app purchase request. If you don’t, read through my in-app purchases tutorial. As a recap,

1) You list the items available for sale from your store to the user.

2) When the user chooses a feature, you prepare a SKPayment object and add it to the queue.

3) Listen to notifications and record the purchases within your apps’ NSUserDefaults.

Or it’s even more simple if you had used my MKStoreKit.

The Idea

The idea here is to maintain a list of device IDs on the developer server and check whether the current device is exempted to use the feature without purchasing. If the device is allowed, rather than initiating a purchase, temporarily set the variables as if the transactions were made.

The complete source code, MKStoreKit V2.0 is attached at the end of the post.

You should be glad to know that, you don’t have to make changes to your calling code to add this feature.
In MKStoreKit, there is a function called buyFeature which initiates a in-app purchase request. In version 2.0, this function is modified to make a check first to your server (server code is also attached to this post) passing the UDID of the current device. If your server responds with a YES, it activates the feature temporarily without “actually purchasing”. This will enable your reviewers to review your app without buying your in-app purchase.

- (BOOL) canCurrentDeviceUseFeature: (NSString*) featureID;

This is the function that is called. Currently it checks the server mentioned in the variable ownServer (presently set to nil). To enable this function, you have to do the server side changes as explained in the next step.

Server Side Changes

Setup a database with two tables setup in your server. One table for storing a list of available products and another for storing new review requests as they come in.

The products table has the following fields
productid productName productDesc

The requests table has the following fields
udid productid email message status lastUpdated

You can use the SQL file attached to create these tables. Add a user to your MySql database and fill in the user id and password into the two php files.

Copy the server files from the ServerCode folder to some location like

http://api.mycompany.com/inapp/

change the “ownServer” variable in MKStoreManager.m to

http://api.mycompany.com/inapp/featureCheck.php

The featureCheck.php file checks the requests table for the UDID and the featureID. If the status of that row is 1, it returns YES. If your server returns YES for a particular UDID, the app activates the purchase for the current session without initiating a StoreKit purchase. Note that, this featureCheck happens everytime the app is started. Hence, if you deactivate a UDID on your server after the reviewer has finished reviewing, he will not be able to continue using it for free (Which means, you have actually given the reviewer a sneak-peek to your feature. Even if he likes it, he has to buy it)

How to send your review request?

There are atleast three ways of doing this.
One way is to ask your reviewers to send the UDID to you by email. You can ask them to use the Ad Hoc Helper by Erica Sadun You can then manually add it into the database using the AddDevice.html (present in the Server Code folder)
Second way is, You can “pretty up” the AddDevice.html and host it somewhere in your server. Send a link to this to your reviewers for filling their UDID/Product ID.
Third, as in my case, I’ve created a separate iPhone App for doing this. The only reason for doing so is, filling the UDID is very very cumbersome and error prone. If anyone knows a way to read the UDID of a device from a webapp, do let me know. (The big5 code didn’t work for me)

Going forward

I understand that all this server side setup is quite cumbersome. The server code isn’t even polished like the MKStoreKit. If Apple approves this method (which I will know in another 20 days), In MKStoreKit 3.0, I’ll probably throw of the whole server side code and replace it with a much elegant method by using a Google Spreadsheet. I haven’t yet digged around with the spreadsheets API. This way, you can implement the same feature without even owning a server .

I might as well add in features to migrate your existing customers who use your pro version to the version with in-app purchases. Stay tuned!

Source Code (Much awaited)

MKStoreKit V2.0
If you cannot successfully use this, you can hire me to do it for you. I usually freelance through oDesk.com

©2010 MK Blog. All Rights Reserved.

Related posts:

1. iPhone Tutorial – In-App Purchases Last week, Apple announced that in-app purchases will be available...
2. iPhone Tutorial – UISearchDisplayController with NSPredicate Though UISearchDisplayController is seemingly easy (and yes it’s easy), apart...
3. iPhone Tutorial: Follow Cost API and a open source wrapper What is Follow Cost? Follow Cost is a interesting and...