How do I make my app "approvable" for the app store after rejection? - app-store

I have an app on the App Store called System of A Down app.
Yesterday, while having submitted the new version, ( which fixed a critical bug ) I submitted for a Expedited App Review. I got a message my app was "In Review" in iTC.
One day later, ( Yes, the review took one day ) it got "Metadata Rejected"
I mentioned "System of A Down" which apparently is a copyrighted brand according to Apple.
I can't mention System of a down in my app, by the /whole/ app is dedicated to them.
8.5
We found your app includes features or content, in the title, keywords, and/or imagery, that bear a resemblance to the well-known, third-party mark, System of A Down. In order to proceed with the review of your app, we require documentation evidencing you are authorized by System of A Down to use features from System of A Down. Additionally, it would be appropriate to adjust the title of your application so that the trademarked title is used as a descriptor, but not as part of the product name. For example, the following styles are acceptable formats for names: GreatApp - "for System of A Down" GreatApp - "System of A Down edition" GreatApp - "System of A Down version" Please remember that pursuant to your agreement with Apple, you represent and warrant that your application does not infringe the rights of another party, and that you are responsible for any liability to Apple because of a claim that your application infringes another party's rights. Moreover, we may reject or remove your application for any reason, in our sole discretion. Accordingly, please provide documentary evidence that you have the rights to use this content to ensure compliance with the iOS Developer Program License Agreement. Once Legal has reviewed your documentation and confirms its validity, we will proceed with your app review. While your iTunes Connect Application State is displayed as Rejected, it is not necessary to upload a new binary if you only need to address issues in your metadata. However, if you need to address compliance issues in your app - and not just its metadata - and you are able to make the necessary changes, we encourage you to do so and resubmit your binary for review.If your iTunes Connect Application State is Metadata Rejected, we do NOT require a new binary. In iTunes Connect > Manage Your Applications, select your app and click View Details. - Click Edit in the Metadata section - Revise the desired metadata values - Click "Save" at the bottom of the screen - Once you click Save, you will see the "Submit New Metadata" button in the top right. Click "Submit New Metadata" If your iTunes Connect Application State is Rejected, a new binary will be required. Make the desired metadata changes when you upload the new binary. NOTE: Please be sure to make any metadata changes to all App Localizations by clicking the Edit button next to each localization.<<
The first version however, DID get accepted. Now the question is, should I reject the Binary, and re-upload it in the hopes someone else reviews it and approves it?
I can't not mention system of a down in a system of a down app...
Or what is the best way to get this update approved?
Here's the Metadata :
Do you want all the info on System of A Down?
Their Demo tapes, Released albums, unreleased albums, videos, biography, tour dates and way more are all in this app!
Features of this app :
All 5 Demo Tapes
All info on Toxicity II ( Unreleased Album )
All info on Storaged Melodies ( Collection of unreleased songs and demo's )
All Videos ( Play directly )
Lyrics on all the videos
Play the Demo Tapes directly ( iPad only )
All 5 Studio Albums
All info on Advance ( Collection of unreleased songs )
Tour Dates
Biography
Way more amazing features planned for updates.
Amazing interface and great info - 4/5 - AppReviews Netherlands
Simply Amazing - 5/5 - My Mom
-This is a modern app, which uses gestures on iPhone and iPad instead of the old tap-bar. Swipe through the interface while you're listening to their Demo tapes in the background. ( This is has been been developed in iOS 6 Required for iPhone.
DISCLAIMER : I, Sam Guichelaar do not own, control, or endorse any of the information, Names, Groups, bands, or services linked or referenced to a Third Party in my app. No Copyrighted Images were used unless properly edited. No Copyrighted names were used, without permission. What's New in this Version - Added a option to re-view the tutorial.
-Bug Fix : Fixed an issue on the iPhone version where the user had to kill the app and relaunch before the content became visible. Thanks to Jarl and #gameshack_ for reporting this bug.
-Memory leaks fixed<<

Well, as the Apple guys put it, you can't use a third-party mark in your application without consent from the owners, It's like trying to make a game with Nintendo's Mario in it without Nintendo's consent.
The fact that it got approved before beats me

Related

Apple iphone app transfer or app replacement

We have built an inhouse version of an iPhone application that is to replace another that is already available from another developer.
I was wondering if you think we can use "app transfer" from the previous developer and in turn replace it with our own app. Previous developer has agreed for the transfer (ofcouse excluding his code). Therefore our question is if we can transfer his app to our development name and then replace the app with our own. Our goal is that the current users of this app will receive ours as an update to what they already have and not as a different app.
In short, transfer and replace so users get our app as an update.
Note:
Please note that as we were unaware of this "transfer" we submitted yesterday our version of the app with a slightly different name. Should we cancel submition (as it is still pending for validation) and follow some route you may suggest in your replies, or stay as it is now?
If you keep the Appidentifier the same between the original version and the new version you will submit, this should work as expected. (But nobody has much know-ho of the new "transfer" option yet)
So, you process would be as follows:
Hand the old developer your TeamID and your Apple ID
The old developer transfers the current App over to your team
Once done (no clue how long that takes), you have the app in your itunes connect
Now you add a new version of the App to itunes connect and mark it as ready to upload
You upload your newly coded app that meets these criteria:
Application Bundle Identifier is the same as with the App you're updating
Your new App is signed with a correct certifcate/provisioning profile (just correct for the appid, doesn't have to be the same one)
The BundelVersion and BundleShortVersionString are at higher than those of the already submitted applications.
So basically, it will work just like a regular update.

Apple Rejection of application due to in app purchase

I had created one application with 2 versions one is paid second free.
Now in free application my some of features are showing an alert by telling the user
"For using this feature you have to purchase Full Version. Do want to purchase?"
On click of No nothing done just dismiss the alert and user can continue with other available features.
On click of Yes I am navigating user on my application's link in app store. My application enter in background and AppStore opens. That shows my application. From there user can purchase app and can download app.
Apple rejected my free version application with following reason:
11.13 Apps that link to external mechanisms for purchases or subscriptions to be used in the app, such as a “buy" button that goes to a web site to purchase a digital book, will be rejected.
1) Am I doing is wrong?
2) Can I use in app purchase in the manner that my free version application get removed and full version get available? because logic for both application is different.
Thanks,
You can't disable features in lite versions. For example, if your lite version has a button that says "Level 5", the user clicks it, and it tells them to buy the full version, the app will be rejected. However, if you have a button that says "Get the full version for more levels," that should be acceptable.
The only way to be sure is to ask Apple.
I would interpret what you've said as:
Going to the App Store to purchase the full version of your app is acceptible. Many apps (including mine) do just that.
However, using IAP to perform the upgrade might be preferable. Your main problem is transitioning existing users from the Lite/Full apps to one with IAP -- in short there's no fool-proof way of doing it.
One thing that might get you rejected is non-functional buttons in the free app. According to the guide-lines, all apps need to be fully functional. Of course your free version can have fewer features, but they don't like it when there are buttons that do nothing but prompt you to upgrade.
What you are doing here is not in-app purchase. In-app purchase refers to using the iOS SDK to allow a user to purchase additional content or functionality that will run in your app. Having 2 separate versions of the app like that does not use in-app purchase.
I'm guessing your app was rejected because you gave the appearance of in-app purchasing by having a message saying "For using this feature you have to purchase Full Version. Do want to purchase?" What you should be able to do, without significant change, is disable those buttons that aren't available in the free version; perhaps replace their text with "Full Version Only." Then, somewhere else in the app, maybe the home screen or screen where those buttons are, you can have a button that says "Get the full version!" or something, which would link to your full version in the store.

