receipt-validation

iOS in-app purchases verify receipts for consumables

由 ↘锁芯ラ 提交于 2019-12-22 01:36:19
问题 in iOS with in-app purchases, it is necessary to verify receipts with subscriptions. is it necessary to verify receipts for consumables also? 回答1: No you don't need to verify receipts for consumables. You don't need to verify receipts for subscriptions either. What's important here is that you can restore running subscriptions; but for that you can use purchase ID. As always make 100% sure you've given the user what was paid for before telling iOS that the purchase was successful! (There are

how to add openssl to a swift project

由 我的未来我决定 提交于 2019-12-19 07:35:13
问题 I am learning how to add in-app purchase receipt validation to my iOS/OSX projects. There is a nice overview here and the WWDC14 has good videos on this topic. Plenty of sample code, but everyone skips one step. How to import the openSSL header. The swift compiler complains that there is no such module. import Foundation import StoreKit import openssl //no such module ??? I am already stuck before writing one line of code. Where is the openssl framework hiding? 回答1: There is no OpenSSL module

Can I migrate purchase between applications in macOS App Store?

由 前提是你 提交于 2019-12-13 17:44:20
问题 I have several similar applications (A1-A3) with hugely the same codebase. They all do similar things (diagrams), each with a specialisation for a specific use case. I am now considering to create one app (B) that sells the specialisations as an Mac App Store In App Purchase. So basically, I reduce number of applications, but will provide same diagrams, just change how to sell them from dedicated app to in-app. How can I best ensure that buyers of the "old" applications A1-A3 can use the

Reduce size of OpenSSL binary?

由 一曲冷凌霜 提交于 2019-12-11 16:49:55
问题 I'm using OpenSSL-for-iPhone to generate a self compiled build of OpenSSL that I can use with the library RMStoreAppReceiptVerifier for receipt validation. Specifically, it builds OpenSSL 1.0.2k. The problem I'm having is that libcrypto.a (45.3MB) and libssl.a (8.3MB) are very big and are adding a lot to my app's binary. The classes I'm using in RMStoreAppReceiptVerifier only use: #import <openssl/pkcs7.h> #import <openssl/objects.h> #import <openssl/sha.h> #import <openssl/x509.h> Is there

Detect if a user refunded a 'consumable' in app purchase item (Apple app store in app purchase system)

由 ♀尐吖头ヾ 提交于 2019-12-10 12:31:00
问题 I read so far online that the only way to detect if a user cancelled an in app purchase is by using the receipt data that I get from the user's iPhone and check if the cancellation_date exists in there for that item, but as far as I know, this field is only to be found on auto-renewable subscription items. (At least to what I read online on every post I found that talks about in app purchase, no mention to consumables at all.) Because they are always stored in the receipt data, while

iOS: Tracking the paid users while converting paid iOS application to free with in-app purchases

由 [亡魂溺海] 提交于 2019-12-08 06:38:27
问题 We have a paid iOS application in the AppStore currently. We are planning to convert it to a free application with in-app purchases. We would want to make the in-app purchases free to the users who have already paid for the application in the previous version. I think this can be done via App Receipt Validation. But will the receipt get updated once the application is converted from paid to free and will the purchase details get lost? 回答1: If you convert your app from paid to free, you are

Verifying the purchase (receipt) of another application (Mac App Store)

由 丶灬走出姿态 提交于 2019-12-08 03:41:41
问题 TL;DR: Is there a way to verify that a user has purchased another app (of mine) from the Mac App Store? In a brief, I want to completely rebrand one of my applications on the Mac App Store. The current version is very buggy and has a user base of nearly 90% pirates. I want to shut down the old application and completely rebrand it as a new product. However, I don't want to completely screw over my current, legitimate customer base. I am hoping there is a solution to this. The way I was hoping

iOS: Tracking the paid users while converting paid iOS application to free with in-app purchases

由 南笙酒味 提交于 2019-12-06 16:45:32
We have a paid iOS application in the AppStore currently. We are planning to convert it to a free application with in-app purchases. We would want to make the in-app purchases free to the users who have already paid for the application in the previous version. I think this can be done via App Receipt Validation. But will the receipt get updated once the application is converted from paid to free and will the purchase details get lost? If you convert your app from paid to free, you are still able to inspect the receipt and see which version was originally downloaded and act accordingly. When we

Apple receipt - original_purchase_date has date before app creation

由 倖福魔咒の 提交于 2019-12-05 08:44:59
I'm a bit confused with this. So following this approach I got json which contains bunch of decrypted fields. Among them original_purchase_date. What I need is to track if application was purchased before this new version becomes free and I think I need to use this field for that. But for some reason on sandbox environment it shows date "original_purchase_date" = "2013-08-01 07:00:00 Etc/GMT"; which is couple of years before application was made. So right now I'm not sure Why it shows that date. Is original_purchase_date really the field I need to track. Original purchase date is always "2013

How to determine the original build or date that app (not in-app purchase) was purchased

由 微笑、不失礼 提交于 2019-12-04 08:23:37
My app is currently a paid app. I would like to convert the app to a free app with IAP and grandfather (give all users who paid for the app) the IAP features for free. I thought I could use receipt validation to either (1) determine original purchase date of app - but this seems to be only available for IAP or (2) Use original Application Version (which appears to be the build version not the app version). However, when I test this in testflight, the original version number is always '1.0'. Various sources say this is a testflight issue and that the release app would correctly identify the
订阅 receipt-validation