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!

You've seen it and App Review has seen it, so we're left to our imagination what they witnessed that prompted your exact rejection, but I'd speculate that a tilt-puzzle is hardly original/unique these days. MazeTilt, HydroTilt, Tilt-to-Live, FallDown, Tilt Tilt Ladybug, Block tilt Escape, Gate Tilt, tilt The Box, Time Tilt Ball....on and on, the store seems well saturated, since at least 2010. Maybe they've just had enough...surprised they didn't just flag it w/4.3.

update Ok so i received another notice saying im violation the spam policy i deleted the duplicate submission, im not sure what the problem is now. maybe they didnt see the duplicate was deleted i replied back on the app store connect site clarifying Guideline 4.3 - Design We noticed that your app provides the same feature set as other apps submitted to the App Store; it simply varies in content or language, which is considered a form of spam. app id 1665868224

We got another app rejected because the app is not compliant with Guideline 4.3View on App StoreThis app displays waveforms of a sound file (typically spoken words), enables users to clip a certain area, make a sound clip playlists, convert it to MP3 using LameMP3 library, etc.We don't have any similar apps. We believe the store is not saturated with similar apps. The standard of the guideline 4.3 is getting very strict recently.

我也遇到了同样的问题，我用的是metal developer tool 4.3 for windows。生成metalsym时会出现“warning: 'test.metallib' architecture air64_v21 does not support a companion MetalLib; copying verbatim”，当我在xcode import sources时，仍然现在显示 metal code。

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

Did you receive any other feedback after that? What did they ask or argue on the phone? What did you write in the paper? Did they say if this means you should request a phone call and submit a paper everytime you submit/update an app for review or does it create an expcetion for your account or at least for the app?My company creates apps for churches and we are having the same problem. Each church wants its own app with its own brand, name, colors and visual identity but all of them need the same features (articles, musics, calendars, events and others). Because of that our apps are being rejected with the 4.3 topic justification.The main problem is that our clients (the churches) do not have any interest on having a single app with data from all the churches and a random visual identity - like Apple suggests in the review. They want their brand in the App Store but also at a minimum price. Our product offers exact that, but now with this new approach, Apple is killing our business model, frustratin

You may consider it a fanboy response but, the reality is, in some cases, xCode 7 for example, what youare asking simply may not be possible. If you're coding with Swift, iOS 7 is the lowest target possible.Once xCode 7 goes into release, xCode 6.x will only be allowed for a limited time period so, same issue.Right now, you can use xCode 6.x and as Simpsonics said, set the target all the way down to 4.3 if youwish BUT, not in Swift apps.

I got the 4.3 rejection for this app. https://itunes.apple.com/us/app/id1272669652?ls=1&mt=8This app is a law reader app. I have spend full 3 months to develop this. It also built on several years worth developing resources. I released it a month ago as an updated version of the existing app, which had over 1500 good users' reviews. It was by far the best app compared to similar apps from other developers. https://itunes.apple.com/us/app/id916069107?ls=1&mt=8 It is very handy app for law students and practitioners. The first several updates were fine, but suddenly I got 4.3 rejection on Oct 28. And the reviewer refused to say the exact reason. Only a template reply. No proper reply, no phone call. Yesterday I made a container app as they suggested and uploaded it.https://www.dropbox.com/s/z26xxfapsk56ant/Screen%20Shot%202017-11-08%20at%207.46.21%20AM.png?dl=0This includes my other app https://itunes.apple.com/us/app/20th-industrial-property-law-commentary-reader/id1217317638?ls=1&

Thanks a lot, I'll try your suggestion with bitcode and metadata (I don't use admob etc.).Do you have any more tricks to share?My experience: After couples of attemps to make apple approve my app, I've tried to create a new separate dev account for one of my apps, and I again got 4.3 and message saying identical apps.So my question is, how apple bot spots identical or simular apps and what could we do to pass thro this algorythm, at least on a separate account. If fair review doesn't work, we should at least find a workaround...

With opening the latest Xcode 6 (6.4), you'll see you can set the deployment target back to 4.3.As the deployment target is the minimum supported iOS version, your app needs to run on all iOS versions including both 32-bit and 64-bit if available,and needs to run on all models of iPhone/iPod touch/iPad which work with any of the versions you specified.And to test your app, Xcode 6 does not provide simulators of older versions, you need actual devices.

I am seeing the same behavior as well (Card Unavailable - Try again in a few moments). Have tried the following things but none did not resolve the issue:Restart Watch and iPhoneRemove credit cards and re-addReset the watchSign out of iCloud on iPhone and restart iPhone and Watch and sign-in again (with adding credit cards back to wallet)I have now filed a bug report with apple (#37449485), let's hope it will be fixed in the next Beta. Payments working fine in iPhone X with latest Beta, just not in WatchOS 4.3 Beta 2 with Series 0 watch.

The established technique is to examine the receipt of the app. It will have a field in it entitled original_application_version. That will indicate the 'Build' number (unfortunately not the Version number!!!) of the app that the user originally purchased. In your 'new' free app you use a different Build number - like 4.1 then 4.2 then 4.3. You use that Build number to separate the paid purchases from the free purchases.(iOS - Build number; for Mac Apps it's the version number)https://developer.apple.com/library/archive/releasenotes/General/ValidateAppStoreReceipt/Chapters/ReceiptFields.htmlhttps://forums.developer.apple.com/message/11915#11915https://forums.developer.apple.com/message/185419#185419

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...

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.