I am trying to transfer app from itunes connect account to another by following this web site
https://developer.apple.com/library/ios/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/TransferringAndDeletingApps.html
but can't see the "Transfer App" menu item
Here are my roles
Any idea? Thanks, Michal
If you don't fulfill something or this, you can't see "Transfer App" option, get from Apple Documentation.
I hope help you.
Criteria for Transferring an App
Before you transfer an app to another developer, ensure you’ve met the following criteria:
Make sure your accounts aren’t in a pending or changing state.
For example, make sure your account or your recipient’s account have agreed to any contract amendments that wait for approval and that any iAd App Network-related account information is up to date. See Viewing Contracts and Contract Status.
Make sure the app uses only technology and content that can be transferred.
No version of the app can use an iCloud entitlement.
No version of the app can use a Passbook entitlement.
The app can’t offer (or have previously offered) In-App Purchase subscriptions: auto-renewable, free, or non-renewing.
Make sure the app and any In-App Purchase products it offers have a status that supports transfers.
The app status can be one of the following, assuming that there is at least one approved version of the app: Ready for Sale, Prepare for Submission, Developer Removed From Sale, Invalid Binary, Developer Rejected, Rejected
In-App Purchase products can have one of the following statuses: Approved, Ready to Submit, Developer Removed From Sale, Rejected
Make sure that In-App Purchase product IDs on the app aren’t the same product IDs on any apps in the recipient’s account.
Make sure to turn off TestFlight beta testing for all prerelease versions of your app.
Besides the criteria you must meet to be able to transfer an app (and have the link show up in your iTunesConnect page), my experience was that the logged in user must be the Team Agent, which is whoever opened the account in the first place. No admins or app managers other than him will be able to see the link.
Here is a list of the criteria that you must meet to have the app be transferable: https://developer.apple.com/library/content/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/TransferringAndDeletingApps.html
Hope this helps.
Related
I am trying to submit my app for Test Flight beta testing, while submitting is is showing error saying
"Apps that use the entitlements [com.apple.developer.in-app-payments] must have a privacy policy for [English]. If your app doesn’t use these entitlements, remove them from your app and upload a new binary."
I have already updated privacy policy link in
TestFlight->Test Information -> Privacy Policy URL
AppStore->App Information -> Privacy Policy URL
FYI, I did not yet updated in Marketing URL in Test Information & I am using Apple pay in my App.
Please let me know what I am missing or where am I missing anything.
Thanks
If you use In-app Payments you need to disclose so in your Privacy Policy -- even if that's the only thing you use in your app.
To fix this, you need to:
Create a Privacy Policy on your website (or any other public page where you can host your policy)
Disclose in your Privacy Policy that you use in-app payments and that Apple is responsible for payments
Provide the URL to your Privacy Policy in iTunes Connect
Some few examples that might help you:
WeatherBug clause:
Calm policy:
Please See this - https://developer.apple.com/support/itunes-connect/#//apple_ref/doc/uid/TP40013727-CH33-SW19
In iTunes connect, you need to go to your product and set it to Remove from Sale. You can then delete it.
Also, In Your Project --> Target --> Capabilities --> Turn In App purchases to off.
Removing Products from Sale You can choose to stop an In-App Purchase product from being sold in an app. If you do, the In-App Purchase product remains in iTunes Connect.
Important: Removing a product from sale prevents auto-renewable subscriptions from renewing, but it doesn’t keep users from being able
to restore products that they purchased previously. bullet
Deleting Products You can delete In-App Purchase products after they’re created, but not if they’re In Review. To delete a product after it is available for sale, you must first remove it from sale.
Important: After you delete an In-App Purchase product, it’s no longer
available on iTunes Connect and it can’t be restored. The product ID
can’t be reused for another In-App Purchase product.
The following approach has resolved my issue.
I was in an impression that [com.apple.developer.in-app-payments] is needed for Apple pay, but when I removed [com.apple.developer.in-app-payments]/Merchant IDs from entitlements file, the Apple pay still works, & build is able to submit for external tester/review
Now the conclusion is that both in-app-payments & Apple pay in Application is totally different
I have developed an app like money wallet (e.g. paytm), where user can request money to each other and transfer money to each others account. with every transaction of user, Admin will get some fixed percent commission.
As app is for one small town only,right now user will have to manually contact admin to load money in his wallet or to withdraw it.
I want to submit my app on iTunes store. I know to use any digital content, services, unlock features we need to use In App Purchase. And for any physical good we need to go with any other third party payment gateway.
So I am confused that will apple approve my app or not. Please help.
Thanks,
First, you never know if Apple will approve or not. The only way to know for sure is to submit and see what happens.
Your description of features sounds like you are probably taking the correct approach.
Its important to use In app purchase for unlocking content/features:
Apps that unlock or enable additional features or functionality
with mechanisms other than the App Store will be rejected
And equally for real world purchases to use something else:
Apps using IAP to purchase physical goods or goods and services used
outside of the App will be rejected
The complete guidelines can be found here https://developer.apple.com/app-store/review/guidelines/#purchasing-currencies
And again, its Apples own words:
This is a living document, and new Apps presenting new questions may
result in new rules at any time. Perhaps your App will trigger this.
I tried to submit using paytm integration sdk, and after that my app got rejected
following is reply from App Store
Guideline 3.1.1 - Business - Payments - In-App Purchase
We noticed that your app or its metadata enables the purchase of content, services, or functionality in the app by means other than the in-app purchase API, which is not appropriate for the App Store.
Next Steps
While the payment system that you have included may conduct the transaction outside of the app, if the purchasable content, functionality, or services are intended to be used in the app, they must be purchased using in-app purchase, within the app - unless it is of the type referenced in guideline 3.1.3 of the App Store Review Guidelines.
Please see attached screenshots for details.
Since your App Store Connect status is Rejected, a new binary will be required.
My Apple Developer program membership is expired, so my App has been removed from the App Store.
And I already renewed today, but the App status in iTunes Connect still shows pending contracts like the following picture:
What should I do after renewals? Should I submit the App again?
Apple won't publish apps until you've accepted the contracts.
Log in to iTunes Connect.
Go to Contracts, Tax and Banking.
Add the necessary info there. Your app will then be automatically approved.
When your status is Active (Pending User Info).
Go to Agreements, Tax, and Banking and View for paid apps. In that page you need to add contact for Senior Management, Financial, Technical, Legal, Marketing and you are done.
Once you have applied for renewal of contract, then Apple will send one code within 2 business days. You need to click on the activation code and enter it to activate account. Once you activate your account, the application state will automatically change from Pending contract to "Ready for sale"
No need to submit application again...!!!
We hit this problem and tried a number of methods as found to fix it but got nowehere. It appears we had paid the renewal in the developer center but for some reason the update was not synchronised with itunes connect.
A quick call to iOS developer center on one of the numbers listed on the following page and the issue was fixed by the support person within a couple of minutes.
https://developer.apple.com/contact/phone/
Login to your apple developer account and you would need to clear any notifications like the one shown here.
Login to iTunesConnect.
Go to Contracts, Tax and Banking.
Fill in your info.
This is my first iPhone application that I am creating for a client and he asked me to submit the app using my own Apple Development License (Individual & Not Company License) so my question which might be very basic; can I submit the App using my own development license but it appears at the end on the App Store under the client's company name (i.e. is their a field or something while submitting the app that we use to tell the owner of the app)?
P.S. I tried searching for this specific questions but most of the websites/threads are talking about submission guidelines and probably my question is a very basic question before going into the guidelines
Thanks
No, if you submit as you, it appears under your name in the App Store. You can, however, transfer an app to another party.
FAQ on Transferring App Ownership.
From the FAQ:
What are the requirements for transferring an app?
To transfer an app, make sure that:
The transferor and the recipient have active developer accounts and accepted the most current version of all master agreements that are currently in effect
The app has at least one approved version
The app is in the Ready for Sale, Invalid Binary, Rejected, Developer Rejected, or Developer Removed from Sale state
Any associated In-App Purchases are in the Ready to Submit, Ready for Sale, Rejected, Developer Removed from Sale, or Approved state
You know the Apple ID of the recipient’s Team Agent and their Team ID
It is customary for developers to first submit apps (or major revisions) to the store under their own identity ... or, in larger companies, to a separate "development" identity ... and then to transfer the apps when they are really ready to be sold to the public. (Companies often do not want to draw attention to these apps until that time.)
If the company does not yet have their own Apple identity, you should instruct them to start getting the necessary paperwork in place now, so that ownership of the app can be transferred without delay.
Don't let the company initially offer the product for sale under your identity. (See above.) You've got a developer identity basically [just ...] so that beta-testers can actually download from the store.
I am stuck with one of the in-app purchase rejection issue in my app and need some help on this.
What this in-app for?
In our app we have options for user to become premium user. A user can become premium user to enjoy some benefits and it is tied to time. There are two in-app products which defines them
One month premium service.
One year premium service.
Since these are time based service, user expects these service should be made available for that user once he/she purchase the product for the specified time, from all his/her other devices. In order to track whether the user is premium service user or not, once the purchase is done, the app writes a entry in server about premium service. So when user uses other device and logs in, he/she can enjoy the premium service without any issues. For this reason I created the above mentioned products as "consumable", thinking that it is controlled by our server there will be no issues. But apple came back with rejection and asked me to change the products to "non-renewing subscription".
Here is what apple says about this
We found that the Purchasability Type for one or more of your In App Purchase products was inappropriately set, which is not in compliance with the App Store Review Guidelines.
"Premium account service for 1 month and 1 year" IAPs are set to Consumable.
However, based on product functionality, it would be more appropriate to use the Non-Renewable Subscription In App Purchase type because the service offered by your application requires the user to make an advance payment to access the content or receive the service.
The Purchasability type cannot be changed once an In App Purchase product has been created. Therefore, you will need to create a new In App Purchase product with the correct Purchasability Type. To create a new In App Purchase in iTunes Connect, go to Manage Your In App Purchases, select your app, and click "Create New". The current product will show in iTunes Connect as "Rejected".
Non-Renewable Subscription content must be made available to all iOS devices owned by a single user, as indicated in Guideline 11.6 of the App Store Review Guidelines:
11.6 Content subscriptions using IAP must last a minimum of 7 days and be available to the user from all of their iOS devices
If you choose to use user registration to meet this requirement, please keep in mind that it is not appropriate to require user registration. Such user registration must be made optional. It would be appropriate to make it clear to the user that only by registering will they be able to access the content from all of their iOS devices; and to provide them a way to register later, if they wish to access the content on their other iOS devices at a future time.
For more information about Purchasability Type, please to refer to the iTunes Connect Developer Guide.
Now I have created new in-app products which are non-renewing. But this works the same way as I mentioned earlier, i.e. the server keeps track of whether user is premium user or not, expiry date. When user goes to other device and does login, the app comes to know whether user is premium or not and based on that app works.
But I have couple of questions on this,
Should I need to provide the "Restore" button in the app? If so what is the purpose and how it works?
Since the user can access this service only after doing login to the app (it is different from app store account). Will these two logins make any issue?
Please share your valuable inputs.
It is highly unlikely that the user will end up in a situation where they won't be able to use your app unless they restore their purchases, however it is still possible. Imagine your server goes down for a day and during that day some user purchases a subscription, gets a new iPhone, installs your app on the new device and then wipes their old iPhone. I can think of a couple of other, equally unlikely, but still possible situations (Apple receipt validation server going down, etc) in which the purchase receipt will get lost in transit. It's best to provide the button, and if Apple thinks that you need it in your app, you will have a hard time convincing them otherwise.
If by "two logins" you mean user having to log in to your system and then log in to the App Store to purchase the subscription, that should not be a problem.
I recommend you make the changes Apple requested to the Purchasability Type and then re-submit. If you need to clarify a lack of a restore button put it in the notes for the reviewer