Forum, I for one struggled at first, to process everything in related to the 'Easy In App Purchase' plugin. That included creating the In App purchases in iTunes Connect, aswell as linking the Buzztouch screens to these In App's purchases. I have created this short guide to hopefully help people out. http://www.randalldesigns.co.uk/EasyInAppPurchase.docx Hopefully people find this useful. Thanks Steve

I'm so glad you did this; I was hoping someone would before I started working with in App Purchases, lol! Thanks a million Steve! You're a rock star!! :) Cheers! -- Smug

cool, finally, thanks, will read now.

Fantastic. Thanks a lot. You don't happen to know the steps for an in app purchase for a new app. I mean instead of unlocking a screen, it pays for a new "full" version of the app, and downloads it? Thanks, Miguel

I've not personally tried it but wouldn't you just link them to the App Store?

Thanks Bonzo. How do you mean, link them to app store? If its a direct link, it would open app store and the user would have to pay again, right? Following your tutorial. It works fine, but, do you know of a way to have the iap plugin disappear after its payed? I mean, its a bit annoying having to always go through the iap screen. Thanks.

According to theMonster(plugin designer) this is now standard. It was the only was to fix one of the bugs that was in v1

The problem with that procedure, is that if you don't have internet access, your user will not be able to go pass the iap screen. that could be a problem. A user unlocks a content and can then only access it if he's online?? What did you mean by direct link to app store? Thanks

I never noticed that before! that sucks.....wonder if the designed knows that? all i meant was you would have a link direct to the app store using the open with native app feature. then they could download the app

There is one workaround for the in app purchase FYI that worked in my app: I removed the Back button from the purchased screen and only included a "home" button. For this app I configured left nav button same as the right nav button (i.e. add the left side button based on the choice in screen data, defined in config file) so this worked out good as I did not want Back buttons on all screens. then by changing isAlreadyPurchasedShouldGoToScreen to equal YES, the iap screen will pass directly to the purchased screen, even if offline, and from there the user can only go home. If you need more details just let me know.

Sounds interesting. Can you explain more with code snippets please?

Sure...for the back button I did the following: in BT_viewUtilities.m, I replaced the chunks of code for if([theViewController respondsToSelector:@selector(navLeftTap)]) and just below this code for //navLeftTap or closeChildApp with the code found further down for "//add the right side button based on the choice in screen data," but configured for "left" instead of "right". This way the navbarleftbutton is defined in the config file for each screen. For example, include the details in the config file such as: "navBarLeftButtonType":"details", "navBarLeftButtonTapLoadScreenNickname":"XXX", "navBarLeftButtonTapLoadScreenItemId":"XXX" Note this will apply throughout the app however for all screens. For the iAP purchased screen/menu, I did not define any navbarleftbutton data, but included a "home" button for the rightnavbutton. Then in easy_in_app_purchase.m, under viewDidAppear method, I changed [self isAlreadyPurchasedShouldGoToScreen: to equal YES instead of NO. this worked for the format of my app, but I'm sure there are likely other ways to remove back button and not affect all screens.

Hi guys I think I have solved the offline screen accessing problem and want to explain how and why. The problem with being offline is that when you approach your iAP screen(the one on which your users see the buy button etc) there is a "wheel of death" that says please wait. This wheel blacks out the screen making it impossible to press on any of the buttons. So what I did was, in my easy_in_apppurchase.m file around line 52-56 //viewDidLoad -(void)viewDidLoad { [self.pleaseWait setHidden:YES]; [BT_debugger showIt:self:@"viewDidLoad"]; [super viewDidLoad]; where it says self.pleaseWait setHidden : NO]; I chaneged it to a yes. This means that the wheel is now going to be set hidden at all times and you can always press your buttons since the screen is not blacked out anymore. The only problem that remains is that when you are offline the description and title of your iAP does not come from itunesconnect you have to set it up yourself in buzz touch. I hope you guys understand.. Thanks Incase you require any further explanation that I might be able to give please contact me with my email address @ [email protected]

Silly question..... Does the inapp purchases work for you on iPad? When I try on iPad, clicking on the buttons to buy or restore don't do anything. They look like they are being pressed but nothing happens?? Thanks

I tested my iAPs on the iPad simulator in xcode and they worked perfectly so I guess thats about all I can say.

My fault (I guess), somehow I lost the 'sendEvent' on the buy and restore buttons.

Sure, incase the iAP problem has been solved just give us a shoutout so that we can use this post as a reference to any further (similar) problems.. Thanks

so by setting the description up yourself, means i would need to create a .txt or .html file and point to the file name in the 'Product description URL box? i cannot physically type the text into the control panel

I guess not, I saw that too, it's a bummer that you've gotta point it to another file.

@Bonzo - I had the same issue with the iPad...see this post for a fix: https://www.buzztouch.com/forum/thread.php?tid=2B2F443B904C35E372C65C4&command=isSearching&currentPage=1&topicTitle=in%20app%20purchase&createdBy=&repliedBy=&minViews=-1&maxViews=-1&minReplies=-1&maxReplies=-1&forumCategory=

If I. don't want to use the plugin (I just don't go to the buzztouch setup step right?) and how the in app will be available? only by app store?

@armacfan, did you get it to read a local html file? I changed the No to Yes, then created a HTML file with some text, which i added into xcode in the BT_docs folder. Sent the build to my phone. the spinner no longer appears but nor does a description

I can't say anything about that, I havn't tried it but maybe it might work with a normal .txt file. Not 100% sure though. I apologise. Thanks

Hello, I'm a newbie and wondering if anyone can assist with my query?... I'm trying to implement the Easy IAP plugin in a free version of my app to give people the option to upgrade to the paid version. My intention is to use the IAP plugin to send people directly to the paid product in the App Store when they click on the 'Buy' tab. Is it possible to make this happen? I've read through lots of forum feeds and also gone through the short guide link posted above by Bonzo, but am quite confused on what to do. Thank you, Natasha.

G'day Natasha, I don't believe what you are requesting, is doable with this plugin. I believe you could use it to disable ads. (for example. you have a free version with ads. then you can use it to make a non consumable purchase which then disables the ads to make it add free) This only works if your app is the same and your full version doesn't have more functionality. I have created my own plugin (if you are self hosted) that enables you to add a button somewhere in your app, that brings a pop up, that would display the full version of your app (as long as its in the appstore) and they can purchase it from within your app without having to leave the app. I am willing to share if interested. (Its currently in review for the plugin store) Hope this helps Steve

thats awesome @Bonzo. Do you have a working app that you can show? hopefully it will be approved soon!

Hi Bonzo,thanks for your feedback. I'm not up to self hosting yet. But yes, I would still be interested to see your plugin so I might be able to give it a go in the future.

I have it in 2 apps that are currently waiting for review. I am also hoping it will be approved soon :) ive posted in the forum to ask how people create those demo video's. if i had the software to do it then i will create one showing it in action