4.3

Thank you. We're in the same boat--dinged on 4.2.6 and 4.3.We make software for trucking companies. Large trucking companies have their own app developers, accounts and marketing teams. Small to mid-size companies don't, but want to be as competitive as the big guys or else they're toast.Our apps help those companies provide a level of service that their customers only expect from larger companies. The last thing they want is to be forced into some container app that screams we're not as good as the big guys!

Basically, I have been dealing with the same issue. Apple is just basically sending auto-responses. So here is basically what Apple will allow you to do.1. If you upload an app and get hit with 4.3 or 4.2.62. Build your container app3. Your container app will get rejected because of the auto scans apple is doing.4. Reply in the first rejected app that you have built a container app and reference that container app5. Apple will reply super quick6. Your app will go into review!So basically Apple is giving you one more app to make in your developer account... If you follow their rules they will work with you very fast. I don't like what is happening but I do like that they are giving us an option... Hope this helps everyone.

I also just got my container app rejected for 4.3... They tell you to create a container app and then they reject it... So expect it to be rejected. I had to submit to the review board because I know they will not read my comment. Good Luck

Good afternoon.I'm having the same problem and would like to know if there is any way we can come up with collective complaint demanding Apple to review guideline 4.3.Instead of improve the experience of users and developers it's harming.

We too have been caught by this. The robotic response and complete lack of any deeper insight is most frustrating. We even received a 4.3 rejection for an app which is brand-new and has NEVER been published before. Despite asking for clarification, we simply received the cut and paste answer. We are a small company, my customers don't want to aggregate their content, neither will they sign up for a devloper account on their own (which I read from others actually makes little difference in any case) as they can't agree to be bound by conditions over which they have no control. We are the developers, it is natural for us to work in this world, our clients don't want the hassle or lack the expertise and that is why they pay us to do the work. It's like the world has gone mad!

In the iOS 11 new guideline 4.3, Apple recomend that 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.“ Unfortunately, we noticed that, the number of in app purchase you can promote up on the product page is limited to 20 .(https://developer.apple.com/in-app-purchase/) => Promote Your In-App Purchases on the App StoreWith iOS 11, you can choose to promote up to 20 in-app purchases at a time on your product page, increasing discoverability for content previously only found inside your app. Users can browse in-app purchases directly on the App Store and start a purchase even before downloading your app.My question is, is it possible to browse all in app purchases available for one app directly on the Appstore ? I mean, even if we have more than 20 in app purchase ?As you know, our company develop official applications for sport team (we have about 100 teams.) According to th

Do those hundreds of apps all come from the same template(s), or app generator? >each client would like to see their own official app for their event.If they want their own app, they should have their own dev program account, in that case, but I suspect you'd still get pushback from Apple to use a 'container' app instead.Be sure to review the ASRGs - example 4.3 Spam

I completely agree with you. We at Mobifitness make apps for fitness clubs and gyms. There are some companies that do the same and suffer from 4.2.6 and 4.3 as we do. Mindbody, Migymapp, Perfect Gym, Technogym (My Wellness Cloud), Yclients, etc. You can't make a consolidated app while your business model is b2b solutions but not lead generation. We have 200 apps now. Please Apple, take from us $20.000 annually and allow to stay within one account and publish the apps that help customers of gyms to communicate with their managers. Best regards.

We also have the same issue. We strongly believe that Apple enforces this rule in good intention but in the wrong direction. Appstore is full of clones of low value and this seem to cause extreme burden to App Review Team and the whole ecosystem. The templated/white label industry though has a lot of great examples where it would not work otherwise:Example:Smart City Apps: Applications that are contracted to several municipalities throughout the world to offer e-services to citizens like complaints, parking payment, notifications for deadlines etc. These apps rely on robust backends with a lot of functionality and communication with the app. They cannot get consolidated (every city needs it's own identity, would be funny to combine cities in USA and Thailand and Ukraine for example in one app), and they will eventually share mostly the same code. Some functions may be available to some apps some to others, but essentiatlly they will have a lot of common ground. But each app will target extremely different peo

>Does creating multiple developer accounts solve this problem?Two different things. One is apps that are made via a template or app generator(4.3 design), the other is a Developer Program account that belongs to the content owner.Simply moving to an owned account won't help if the app is still made using a template/generator (4.3 design), etc. When both are an issue w/review, both have to be dealt with separately, I think. > Each one want an individual AppThat's where owned accounts come in. You can still do your thing as a dev, regarless of who owns the account.