Iphone app for german app-store (localization)

i recently published an iphone app using monotouch to the market.
It's currently in the waiting for review status.
Today i found out that when clicking on the button "View in appstore", the following happens:
Itunes openes with the following message (Your app is in the US-Market, click to change your default ....)
"Your app is not available in the us market".
I'm irritated about this messages and unsure if i did anything wrong because i did not use the official localization. My localization is completely build in C# and does not use "lproj" files.
So i DO NOT have any +en.lproj or de.lproj folders in my app.bundle.
The binary details in Itunes-Connect says the the following: Localizations: ("en")
Does this mean my app will not be available in the german market if it gets approved, even though my default language in Itunes Connect is "german" and i have added all the app-details in german?
How does Itunes Connect decide in which markets the app is available?
The problem is that i don't want to publish a new binary and risk waiting another +5days, because the app should already be in the market (customers ...)
Just the be clear: The app does have english and german localization strings and will show the correct ones depending on the user-language -> but it's all written in C# ...
Does this mean my app will not be available in the german market if it gets approved, even though my default language in Itunes Connect is "german" and i have added all the app-details in german?
How does Itunes Connect decide in which markets the app is available?
Find under Manage Your Applications -> "YourAppName" -> Rights & Pricing -> "specific stores". You can change all territories in there.
As long you app is not reviewed yet -the app store link does not work.

How can I reserve an iPhone app name in apple's developer portal?

