I am trying to implement in app purchase in my mac application.
I am able to get the product list. Show to user the product list.
I am able to make purchase with my test account. Now I want to verify the receipt in server instead of the application...
What my doubt is. In my bundle i am getting a receipt file which ..should i send the content of that file or i have to send the transaction data to my server for verification.
And in server side what will be the verification process I need to follow
Send the receipt file to the server. and from server send that receipt to the itunes for verification.
Related
My app has a little dialog where users can click to opt-in for push notifications. On iOS when they press this, they get the permission request and then if they approve it, I send a POST request to my server with their push tokens.
Since, Android remote notification permissions are granted during the app installation, when do I send this POST request to my server with their push tokens?
Save it on first launch.
Using AsyncStorage you can save user first launch and save the token at this time
Let's say I have an admin page with data that hides on load and shows when the admin logs in. This is insecure as anyone can just inspect it and click 'show'. I would like to set up some sort of server (I'm new to this sort of stuff so don't know what is required) that I can send the attempted username and password and it will return the data if the user is an admin. This way it would be more secure.
If it helps: I have a raspberry pi (C) 2011.
I'm currently working on a web app which will allow a user to subscribe to push notifications. We'll store the subscriptions in a database table mapped against the user's ID and when a notification needs to be sent, we'll look up the user's subscriptions and send the notifications.
I've been following this guide:
https://developers.google.com/web/fundamentals/codelabs/push-notifications/
All is going well, but something just doesn't feel "right".
On every page load, the service worker is registered, then it checks if they're already subscribed, then even if they are it calls updateSubscriptionOnServer() which contains the following comment:
// TODO: Send subscription to application server
This effectively means that every page load is going to be attempting to write the same subscription back to the database. Obviously we'll handle that in the application, but it doesn't seem ideal.
With the Web Push API, is this the expected approach?
Many thanks
Yes it can be useful to send the subscription to server on every page load:
The user may have changed permission from blocked to granted (or default) in the browser settings, so you want to create the subscription and send it to the server
The subscription endpoint may change for different reasons, so you need to make sure that the current endpoint is sent to the server (the previous endpoint will return 410 Gone)
A compromise between the points above and performance can be to send the subscription to the server only on given pages (e.g. homepage).
I want to store my messages received on my email account in my own database, so that I can view those emails in application of asp.net made by me.
How to retrieve those messages from email server and store them in SQL Server database.
You might find that the emails are deleted from the mail server when your email client retrieves them. e.g. if you have outlook pointing at your mail account and it retrieves the emails your application will no longer be able to get them.
You can set up an auto forward rule to forward onto another email address. Then your application could retrieve from that.
I have used this for retrieving mail off the mail server http://www.lesnikowski.com/mail/
I am developing a software but for that I want to know as if i send an email then how can i check the sent email is in recipient's inbox/ Junk.
I am using AsP.net and c# technology for this
Please reply
You can't detect what is done with the email once it is delivered to the users inbox other than requesting a delivery receipt and a read receipt but the user can opt out of these.
The best way to avoid being marked as spam is to use a trusted third party service such as Campaign Monitor or MailChimp.
Failing that you should make sure that your email has a proper from address set, that you have set up SPF records to allow the sending IP official permission to send email on behalf of the from domain, keep your html to content ratio reasonable and if possible use an email address that your customers have already received an email from before so that there is a higher chance that the address is already in a whitelist.
You really can't because there are many different email spam solutions out there and they don't send a status back saying whether they delivered the email to the recipient or not. What you can do is send an email with a tracker to see if the receiver opened it.
http://www.aspnetemail.com/samples/emailtracker/default.aspx