4.3

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.

The recent 'spam' objections are all directed to the same developer publishing similar versions of the same app for different 'stores' (i.e. multiple apps for different Barber Shops - one for in each town in California). While your app is the same it will hit the App Store from two different developer accounts so the App Store will not apply that recent concern to the two apps. But your app does have similar code so it still violates the 'spam' 4.3 guideline; but does it? Won't the versions be localized differently; one in Chinese the other in English? If so, go for it.

Hi Add me to the list of 4.3 victims. I have a very niche client/server app that has been on the store for nearly 12 (TWELVE) years! (the software consists of 2 apps, the client and the server), so this is just an update, not a new app. There is NOTHING even remotely similar to it as it is a very niche market with a limited userbase. We did an update 2 weeks ago (client) and everything went fine. Of course after updating we noticed a couple minor changes that needed to be made, nothing operational, all cosmetic like a spelling error and limiting the number of ad's shown. Literally changed 5 characters in the source. Submit a new build and now we are in 4.3 spam hell. Of course we keep getting the same canned response from the review team that tells us absolutely nothing. Appealed the rejection last week, and so far, not a peep out of Apple. No calls, no emails no nothing. We also updated the server app, and no problems whatsoever. The 2 apps are totally different, but all i can suspect is po

There are actually apps doing this already, like Mathletics, Raz kids. So each school gives the teachers, students / parents the school login AND the individual login for students.But for some other cases , e.g. the Church example i saw in another thread, 4.3 guideline doesn't make any sense.Religious people would search for their own church on the app store naturally, say Michigan state Pentecostal ABC church or whatever. The problem is if it was under one container app, the religious person would most liklely unable to search for the app since there can only be 100 characters in the keyword field and there is no way to fit all church names in it.

Apple rejected many times.What to do ? Please help me. 4. 3 Design: Spam Guideline 4.3 - Design - Spam Your app primarily features astrology, horoscopes, palm reading, fortune telling or zodiac reports. As such, it duplicates the content and functionality of many other similar apps currently available on the App Store. While these app features may be useful, informative or entertaining, we simply have enough of these types of apps on the App Store, and they are considered a form of spam. Next Steps We encourage you to review your app concept and incorporate different content and features that are in compliance with the App Store Review Guidelines.

I have the same problem. I made a game, uploaded it, and passed the moderation. Then, when updating to a new version, after adding in-app purchases using RevenueCat, I received a rejection. Guideline 4.3 - Design We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. The game is also written in Flutter. Could that be the issue? Any ideas on what to do? I've already rewritten it from scratch twice, with entirely different code.

Read the guidelines. Spam may be because your app falls into an overcrowded category without enough innovative features. Dating apps are just such a category. 4.3 Spam (b) Also avoid piling on to a category that is already saturated; the App Store has enough fart, burp, flashlight, fortune telling, dating, drinking games, and Kama Sutra apps, etc. already. We will reject these apps unless they provide a unique, high-quality experience. Spamming the store may lead to your removal from the Apple Developer Program. So, the only thing you can do is to add comments to reviewer explaining how your app provides this unique experience.

Thank you for your post. We believe we have resolved this issue as we see you were able to discuss this with an App Review representative during Meet with Apple. If you continue to experience issues during review, please contact us. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you disagree with the outcome of our review, you may consider submitting an appeal to the App Review Board. The App Review Board will contact you directly as soon as they've completed their investigation.

Apple reviewers are just taking the 4.3 guideline out of context these days.Your Church app(s) is a perfect example of how this guideline fails.Main thing is the searchability. Each country, each state, each city probably has multiple churches, one person who goes to, say, Michigan state , Midland Pentecostal Church would probably simply search michigan church on the app store.But if all church apps in the country is under one app he / she will get no search results since the developer just can't fit all the states in the keywords...

The current App Distribution Guide says For example, the lowest available setting for iPad apps is iOS 4.3. ( Setting the Deployment Target ) but my Xcode 7.1.1 doesn't seem to allow any deployment target for an iPhone project to be lower than iOS 6.0. So YMMV I guess. Basically the minimum is whatever the minimum supported Xcode version (Is Xcode 5 still allowed or does the store now require Xcode 6? I don't know) allows in the popup for the project deployment target.One other factor - if you use Swift that limits you to iOS 7.0 and later.

Thank you for your post. There are several factors that may contribute to an app not following App Review Guideline 4.3. Typically, these apps share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences. If you have questions about App Review's review of your app, we recommend requesting an appointment with App Review during the bi-weekly Meet with Apple event. Sign in with your Developer ID and select App Review Appointment. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Appointments are subject to availability during your local business hours on Tuesdays and Thursdays.