rejected 10.1

Get Started | Login

Discussion Forums > App Store Rejections

Replies: 1 Views: 157

TraceCampbellBSNRN buzztouch Evangelist Posts: 233 Reg: Dec 16, 2011 Forney 3,680	confirm \| cancel 07/02/12 09:22 PM (13 years ago) rejected 10.1 10.1 We found that your app does not comply with the Apple iOS Human Interface Guidelines, as required by the App Store Review Guidelines. Specifically, we noticed your app contained popover elements that didn't point to the element that revealed them. To avoid user confusion, a popover element's arrow should point to the element that revealed it. Please see the attached screenshot/s for more information. For more information, please review the iOS UI Element Usage Guidelines section of the iOS Human Interface Guidelines. For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. Please be sure to: - include the complete details of your rejection issues - prepare any symbolicated crash logs, screenshots, and steps to reproduce the issues for when the DTS engineer follows up. For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports. If you have difficulty reproducing this issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Testing Workflow with Xcode's Archive feature". Screenshot of image uploader? http://a1809.phobos.apple.com/us/r30/Purple/03/50/fa/dj.ytatponh.png Does anyone have any ideas Title Comments 10.1 We found that your app does not comply with the Apple iOS Human Interface Guidelines, as required by the App Store Review Guidelines. Specifically, we noticed your app contained popover elements that didn't point to the element that revealed them. To avoid user confusion, a popover element's arrow should point to the element that revealed it. Please see the attached screenshot/s for more information. For more information, please review the iOS UI Element Usage Guidelines section of the iOS Human Interface Guidelines. For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. Please be sure to: - include the complete details of your rejection issues - prepare any symbolicated crash logs, screenshots, and steps to reproduce the issues for when the DTS engineer follows up. For information on how to symbolicate and read a crash log, please see Tech Note TN2151 Understanding and Analyzing iPhone OS Application Crash Reports. If you have difficulty reproducing this issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Testing Workflow with Xcode's Archive feature". Screenshot of image uploader? http://a1809.phobos.apple.com/us/r30/Purple/03/50/fa/dj.ytatponh.png Does anyone have any ideas

Space_Hippie I hate code! Posts: 6 Reg: Jul 05, 2012 Seattle 2,510	07/09/12 09:47 PM (13 years ago) This may be a stupid suggestion but 'Uploader' sounds like FTP and what I see is a camera utility. Of course, you're going to allow an image to be 'uploaded' but what is seen here is image capturing not uploading. Uploading event would be a button that actually initiates the actual upload process itself. Perhaps if you had two buttons in this state: CAPTURE MODE: button1 - Capture ACTIVE button2 - Upload INACTIVE UPLOAD MODE: button1 - Capture INACTIVE or Re-shoot image button2 - Upload ACTIVE Visually: CAPTURE MODE: [CAPTURE] [UPLOAD] [...ON...] [...OFF...] ************************* UPLOAD MODE: [RETAKE] [UPLOAD] [...ON...] [...ON...] or [CAPTURE] [UPLOAD] [...OFF...] [...ON...] *********************** Where OFF is visible but inactive and unclickable. Hope this is helpful Comments This may be a stupid suggestion but 'Uploader' sounds like FTP and what I see is a camera utility. Of course, you're going to allow an image to be 'uploaded' but what is seen here is image capturing not uploading. Uploading event would be a button that actually initiates the actual upload process itself. Perhaps if you had two buttons in this state: CAPTURE MODE: button1 - Capture ACTIVE button2 - Upload INACTIVE UPLOAD MODE: button1 - Capture INACTIVE or Re-shoot image button2 - Upload ACTIVE Visually: CAPTURE MODE: [CAPTURE] [UPLOAD] [...ON...] [...OFF...] *********************** UPLOAD MODE: [RETAKE] [UPLOAD] [...ON...] [...ON...] or [CAPTURE] [UPLOAD] [...OFF...] [...ON...] ************************* Where OFF is visible but inactive and unclickable. Hope this is helpful

Login + Screen Name Required to Post Login to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.