I developed an iOS application where in that application can rate and review other users in 3 sectors like:
Dating
Personal
Professional
The entire application was completed and built in 1.0, i have submitted the application to the app store but the application was rejected due to 1.2 guidelines.
As per the 1.2 guidelines i have implemented
Block/Unblock
Terms & Condition
User Objection Features in 1.1 build
and resubmitted it to the app store but still rejected by the app store.
I'm getting issue from apple like this
Your app still includes features that objectify real people, which
could be interpreted as being offensive or mean-spirited.
Next Steps
Please remove all offensive and mean-spirited content from your app
and submit your revised binary for review.
Please see attached screenshots for examples of objectifying content.
can you point it out to me what is the mistake i am doing and should be revised?
Please help me on this Thanks in advance.
What options do you present for taking the input on rating? May be the wordings you use are being considered offensive.
Taking user rating is not an offensive feature, you need to look into the next level of details which is causing rejection.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
Apple started to reject our app because they can't access our app because of geo-restriction. We have also a video which shows our app's demonstration in the review process. And Apple Review Team can't access app in U.S.A. It's a gambling app and it must be geo-restricted according to the App Store Review Guidelines.
5.3.4 Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must have necessary licensing and permissions in the locations where the App is used, must be geo-restricted to those locations, and must be free on the App Store. Illegal gambling aids, including card counters, are not permitted on the App Store. Lottery apps must have consideration, chance, and a prize.
We show a pop up to user which says basically that they could not access to the app because of the geo-restricted.
Apple Review Team's Response:
5.3.4 Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPhone running iOS 13.5 on Wi-Fi.
Specifically, upon launch, your app displayed an error message. All apps submitted to the App Store must function correctly and provide access to all features and content at the time of review, regardless of network, device capability, location, etc.
Next Steps
To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.
How can we make the app geo-restrict and also provide access to all features?
Thank you.
Specifically, upon launch, your app displayed an error message.
Was your error message clear to the user, explaining what had happened and what they must do to resolve the issue? Did you explain this restriction in your App Store description (particularly if you're submitting to any store where the restriction would apply), and in your App Store submission? Even if the user cannot proceed, they should have a good experience. It shouldn't just be an alert saying "go away." A legitimate user might launch your product while traveling, and it should be clear that they need to wait until they get home.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
This is the key point. Contact them. You may need to give them a backdoor that unlocks it for the Apple site. You may need to give them a special login. They may work with you in other ways. But contact them.
When you say "keeps getting rejected," that suggest more to the story. Did you contact them and did they tell you other things? Did you just keep submitting?
even though your app is geo restricted,you need to implement code for testing purpose so that they can test all the functionality of the app.i suggest you create a user for testing that will bypass the geo restriction and specify the name and password at notes in app submission.
App Review:Rejected - Design 4.2.2
Message from Apple Review Team:
Please revise your app concept to provide a more robust user experience by including native iOS features and functionality.
What native features do iOS devices have, I really don't have a need for Health-kit, gyro-meter and camera.
I already have Offline data sync and Push notifications included, what else could I possibly use in the very limited iOS feature hut?
Apple has made this rule around before 2 or more year ago. Actually this is because there was so much rush of the template kind of apps with less features & due to that the other quality Apps was getting less attention.
There is 2 possible ways to get out this situation :
You can explain apple review team by high lighting key features of your app & try to convince them that your app contains enough features to get approval. You can post message just below the rejection message by them.
If 1st option does not works & they are not convinced by the features than you must than add few more helpful features in the app & upload the new binary.
Important note :
In case of adding new feature & submitting new binary don't forget to add comment on review notes that you have added few key features & app is now with full of features as per the apple rules.
Hope it will help you.
I've noticed that Instagram and some other apps allow users to report problems but don't actually let people report "bugs". Since I guess the premise of the Apple review process is they catch all bugs and there are no bugs in IOS apps, it makes sense that they do not use the word.
However, is Apple likely to reject the app if you use the word "bugs"?
Coming from a web background where it is okay to launch with a beta, I would like to be honest with users rather than politically correct if that is possible.
The reason I want to let them report bugs is not so much to catch them as we hope to launch bug-free but if anyone has a problem let them report it rather than write a bad review.
Would appreciate any guidance.
Thank you.
Apple review guideline;
2. Functionality
2.2 Apps that exhibit bugs will be rejected
I don't think this means that they have a filter on the word 'bug'. You may find some bug tracking apps available on the app store where they used the word so rejection it not a given, just because of a report bugs section in your app.
But at the time of an Apple review, if they find any bug, they will reject the app so that you may fix it. So you need to be very sharp at it that your app should not have any permanent bug or issue.
For confirmation you may contact App Developer support at https://developer.apple.com/contact/submit.php
You need to avoid using bug, beta or similar words. The phrase Bug report gives users the impression that your app has known issues. I would recommend Send feedback or Contact developer.
The App Store Review Guidelines does not allow you to submit beta apps.
2.9
Apps that are "demo", "trial", or "test" versions will be rejected.
Beta Apps may only be submitted through TestFlight and must follow the
TestFlight guidelines
Similarly, you should not leave known issues present in your app. If you already know the issues, you need to fix them before you submit the app.
For example, when I wrote Please reboot the app if it freezes in the description, it was rejected.
I recently got a phone call from Apple saying they would reject our app since there's a problem with the metadata. I asked whether there's a problem with the app itself and she said she doesn't know because she's not part of the review team. She said it should be ok.
So I changed my metadata and resubmit the app, and the status now is in review. According to itunesconnect programmer guide, they will reuse the binary. Does that mean the binary is good? Is it possible that they will take a look at the app again and reject me for some reasons other than they specified in the resolution centre?
I know this is a question that probably only apple can answer, but this is our first app so i don't really know how it works. I asked apple but they didn't tell me anything.
You do not need to upload new binary. They will review it again and approve it (or reject for other reason). It took only few hours in my case. But you can't be sure the binary has already been checked. Maybe they only did the metadata so far and will check the binary after your metadata correction. Anyway, no need to upload anything now.
Usually reviewers stop their review process as soon as they find an issue. This means that the metadata rejection can be the first of a longer list (hopefully no!) or that they reviewed your whole app and found the only issue at metadata level only: in such case fixing your metadata should be enough.
Recently I saw one of my apps rejected due to a mistake in adding an In App Purchase (basically the app was referring to an IAP still not in iTunes). After fixing it (no binary change, just adding the "in app") they found an issue in the app this time and then the binary was submitted. It would have been quite easier for me to know of the two issues together and fix them once, instead the triple-trip delayed my final app submission by 10 extra days (consider 5 days between two consecutive reviews)
From my experience, it doesn't always mean the binary is good. They may have very well reached the point of checking metadata and found an issue without testing the binary itself. Expect the Unexpected with Apple.
This is due to metadata information, no need to upload new binary. They will review it again and approve it (or reject for other reason). In my case, I was using location in background mode but in my Application description did not include the required "battery use" disclaimer, I changed the meta data (Application description only) according to apple message. It took only few hours (hardly 4 hours) and application was live. I was socked :) because some people was saying, It will take upto 7 days(as apple normal process).
Following was reason for app reject in my case(Below was the mail, I received from Apple)
From Apple
* 2.16 - Multitasking Apps may only use background services for their
intended purposes: VoIP, audio playback, location, task completion,
local notifications, etc.
2.16 Details
Your app uses the Location Background mode but does not include the
required "battery use" disclaimer in your Application Description.
Next Steps
Please add the following disclaimer to your Application Description:
"Continued use of GPS running in the background can dramatically
decrease battery life."
Please see the app store screenshot for confirm.
In my experience, they reject the app as soon as they find a reason and they won't review it any further until next submission. So if the metadata is rejected it does not mean that they have approved the binary.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
Can anybody help me out to know the possible reasons for which Apple store can reject or raise objection to submit any iPhone application.
Here are possible reasons (unofficial, from here):
Vibration. It is not permitted to use continuous vibration in your apps - short bursts as warnings is all that is allowed. Don’t bother trying to set up a timer to keep the vibration going, it will cause your app to be rejected.
Linking to private frameworks. This is obvious, but somehow in playing around with stuff we had linked to the MoviePlayer.framework. That’s a no-no, and cost us about ten days while we unlinked that framework, recompiled, and then resubmitted.
Improper handling of editing in tableview cells. Also obvious, but be aware that if you enable table cell editing, you’ll have to manually specify which cells should respond to editing controls and which should not. We had some random prefs cells in one of our early apps that were able to be swiped to bring up a ‘delete’ badge. Of course it didn’t do anything, but Apple justly considered this poor design and rejected our app.
Icons. Make sure the 57 pixel icon is identical to the 512 pixel version. Also, use a different icon if you are creating ‘lite’ and ‘pro’ versions of your app (i.e., free and paid). Using the same icon for both sends your app straight to … you guessed it … the bin.
Copying existing functionality. This one is much more subtle and insidious, and has probably affected the great percentage of developers. In addition to the widely publicized Podcaster debacle, reports from user comments indicate that Apple is casting a wide net when looking for duplicated functionality. Mini web browsers, or apps that essentially show web pages, seem particularly vulnerable, even if they add new and/or useful functionality. Stay away from email clients as well.
Using appropriate keyboard type. If your app asks for a phone number or other numeral-only input and you present a keyboard that also includes the possibility of entering standard alpha-numeric input … yep. (Thanks Jeremy1026)
Version numbers. If your app is currently at version 0.99 or below, you’d better consider giving it a promotion as Apple seems to prefer 1.0 and above. One of ours was recently rejected for being .016, with a message suggesting that our version number wasn’t even numeric. When we resubmitted the same app from scratch as version 1.0, it went through.
Network Reachability. If your app requires any type of network access you need to make sure it works when that access isn't available. If it doesn't it will be rejected. Apple provides sample code to test this which you can use as-is in most cases: https://developer.apple.com/library/content/samplecode/Reachability/Introduction/Intro.html
And last, but not least:
Flatulence Don’t even try. ;-) UPDATE: sorry, this seems to be outdated by now. Apple makes a lot of money now with "fart apps": see this article.
Edit:
Here is a link to a recent article about ten iPhone Apps That Didn't Make Apple's App Store.
And a tip: Apple has a Mac app called Application Loader that you could install. Once you install it, it analyzes your app's zip file. It verifies all the certificates, icons, and other things are correct before submitting to Apple. Using the Application Loader minimizes your chances of app rejection.
Another interesting resource: App Store Roundtable: Transparency and the Approval System (appleblog.com)
Yet another edit:
New rules by February 2010: "No Swimsuits, No Skin, And No Innuendo" (source: TechCrunch article, Wobble author's blog)
By the way: during the iPhone 3.0 preview event (march 2009), an Apple spokesman told that 96% of all submitted application were approved.
Apple have now (as of 9th September 2010) published their official list of app store review guidelines:
appstore approval guidelines
(apple developer login required)
or a mirror here:
app store guidelines
Will apple want to create an app like that in the future? If (yes) reject.
Do you have a really awesome idea that apple may want to use in the future if(yes) reject
Here's the video of the SDK announcement that describes Apple published list of rejection criteria:
SDK Announcement
As others have noted, Apple also seem to have a bunch of other conditions that they don't publicise. Note that rejection notices are now covered by the NDA.
I can't confirm this but it makes sense, but people are reporting their apps being rejected for being too simple or too trivial.
Just got a bounce for handling network outages badly. If you connect to the network, be prepared to handle any error conditions that may come up.
My paid version of app was rejected by appstore.
After Purchasing and downloading app first screen was "User Agreement" and when user taps on " I agree" only then he is able to continue using app.
Apple described the reason of rejection "when user purchased app from appstore and download in phone then you must not restrict user to Agree with Agreement" instead display your agreement before downloading app in iTunes.
Amazingly, apps can get rejected for trying to keep their interface consistent with Apple's own apps. (ie, using pinch zoom/expand gestures)
There is a site I know which can help you generate great advertising ideas with iPhone. see this site:
http://itunes.apple.com/app/adpack/id359562015?mt=8
I submitted a paid app to app store but get rejected and i learned another possibility of app rejection
My app was Game Center enabled. When app starts first screen was login screen that prompt user to login through GameCenter to continue.
They rejected the app giving reason- As user will not be able to get services of your app unless he is not logged in with Game Center although he paid you to download app. You cannot restrict user to login through Game Center each time before app starts.
From 1st May,2013 onwards if we don't support iPhone 5, your app will be rejected.So iPhone 5 support is must.