I am trying to make In-app purchase in my application using phonegap plugin which is https://github.com/phonegap/phonegap-plugins/tree/master/iPhone/InAppPurchaseManager
but in sandbox testing i'm getting following error
plugins.inAppPurchaseManager.updatedTransactionCallback.apply(plugins.inAppPurchaseManager, ["PaymentTransactionStateFailed",0,"Cannot connect to iTunes Store","","",""])
and then the application gets struck...can anyone help me out with this??
Take a look inside of InAppPurchaseManager.js, and you'll see the first call of InAppPurchaseManager.prototype.updatedTransactionCallback is:
alert(state);
Replace that with PhoneGap's preferred:
navigator.notification.alert(state);
And it should clear up fine.
Related
Whenever I try to checkout I am getting infinite loader. When I try to debug I found there is a Javascript error in the console. As you can see in the screenshot.
When I debug the javascript file lib/web/jquery/jquery.validate.js then I found it is not an issue of a payment method rather it belongs to the shipping address. And in my case the issue start when I start to use Amasty Onestep checkout extension. I hope it will help you.
Currently I am developing an app and I want to send the client a test build , I had successfully archived the app and uploaded on AppStore ... Under the Activity section it was showing "processing" for about an hr or two , now its not showing neither anything nor the app been uploaded. Any idea what went wrong ? Did anybody experienced this kind of problem ?
It is likely that something with your binary is wrong.
You would expect to get notified about that issue in the Activity tab but it seems that (currently) you can only find the invalid build in the App Store tab when selecting a new build.
Also you should have received an email (iTunes Connect account) describing the issue.
Yes ,Some times it take time .
In my case i have wait for 4 hour then it will reflect on itunes connect account.
or you can check build status in a activity .
Please check linked image for references
I got an email from apple saying "This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data" . I then added some string on NSPhotoLibraryUsageDescription and uploaded it , it worked like a charm .
I am trying to create Payout functionality using REST API, and I have few errors.
While I am sending this request :
{"sender_batch_header":{"sender_batch_id":"test_0","email_subject":"RaceBets Withdrawal","recipient_type":"PAYPAL_ID"},"items":[{"recipient_type":"PAYPAL_ID","amount":{"currency":"EUR","value":"20.0"},"receiver":"XXXX","note":"Hello there!","sender_item_id":"71292226"}]}
I received:
JAXBException occurred : 4 counts of IllegalAnnotationExceptions.
or :
{"name":"REQUIRED_SCOPE_MISSING","message":"Access token does not have required scope.","information_link":"https://developer.paypal.com/webapps/developer/docs/api/#REQUIRED_SCOPE_MISSING"}
the second error is also strange, because payments are working fine, and scope is also fine
{"scope":"https://uri.paypal.com/services/subscriptions https://api.paypal.com/v1/payments/.* https://api.paypal.com/v1/vault/credit-card https://uri.paypal.com/services/applications/webhooks openid https://uri.paypal.com/services/invoicing https://api.paypal.com/v1/vault/credit-card/.*","access_token":"xxx","token_type":"Bearer","app_id":"APP-xxx","expires_in":28800}
Any idea?
For the second error make sure you have checked the option for "payouts" under your application at developer.paypal.com .
Go to developer.paypal.com --> DashBoard --> My APP -- > Click your APP Name --> App Feature . Select Payout here .
Regarding the REQUIRED_SCOPE_MISSING error, I experienced this as well. Adding the scope as the other poster describes fixed the issue.
Please note that after changing scope (i.e. adding Payouts) it can take a few hours for the change to be reflected, so you'll continue getting the error for awhile. This confused me when I was testing because I didn't expect sandbox to have this latency.
I have integrated MobClix to my app, the test adds are working correctly before entering my MobClix application ID, after giving actual MobClix ID i am getting below error.
( I have checked my MobClix applicationID, and also i have enabled only 320*50 add i used the same in code they are correct) Dont know why i am getting this error.
Error Domain=com.mobclix.ads Code=-503 "The operation couldn’t be completed. (com.mobclix.ads error -503.)"
Try following the steps here. If that still doesn't work, submit a support ticket and we can take a look into your account.
Well i started of by following all the instructions here:
http://code.google.com/p/xmppframework/wiki/FacebookChatHowTo
I used the recommended fork of the facebook api and tried the latest from:
https://github.com/facebook/facebook-ios-sdk/
My problem starts with the following error:
< failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl">< not-authorized/></failure>
The error is a reply from facebook to xmppframework s response to a authentication challenge. The response that is made by the iphone is base64 encoded msg when i decode it i find 2 of the values are null:
api_key=(null)
and the
session_key=(null)
This is obviously the reason facebook is returning that error. But the problem i have is i cant seem to find any where to set these values in the framework. Besides i think the session_key should be pulled in from facebook anyway.
I guess what i want to know is a couple of things.
Has any one got the xmppframework working with facebook on a iDevice?
If you have got it working did you have to stray from the path of the instructions on http://code.google.com/p/xmppframework/wiki/FacebookChatHowTo ?
do you know of any other method to get facebook chat working on the iphone?
Any suggestions or help for my current dilemma would be appreciated. Happy to share my code if you want.
cheers
I wrote the Facebook integration for XMPPFramework. The api_key and session_key, come from a call to auth.PromoteSession. Facebook is trying to deprecate that call, so to enable it, you must follow step 7, in the HowTo:
Under Migrations, change Disable Deprecated Auth Methods from Enabled to Disabled and Save Changes.