4.3

Same here. We have done dozens of apps which serve a particular type of business. Needless to say we try to produce them in a way that it is cost efficient for those businesses. But each app has a totally different look and the content is always different (each one has different data and data sources).Yes Apple is reject saying these violate 4.3. We have been doing this for years, have 700 clients and service customers from small to the largest of their kind in the world. Apple review used to be great and smooth and fast. Now it's become one reject after another that makes no sense with this 4.3. reject being the latest reject fad.

I am in the same boat. To target the little guys who are honest and create apps for small businesses that have different criterias and looks. We don't even make money off of it or are we targeting a wide audience. I mean if the YMCA in Louisville want their own app, we will create it and it will have similar funtionality as it hooks into our API scheduling system. The YMCA is targeting that area, not trying to make money. We dont use a commercialized template or app generation service. Our apps are unique, not another flashlight app. I mean are there really more then one YMCA of Louisville app?4.2.6 Apps created from a commercialized template or app generation service will be rejected.4.3 SpamDon’t create multiple Bundle IDs of the same app. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase. Also avoid piling on to a category that is already saturated; the App Store has enough

I feel it is less about what differences are inside the application, and more about Apple wanting to reduce the clutter in the Appstore.I am all for reducing the number of junk apps, clones, flappy games, and spam, but to outright tell all developers that they have to combine several games into a container app, some of which just don't belong together is overstretching this guideline.Apple needs to soften up the 4.3 guidelines, and allow developers to continue to publish apps that are branded toward the specific target market. eg: diet apps should not be combined. I as a customer would not want to download an app with multiple varying diets when I'm only looking for one specific one.Same with travel apps - if I want an app that caters to Paris traveling, I do not want NYC, Rome, London, Milan, & other cities in a bundle.The idea behind the agreement is well intended, but it's taken too far, without consideration for marketing & other things that come into play with the Appstore.So the topic i

Hi, My company is in a simaler situation. We create test prep apps for many certifications and have recently run into the 4.3 Spam rejection problem. Have you had any luck apealing the rejection?

Currently UNABLE to submit Stand Alone Sticker Packs created using the Xcode Template, due to the fact that creating an App ID ENABLES both Game Center and In-App Purchases, converting the underlying framework of the code-free Sticker Pack to that of an iMessage App. No way to edit and disable theses Features withing the App ID to submit a Stand Alone Sticker Pack intended ONLY for the iMessages App Store.This creates two problems:1. Unable to access the Archived/uploaded Build WITHOUT also uploading screenshots for the 'Optional iMessages in prepping the Sticker Pack for App Review2. Submitting more than one Sticker Pack App Review judges the app (Sticker Pack now converted to iMessages App via App ID Features ENABLED) on the basis of the underlying framework with Features instead of looking only at the appropriateness of the content (i.e. images) of the Sticker Packs. They reject submissions on the Rule 4.3 Design Spam (underlying framework is the same for Sticker Packs generated using the Xcode TE

According to the wikipedia Xcode, Xcode 6.4 is the latest version where minimum Deployment Target is iOS 4.3 or iOS 5.1.1.en.wikipedia.org/wiki/XcodeAnd currently you can submit apps with Xcode 6.x. (Though I'm not sure if you need it.)

Hello also, I would like to make an appeal on behalf of legitimate developers around the world. How long has item 4.3 be around? It seems like I’ve read that rule many months back. And after seeing all the spam apps on the market I wondered if this rule was even being inforced. It seems, perhaps, they are finally starting to do something about it.What is furstrating for legitmate developers is having to compete with all these thousands, if not millions, of spammed apps. Take Solitaire for example. Just do a search and you will find multiple developers all with the same exact solitaire game spammed 50+ times. Each of these apps are identitcal except for the background and the card back. And they all have 10 to 50—5 star reviews! Many of the reveiws are identical across multiple apps and developers. Do the math. And the worst thing is they utilize the keywords so that these apps appear in all sorts of searches.I trully love Apple’s quote in the Review Guidelines, “Come up with your own ideas. We know y

Is there any real resolution regarding this design 4.3 rejection?Our account belongs to a parent company which owns many subsidiary companies. Each has its own mobile app and shares some general app architecture and functions and of course provides certain company-specific functions. This app rejection design 4.3 seriously affects all our mobile app submission. We can no longer arrange app submission for new app or app upgrade. This really impacts our business. Seems this rule is tightened starting from end of June 2017 but poorly explained to public and affects many parent companies' strategies and app management. Any idea?Hope Apple can seriously review this design 4.3 rule which should stop real spam app but allows white label apps for different entities under parent company or any similar scenario like University app. It does not make sense to offer a single container unversity app for *** University aliance which actually offers services for many individual universities under t

> … not showing up in the boot menu when pressing Option key during bootup. …If the macOS boot volume is encrypted: it's traditional for the recovery option to be hidden from Startup Manager.Here:sh-3.2$ date ; uptime ; sw_vers Sat Jun 24 07:50:07 BST 2017 7:50 up 1:01, 2 users, load averages: 0.97 0.77 0.70 ProductName: Mac OS X ProductVersion: 10.13 BuildVersion: 17A291j sh-3.2$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *160.0 GB disk0 1: EFI NO NAME 104.9 MB disk0s1 2: 516E7CBA-6ECF-11D6-8FF8-00022D09712B 155.6 GB disk0s2 3: FreeBSD Swap 4.3 GB disk0s3 /dev/disk1 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_APFS Container disk2 499.2 GB disk1s2 3: Apple_KernelCoreDump 655.4 MB disk1s3 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +499.2 GB disk2 Physical Store disk1s2 1: APFS Volume High Sierra 14.3 GB disk2s1 2: APFS

Yes, Apple believes that 4.3 applies directly to what you are doing. To quote 4.3: If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and provide the variations using in-app purchase.Also, if your app is for use only by employees of each 'client' then consider using the Enterprise or B2B programs designed for such limited distribution.

You can still use iOS 7.x as a deployment target in the store, but not w/current tools (Xcode 8.3.2). I'd wonder about doing so, however, as number of users on an iOS that far back is in low single digits.Note that according to iTunes Connect, minimum now for the store is Xcode 6, which supports iOS 4.3 or iOS 5.1.1 minimum deployment, so to reach your goal of supporting older iOSs, you'd need to use older Xcode - restrictions apply, mainly not being able to also support newer iOSs, so...

You can still use iOS 7.x as a deployment target in the store, but not w/current tools (Xcode 8.3.2). I'd wonder about doing so, however, as number of users on an iOS that far back is in low single digits.Note that according to iTunes Connect, minimum now for the store is Xcode 6, which supports iOS 4.3 or iOS 5.1.1 minimum deployment.