The objective of the document is to explain the steps involved in doing auto renewal payment in PayPal using its Mobile Payment library for android mobile.

Steps to get confirmed PreApproval Key

1. The first step towards integrating PayPal with android application is that we need a PayPal sandbox account for testing. So create new sandbox account if you don’t have one from following URL https://developer.paypal.com/cgi-bin/devscr?cmd=_signup-run
2. Sign in with the user id and password.
3. Create Test accounts for both buyer and seller. You will get the API credential while creating seller account, those API credential will be used for getting preapproval key and payments.
4. From your Local server send the preapproval request to paypal using the following parameters. You should use your account details and API credentials here.
   1. requestUrl: https://svcs.sandbox.paypal.com/AdaptivePayments/Preapproval
   2. requestMethod: POST
   3. requestBody: requestEnvelope.errorLanguage=en_US&cancelUrl=http://www.bytelyte.com/PayPal_X_NVP_tester.php?cmd=test&currencyCode=USD&endingDate=2011-11-11&maxAmountPerPayment=30&maxNumberOfPayments=4&maxTotalAmountOfAllPayments=120&pinType=NOT_REQUIRED&returnUrl=http://www.bytelyte.com/PayPal_X_NVP_tester.php?cmd=test&startingDate=2011-09-21&senderEmail=your buyer mail id
   4. headers: charset”,”utf-8″,”Content-Type”,”text/xml”,”X-PAYPAL-DEVICE-IPADDRESS”,”127.0.0.1″,”X-PAYPAL-APPLICATION-ID”,”APP-80W284485P519543T”,”X-PAYPAL-RESPONSE-DATA-FORMAT”,”JSON”,”X-PAYPAL-REQUEST-DATA-FORMAT”,”NV”,”X-PAYPAL-SECURITY-SIGNATURE”,”API Signature”,”X-PAYPAL-SECURITY-PASSWORD”,” API password “,”X-PAYPAL-SECURITY-USERID”,”API UserName”
5. If the above process and parameters are correct you will get a Preapproval key from server as response.
6. Response:{“responseEnvelope”:{“timestamp”:”2011-09-21T02:54:44.020-07:00″,”ack”:”Success”,”correlationId”:”606efc1b8abb0″,”build”:”2142261″},”preapprovalKey”:”PA-81Y46219NL419022F”}
7. This Preapproval Key say PA-81Y46219NL419022F has to authorize by the application. Pass the Preapproval key and merchant name to PayPal MPL from your android application. Here we used “SimpleDemo” android application given by the PayPal MPL library for understanding purpose.
8. The Mobile User should login and agree the PayPal preapproval payment. After the user agreement the preapproval key get authorized and return back to the application.

Steps to make Payment

From your Local server by using the authorized preapproval key you can make a payment using the following parameters.

1. requestUrl: https://svcs.sandbox.paypal.com/AdaptivePayments/Pay
2. requestMethod: POST
3. requestBody: requestEnvelope.errorLanguage=en_US&actionType=PAY&preapprovalKey= Authorized preapproval key&receiverList.receiver(0).amount=30.00&receiverList.receiver(0).email=your seller mail id¤cyCode=USD&feesPayer=EACHRECEIVER&memo=Simple payment example.&cancelUrl=http://your_cancel_url&returnUrl=http://your_return_url&ipnNotificationUrl=http://your_ipn_notification_url
4. headers : “charset”,”utf-8″,”Content-Type”,”text/xml”,”X-PAYPAL-DEVICE-IPADDRESS”,”127.0.0.1″,”X-PAYPAL-APPLICATION-ID”,”APP-80W284485P519543T”,”X-PAYPAL-RESPONSE-DATA-FORMAT”,”JSON”,”X-PAYPAL-REQUEST-DATA-FORMAT”,”NV”,”X-PAYPAL-SECURITY-SIGNATURE”,”API Signature”,”X-PAYPAL-SECURITY-PASSWORD”,” API password “,”X-PAYPAL-SECURITY-USERID”,”API UserName”

If the above parameters are correct the amount mentioned in the “receiver(0).amount=” column will get transferred to the seller account and you will get a Pay Key as response from the PayPal server. You can login in to both seller and buyer account to ensure the above process.

1. Reboot your device

2. Clean your build and rebuild the project and launch the App.

If you get the same problem again add the following options to your procedure:

1. Delete the App from the device

2. Restart XCode.

At times you can get rid of this problem only by Factory Rest of your device.

The format of the URL should be as follows:

jdbc:oracle:thin:@hostname:port:oracle-sid

Another format to use along with  credentials is:(I have not tested this in the App)

jdbc:oracle:thin:username/password@hostname:port:oracle-sid

Thanks to jguru:

http://www.jguru.com/faq/view.jsp?EID=444466

Webinar at Aspire Systems

Join us for a Webinar                                                                         
Theme: 5 things CIOs need to know before mobile-enabling
Date: Thursday, June 2, 2011
Time: 11 AM PST / 2 PM EST

“More than 4 billion people around the world now use cell phones, and for 450 million of those people, the Web is a fully mobile experience,” according to the McKinsey Global Institute. This explosive growth of mobile is having a significant impact on B2C and B2B businesses.

Mobile-enablement, however, is more than just tailoring your website’s content to fit a smaller screen. There are several options and challenges involved in going the mobile route. Executives overseeing mobile initiatives need to be aware of the considerations – in order to get the maximum RoI from their mobile strategy.

