I'm implementing an in app purchase for a Non-renewing subscription in my app. I'm using an account system so I'm linking the purchase to the user account in my server. This works fine but recently I read that the purchase should be linked to an apple id. I'm a little confused because I thought you couldn't get access to an apple id. So I have some questions:
Could my app be rejected for link the purchase to an account in my system?
I read that I could use the UUID as user identifier in my server and save it in user defaults but I don't know how to identify the user if He switch devices?
If identify the user with the UUID works, I would like to control if the user logs in with the right account in my system so if he has the right UUID but a different account, He should not get access to my functionality. Is this possible or my app would be rejected for this kind of control?
Links:
In app purchase - Subscription - not based on Apple Id and How to store and fetch the response of in-app purchase in ios?
In the apple documentation saids that you should use transactions recipes for restore in case the user switch devices but in Non-renewing subscriptions the app will be responsable for the restoration process.
https://developer.apple.com/library/mac/documentation/NetworkingInternet/Conceptual/StoreKitGuide/Chapters/Restoring.html#//apple_ref/doc/uid/TP40008267-CH8-SW9
Related
Google play console is requesting to verify my identity.
The problem is that the verification form is asking for an organization info and docs while the account is for individual and that is provided in the account details screen.
So what am I missing? Where to go? Or how to contact google support?
I had this after emailing googleplay-developer-support#google.com. Solution: Your payment profile shouldn't be set as organization if your developer profile is set to individual and vice-versa.
Per checking, the payments profile associated with your account is set as an organization. You may choose to verify your account as an organization with the following documents that our system accepts: Certificate of Organization, and a valid ID of the organization's Official Representative.
If you would like to verify as an individual and change the entity type on your payments profile, you would have to create a new account in order to change from organization to individual. You may view your payments profile via pay.google.com
To change the entity type on your Payment Profile, it would need to be deleted and created again. Since a Play Console account can only be associated with one Payment Profile, it will need to be deleted and recreated as well.
To resolve the issue, we can close your Play Console account and refund the registration fee. Then, you can delete your payment profile at pay.google.com before you sign-up for a new Play Developer account. To proceed, please provide confirmation by responding with “I confirm to have my Play Console Developer account closed and have its registration fee refunded.” Also, please remove the existing draft app from the Developer account
I had this issue recently and it turned out it was because I had an old Payment Profile with Account Type of 'Organisation'.
You need to go here: https://pay.google.com/gp/w/u/0/home/settings
Personally, I had two payment profiles; one was for an Individual and one was for an Organisation. Maybe the Organisation one was the default or whatever.
In the end I managed to close that payment profile and create a new developer account after having the first one refunded.
There were a few emails to Google Support going back and forth but that solved it in the end and now I have an app on the Play Store.
I have implemented a login feature in my app where a user can pay for subscription and have that subscription tied to their in-app login account by using the setObfuscatedAccoundId() method. However, in a scenario where the current user(user_A) makes a purchase, logs out of the app and a different user_B logs in, user_B is unable to purchase the same subscription as it has already been bought by user_A (as they share the same underlying Google Play account) even though I DON'T want these in-app accounts to be related at all. Currently, what happens is user_B gets a responses that states "You already own this item". So that makes me wonder:
Can we actually possibly use a single/the same underlying Play Store account to purchase the same subscription while logging in to an app with different user accounts?
Also, what would be an ideal design approach for a problem like this considering the limitation?
I am still a beginner at this and would really appreciate your inputs!
I'm beginner at this like you and may I was wrong but I think you can not do that because the subscriptions are saved in your google account and you can not buy same subscription you owned already.
I need to transfer ownership of my apps to somebody else on windows marketplace.
The procedure is easy on Apple's App Store and Google's Play Store, but could not find a solution on windows marketplace.
Yes, it is possible to transfer ownership of apps in the Windows Marketplace from one account to another.
Contact support
Visit the Dev Center support page and select any of problem types listed.
Change Problem type to "Store registration and your account" and Category to "Other"
Select Start Email and fill in all the details of the app you want to transfer
Details you'll need
Current Account
Microsoft Account
Developer Guid
App Name
App Guid
Transferring to Account
Microsoft Account
Developer Guid
Source: Spaso Lazarevic Blog
In addition to Neil's answer, (This is too long for a comment) :
Trying to do it these days, there are a few constraints that are worth noting (copy paste the support answer) :
Apps must be published to the store
There cannot be any “in progress” submissions or “package flights” for the apps
Apps may not contain in-app purchases
Requests must be made from the source account
All Ad campaigns paid and/or house must be paused
Apps must have reserved names
App may not use MPNS
Apps may not use WNS for push notifications
Additional requirements: If the source account (i.e. owns the apps) is a business account then written authorization is required authorizing Microsoft to transfer the apps. This should be in the form of a notarized letter listing the following details:
Name of the source account/company
Source account’s Microsoft Account (email address)
Name of the app(s) and the Big ID (app id) to be transferred
Target account’s publisher name and Microsoft Account
Letter must be notarized
Before any paid apps can be migrated the tax profile and payout account must first be validated on the new account (Target account) prior to the migration. In addition, if the target account is also a company account, the ID Validation must be completed.
Some considerations:
Ratings and reviews will migrate to the new account
Reporting data stays on the original account.
The new account will only begin accruing earnings for any sales after the app migration to the new account is complete.
You must export all download reporting payout data before the migration. Once the migration is complete this information will no longer be available for export on either account.
Apps will continue to display the old publisher name in the marketplace until a new update has been published from the new account.?
Our windows store application is especially for our customers.
It requires user credential to login.
It doesn't have any sign up page.
New users cannot access our application(They should be our customer.)
For new users, Admin will create an account and share them to the
user.
At the first time, user is requested to change password.
This is how our customer access our application
We submitted our free business app to the windows store.
But it is rejected with the reason saying "Apps that require users to sign in must either specify upfront in app description the type of access user must have and how to get it or provide a mechanism for new users to sign up for services from within the app. At a minimum this could be a link in the app to the website where the user can create a new account and sign up for services. Your app did not appear to provide this information to the user."
We do not have such a page. How can we proceed for resubmission?
Whether we need to provide description like "Our application can be accessible to our customers only"
or
provide support email address and saying like "Contact our support team/admin to create new account"
or
any suggestions?
Simply show a description which tells user that this app is only for registered customers. For more details you can write us to your email id or can fully describe the log in process there on the first page.
The description says it all. Include exactly what you have said in the application's description update. In addition include this information on the main page of your application for extra safety.
Note how DropBox has done it. When you install the app your very first screen has the login boxes and a link to "or Create an Account" which then brings you to a webpage to create the account.
You could link this to a page on your site that allows a user to contact your org for an account or register for one to then be approved, etc
I'm looking to publish an app which gives users the ability to register and login using my hosted database. The user will supply their name, email and password.
I'm wondering what I need to do in order to get the app certified for the marketplace - what disclaimers/notices must I ensure the user agrees to before the app is certifiable? I'm presuming if I don't handle this, it will be picked up by policy 2.8.
Have you many more tips for getting an app published to the marketplace? First time user, really want to have my app up and running within the next month!
Thanks,
Gerard.