How do i implement a non-consumable in-app purchase on an app with its own Login/Registration System?
How do i implement a non-consumable in-app purchase on an app with its own Login/Registration System.(Users can signup, login and logout of the App). From Apple's perspective when a user purchases something non-consumable using IAP, he should be able to access the purchased content on all of his devices. then, it would be possible for a user to purchase the product and proceed to logout of the APP, log back in as a different 'app' user, hit restore transactions button (required if the app is using non-consumables) and get the product for free. How can i prevent this loophole?
Furthermore, App store rejected one of my build saying "We noticed that your app requires users to register with personal information to purchase non account-based in-app purchase products, which does not comply with the App Store Review Guidelines.
Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user".
I had redirected the user to login screen (if a user was not logged in to the app) before making the purchase, and this seems to be the issue of the rejection as apple says: "Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the users."
as Login is necessary for authentication in my app, how do i get around the rejection and implement both IAP and Login.
All ideas are appreciated.
swift
in-app-purchase asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
add a comment |
How do i implement a non-consumable in-app purchase on an app with its own Login/Registration System.(Users can signup, login and logout of the App). From Apple's perspective when a user purchases something non-consumable using IAP, he should be able to access the purchased content on all of his devices. then, it would be possible for a user to purchase the product and proceed to logout of the APP, log back in as a different 'app' user, hit restore transactions button (required if the app is using non-consumables) and get the product for free. How can i prevent this loophole?
Furthermore, App store rejected one of my build saying "We noticed that your app requires users to register with personal information to purchase non account-based in-app purchase products, which does not comply with the App Store Review Guidelines.
Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user".
I had redirected the user to login screen (if a user was not logged in to the app) before making the purchase, and this seems to be the issue of the rejection as apple says: "Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the users."
as Login is necessary for authentication in my app, how do i get around the rejection and implement both IAP and Login.
All ideas are appreciated.
swift
in-app-purchase asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
If you have our custom login, meaning your have your custom backend you need to validate transactions on your backend. developer.apple.com/library/archive/releasenotes/General/…
– inokey
Nov 23 '18 at 7:59
yes i have done the receipt validation on my backend and there are no issues with that. but apple rejects my app if i direct an user to login screen before making the purchase.
– Frankenxtein
Nov 23 '18 at 8:02
add a comment |
How do i implement a non-consumable in-app purchase on an app with its own Login/Registration System.(Users can signup, login and logout of the App). From Apple's perspective when a user purchases something non-consumable using IAP, he should be able to access the purchased content on all of his devices. then, it would be possible for a user to purchase the product and proceed to logout of the APP, log back in as a different 'app' user, hit restore transactions button (required if the app is using non-consumables) and get the product for free. How can i prevent this loophole?
Furthermore, App store rejected one of my build saying "We noticed that your app requires users to register with personal information to purchase non account-based in-app purchase products, which does not comply with the App Store Review Guidelines.
Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user".
I had redirected the user to login screen (if a user was not logged in to the app) before making the purchase, and this seems to be the issue of the rejection as apple says: "Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the users."
as Login is necessary for authentication in my app, how do i get around the rejection and implement both IAP and Login.
All ideas are appreciated.
swift
in-app-purchase asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
How do i implement a non-consumable in-app purchase on an app with its own Login/Registration System.(Users can signup, login and logout of the App). From Apple's perspective when a user purchases something non-consumable using IAP, he should be able to access the purchased content on all of his devices. then, it would be possible for a user to purchase the product and proceed to logout of the APP, log back in as a different 'app' user, hit restore transactions button (required if the app is using non-consumables) and get the product for free. How can i prevent this loophole?
Furthermore, App store rejected one of my build saying "We noticed that your app requires users to register with personal information to purchase non account-based in-app purchase products, which does not comply with the App Store Review Guidelines.
Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user".
I had redirected the user to login screen (if a user was not logged in to the app) before making the purchase, and this seems to be the issue of the rejection as apple says: "Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the users."
as Login is necessary for authentication in my app, how do i get around the rejection and implement both IAP and Login.
All ideas are appreciated.
swift
in-app-purchase swift
in-app-purchase asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
asked Nov 23 '18 at 6:11
FrankenxteinFrankenxtein
17219
17219
If you have our custom login, meaning your have your custom backend you need to validate transactions on your backend. developer.apple.com/library/archive/releasenotes/General/…
– inokey
Nov 23 '18 at 7:59
yes i have done the receipt validation on my backend and there are no issues with that. but apple rejects my app if i direct an user to login screen before making the purchase.
– Frankenxtein
Nov 23 '18 at 8:02
add a comment |
If you have our custom login, meaning your have your custom backend you need to validate transactions on your backend. developer.apple.com/library/archive/releasenotes/General/…
– inokey
Nov 23 '18 at 7:59
yes i have done the receipt validation on my backend and there are no issues with that. but apple rejects my app if i direct an user to login screen before making the purchase.
– Frankenxtein
Nov 23 '18 at 8:02
If you have our custom login, meaning your have your custom backend you need to validate transactions on your backend. developer.apple.com/library/archive/releasenotes/General/…
– inokey
Nov 23 '18 at 7:59
If you have our custom login, meaning your have your custom backend you need to validate transactions on your backend. developer.apple.com/library/archive/releasenotes/General/…
– inokey
Nov 23 '18 at 7:59
yes i have done the receipt validation on my backend and there are no issues with that. but apple rejects my app if i direct an user to login screen before making the purchase.
– Frankenxtein
Nov 23 '18 at 8:02
yes i have done the receipt validation on my backend and there are no issues with that. but apple rejects my app if i direct an user to login screen before making the purchase.
– Frankenxtein
Nov 23 '18 at 8:02
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53441435%2fhow-do-i-implement-a-non-consumable-in-app-purchase-on-an-app-with-its-own-login%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53441435%2fhow-do-i-implement-a-non-consumable-in-app-purchase-on-an-app-with-its-own-login%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If you have our custom login, meaning your have your custom backend you need to validate transactions on your backend. developer.apple.com/library/archive/releasenotes/General/…
– inokey
Nov 23 '18 at 7:59
yes i have done the receipt validation on my backend and there are no issues with that. but apple rejects my app if i direct an user to login screen before making the purchase.
– Frankenxtein
Nov 23 '18 at 8:02