I want to reserve an app name that I intend to build out over the next 90 days, how do I do this in apple's web developer portal?
Update 2015:
The limit of 180 days is now gone, Apple dropped the cap this year -
You can read the full licence here, gone.
Also, you may have noticed that the app name expiring topic is gone from the contact us question tree in iTunes Connect.
That being said, as you can see in the declaration:
You will not, directly or indirectly, commit ... (e.g., submitting
fraudulent reviews of Your own Application or any third party
application, choosing a name for Your Application that is
substantially similar to the name of a third party application in
order to create consumer confusion, or squatting on application names
to prevent legitimate third party use.
This lets us suppose that if you haven't updated your binary for a looong time and someone wants to use the same name, chances are that if they ask for it, they will get it, but yeah, technically speaking, you don't need to worry about this anymore.
Update 2014:
As stated in the iOS Developer Library, the limit is now 180 days:
Note: After you create your app and assign it a name, you have 180
days to deliver a binary or else your app will be deleted from iTunes
Connect so that the app name is free for use by the developer
community. Per section 3.2 of the iOS Developer Program License
Agreement, squatting on an app name to prevent legitimate third-party
use is prohibited. For information about email alerts you will receive
to remind you of this policy, see “App Name Expiry.”
90 days you say? This wouldn't be the first project that was supposed to take 90 days but needed more.
Once you fill in the information in itunes connect you have 120 days. After these 120 days your app name will become available for other developers. Yes, others, you can't take it again.
So you better make sure that you have your app ready for sale in 120 days.
You should read the itunes connect developer guide. It explains the process in detail. It's too complicated to answer this in a 5 minute stackoverflow answer. But the others outlined it, and I just wanted to mention = the 120 day limit. Happy squatting.
You don't do it in the Developer Portal, you do it in iTunes Connect.
Log in using your developer credentials
Click Manage Applications
Click Add New Application
Complete the basic information, including the app name
This resources implies that app names no longer expire.
TUTORIAL: RESERVE YOUR APP NAME FOREVER
Log in to https://itunesconnect.apple.com
Click Manage Your Apps
Click Add New Application
Complete the basic information, including the app name
Upload temporary icons and screenshots (for iPhone 4 & iPhone 5)
Change the app status to “Waiting for Upload”
Create a very simple app and use the new bundle ID
Submit the App to the App Store for Review (as you normally would)
After the status has changed to “Waiting for Review” go into iTunes Connect
Click Manage Your Apps > View Details > Binary Details
Click Reject this Binary
This will set the status of your application to “Developer Rejected”. Since you have successfully submitted a binary and had a “Waiting for Review” status it can sit in that status forever, therefore your app name is parked forever! Apple considers it a “real” app since it was officially submitted. So now sit on your great app name until you’re ready to finish development.
(Source 1, Source 2)
In iTunes Connect, go to Manage Your Apps and then Add New App. You can choose a name and enter other relevant information, but not upload binaries at this point. You'll also be able to set a release date in the future.
Go to iTunes Connect, then Manage Your Apps, then Add New App.
Create an App with placeholder data (you'll need screenshots, real or temporary).
If you don't upload an associated production [App Store] distribution App within 90 days, you'll lose the right to use that name forever.
Cyber-squatting on an App name you don't make use of is bad form.
If you decide you don't want to use the name, please delete it and free it up to someone who will.
You can add the application as suggested above. And about app name reservation here is my answer.
After creating your app and it is in the state Prepare For Upload or Waiting For Upload, you have 180 days (6 months) from your creation date in iTunes Connect to deliver a binary to Apple. If you do not deliver a binary before the 180-day deadline, your app is deleted from iTunes Connect. As a result of this deletion, your app name can be used by another developer and you cannot reuse the app name, SKU or bundle ID.
I got this information from apple documentation and the link is
http://developer.apple.com/library/ios/#documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/8_AddingNewApps/AddingNewApps.html#//apple_ref/doc/uid/TP40011225-CH13-SW1
Search for "App Name Expiry" and it leads you to the required page.
I hope this helps all of us.

The mechanics of the iTunes store

Not specifically a programming question, but might be something a bunch of programmers run into.
I wrote a really trivial application for the iPhone and submitted it for approvals. After a few back and forth (e.g. denied, then resubmit) of fixing various UI guidelines issues, I got an email today stating that:
Your application is now Ready for
Sale. If your contracts are not in
effect at this time, your application
will not be live on the App Store. You
may track the progress of your
contracts in the Contracts, Tax, and
Banking Module in iTunes Connect.
Now the application is free, so I am not sure why they are sending an email saying that the application is ready for sale. The contacts are in place as well:
(source: angryhacker.com)
But the real problem is that I click on the link they provided...it opens iTunes, then says:
(source: angryhacker.com)
I went into iTunes Connect to Manage Your Applications link. The status is green, Ready for Sale. I checked all the countries where the application is supposed to be available -- and all countries are checked. Plus, I cannot find it in the iTunes Application Store either.
What am I missing? Is there an interval between when the app is approved and when it should appear in the iTunes store?
Yes there is an interval while it is released. Wait about 6 hours and try again.
Once your application has been approved it does indeed take up to a few hours before it has propagated and shows up. The same applies when you pull your application from the App Store or changing your application description or screenshots.
Basicly everything you do in iTunes Connect regarding your app, takes some time to propagate through the servers. I don't think I ever had to wait longer than 6 hours though, more like 3 hours on average.