How to send generated passkit to Wallet? - passbook

I generated a passbok file in Java that I want to share with the wallet applications in iOS and Android. The method creates a
.pkpass file so... how can I send it to the Wallet applications? I find really few information about this step...

You can email it to users or put it on a web server with a header Content-Type: application/vnd.apple.pkpass. Or you can use the PKAddPassesViewController to add to Wallet via an app.

Related

Error on "Crypto" to use Twilio (for SMS)

I'm developing an application in React Native for iOS and I'm using Twilio to send a text message (SMS).
To use Twilio I added 2 nodes: Util and Crypto.
In my app, I only added react-native-ble-manager over util, twilio, crypto, and the basic nodes.
Adding the last node Crypto, when I include Twilio in the code, I get an error:
in detail:
Can you help me?
Twilio developer evangelist here.
The Twilio Node.js library is not intended to be used in client side applications. That would require you to store or retrieve your account credentials within the app, which would make them available for a malicious user to steal and use.
Instead, we recommend you set up a server that can perform the API requests and you make calls to that server from your application. Here's how we recommend you do that with Swift on iOS for example. We don't have an example for React Native, but as long as you can make a request to your own server from the application, then that's what you need to do.

Embed DocuSign in my application

We want to integrate embed sending and signing from my application to the point that users of my app don’t know that they are leveraging a mashup? I want to that my users able to use Signatures without leaving my site.
I am using API call through Java Code but it is not possible to us send the document and get back it into onesession. Kindly give some code which help me to implement that.
See the DocuSign API recipes:
Embedded Sending Or use the API directly to enable your app's users to send a signing request. Eg, see the sending step within the Embedded Signing recipe.
Embedded Signing

What url should I use to verify my receipt in In-App Purchase

The above question I found in FAQ in Apple's Tech Notes (QNo: 15). They gave an answer like this:
Use the sandbox URL https://sandbox.itunes.apple.com/verifyReceipt
while testing your application in the sandbox and while your
application is in review.
Use the production URL http://buy.itunes.apple.com/verifyReceipt once your application is live in the App Store.
But in In-App Purchase Programming Guide (Verifying a Receipt with the App Store Section). Apple provides an url like this:
Post the JSON object to the App Store using an HTTP POST request. The
URL for the store is https://buy.itunes.apple.com/verifyReceipt.
Note that first url is using http for live account for verifying In-App Purchase while second one is using https. Which one i should use? My app got rejected because server is not getting correct response, when it sends receipt to Apple. I am using https://buy.itunes.apple.com/verifyReceipt for verifying receipt.
the best way is to first verify with the production server. if you get a 21007 code back you should make another call to the sandbox server. this is needed because during the submission process you're not always sure whether they'll use the live or sandbox server. it needs to work on both.
here's some source code that verifies receipts in safe way (counters the app store hack from last year). i added the above code to this project that will first check with the production server and then fall back to the sandbox server:
https://github.com/evands/iap_validation
EDIT: i wouldn't use that code above anymore in iOS 7. i think there are some problems with it!

Stripe and titanium mobile

How can I intergrate the stripe api for payment processing to allow people to pay for services through my titanium mobile app. Stripe.com
I am using this code to start:
https://github.com/abh/node-stripe/blob/master/lib/main.js
How can I make sure the information is encrypted.
First you need to make sure what you are selling is physically tenable, assuming it is (and your not selling any form of digital content, or functionality within the app) then the easiest way to use stripe from within Titanium would be to just wrap it in a web view (you could implement it in native code but this could get tiresome).
Assuming you have this example in a file called index.html in your resources directory.
var webView = Ti.UI.createWebView({
url : 'index.html
});
win.add(webView);
Note that you will need to let your server support https requests for actual encryption to happen, you shouldn't be encrypting yourself (in code).
Once this is done, all the work now happens on your server to process payments using Stripes libraries like in this example in the documentation.
Really this is a server job, all your doing is sending the server the information to process, not a lot going on with Titanium here except as a gateway.

Instapaper Simple API : adding links without storing user password?

I'm trying to use Instapaper's Simple API (http://www.instapaper.com/api/simple).
The API terms of use (http://www.instapaper.com/api/terms) says apps should not store user id and password, and I don't want to store them either. However, it seems that the only way to add a link to a user's Instapaper via simple API is to store the username/password (if the user does have a password).
Am I missing something?
The API terms of use state that:
Apps must not store users’ passwords. Passwords may only be collected for the xAuth token acquisition and must be discarded afterward.
Only the full API uses xAuth tokens. The above sentence doesn't apply to the simple API, since it uses Basic HTTP Authentication.
You still "must make reasonable efforts to prevent passwords from being compromised, and must not disclose passwords to any other services or individuals".
If you are using a native Mac application (like Apple’s Mail client or a third-party mail client like Airmail) there isn’t an easy way to save a link to Instapaper without first opening the link in a browser and then using one of Instapaper’s browser extensions to actually save the article.
One workaround that I’ve found to expedite this task is to write a service for OS X which uses Instapaper’s API to save links.
In order to write your own service, first open Apple’s Automator application and create a new Service. Then, drag the Run Shell Script action into the application’s main workflow area.
Make sure the service receives no input, can be used by any application, and that the shell script is set to run python.