Come listen to two experienced practitioners discuss key elements that will be crucial in your mobile strategy, on June 2nd, 2011 at 2 PM EST.

Some areas that will be covered include:

Native mobile apps Vs. Mobile web

Design simplicity: where less is more

Mobile as a new channel for growth

Speaker Profiles

My objective was to rotate an image based on touch events. I was experimenting some code snippets with two different ways. One method is by using UIResponder chain and getting UITouch events(began ,moved and ended). Another method is by using UIGestureRecognizer. I implemented both methods in single application and was developing an application to rotate image. After few experiments, I stick with the first method. I removed only the implementation methods of UIGestureRecognizer.

After struggling a lot, surfing through google, I got an answer. It was due to UIGestureRecognizer. If a gesture recognizer recognizes its gesture, it unbinds the remaining touches of that gesture from their view.The window cancels the previously delivered touches with a touches Cancelled message. After removing all the UIGestureRecognizer codes, now it works fine. I also read that we can also turn off the touches cancel in view property to avoid this behavior, which is yet to be tested.

Links:
http://developer.apple.com/library/ios/#documentation/uikit/reference/UIGestureRecognizer_Class/Reference/Reference.html#//apple_ref/occ/cl/UIGestureRecognizer

+(int) getDirectionBetweenFirst:(CGPoint)point1 secondPoint:(CGPoint)point2 {
    
    DIRECTION_TYPE directionType = CLOCKWISE;
    
    if (point1.x < point2.x  ) {
        
        if(point1.y > point2.y){
            
            directionType = CLOCKWISE;
            
        }else if(point1.y < point2.y)
        {
            directionType = COUNTERCLOCKWISE;
            
        }else{
            
            if(point1.y <= kCenterYCoordinate){
                directionType = CLOCKWISE;
            }else{
                directionType = COUNTERCLOCKWISE;
                
            }
      
        }
    }
    else if(point1.x > point2.x  ){
        
        if(point1.y > point2.y){
             directionType = COUNTERCLOCKWISE;
        }else if(point1.y < point2.y)
        {
            directionType = CLOCKWISE;
            
        }
        else{
            
            if(point1.y <= kCenterYCoordinate){
                directionType = COUNTERCLOCKWISE;
            }else{
                directionType = CLOCKWISE;
                
            }
        }
    }else{
        
        if (point1.y < point2.y) {
            
            if(point1.x <= kCenterXCoordinate){
                directionType = COUNTERCLOCKWISE;
            }else{
                directionType = CLOCKWISE;
                
            }
        }else if(point1.y > point2.y){
            
            if(point1.x <= kCenterXCoordinate){
                directionType = CLOCKWISE;
            }else{
                directionType = COUNTERCLOCKWISE;
                
            }
        }
        
    }
   
    return directionType;
}

kCenterYCoordinate and kCenterXCoordinate are center point of the UIView on which you detect your touches.

When you are asked not to do things, you have to do with a IDE.

Here are things you should not do with Xcode IDE version 4.0.

1. Dont use Command + Z to undo the changes you have made.

2. Dont use Command + C to copy and Command + V to paste.

3. Dont save the changes you are making to a file.

4. Dont use Command + X to cut some of your code.

If you dare to do , you would be notified with a message “”Internal error” asking for you to either crash or continue.

No one wants our IDE to crash, so choose to continue and you try the same operation and Xcode throws you the same message again. If you keep doing many times, Xcode would hang and Crash.

There are other annoying things with this version of Xcode.

1. You can not use debugger once you have started your application in run mode. You can debug only if you start right away debugging.

2. Most of the shortcuts you have used with earlier Xocde and Interface builder will not work.

Hope to add many more things to the above list, in my tryst with Xcode 4.

Following are the important point to check before testing the applications in any Java mobiles.

1. Application Signing

• If our application needs any file to be read or write from device it has to be signed to avoid, that device keep on asks for the permission.
• Some devices does not allow the unsigned application to install.
• Once the application is signed and before installing it in a device we have to make sure that particular root certificate is there in the device.
• Thawte and Verisign are the popular certificates available in maximum devices.

2. Obfuscation

• Obfuscating the code not only gives security to the code but also reduces the size of the final jar file.
• Obfuscating level may be from 1 to 9. Most of the devices accept level 8 obfuscation but it’s mandatory for Nokia high end devices to be obfuscated using level 9. If the obfuscation level is lesser than 9 Nokia high end devices throws “Authorization Failed” error while trying to install.

The problem is with the new Subscription billing requirement:

11.2 Apps utilizing a system other than the In App Purchase API (IAP) to purchase content, functionality, or services in an app will be rejected

What does this mean?

If an App has a business model where it gets paid from users by any other than in-app purchase, either they have to adopt the IAP and take a 30 % cut or get out of the App store.

This is the Official Press release from Apple:

“Our philosophy is simple—when Apple brings a new subscriber to the app, Apple earns a 30 percent share; when the publisher brings an existing or new subscriber to the app, the publisher keeps 100 percent and Apple earns nothing.”

And what does this mean? Utter Greediness.

Even though, Apple provides the a platform for the App developer or content provider to make business, the customer buys the App for the App developer and its functionality not for of the Apple.

If Apple wanted to crackdown on Applications that supports payment other than in-app purchase, soon in future iOS would be desolated , because of the prominence Android is gaining around the world, and their yet to be made moves as this.

I dont know if this means that, if Apple would not allow credit card, debit card payments in applications in App store and force developers to include in-app purchase. If this is not the case right now, this might be their next step towards making iOS entirely their platform.