4.3

Hello, while creating the sample app I found a message in the debugger: Widget archival failed due to image being too large [1] - (6000, 4000), totalArea: 24000000 > max[2121055.200000]. Can you provide a table, what is the limit or how to calculate it? I found that this limit is different for all my devices. Now I use a magic number = 3.6. It is not the scale of the device screen, but something else. //ipad 10 sqrt(13.54) ~ sqrt(13) ~ 3.6 //iphone 16 pro sqrt(18.5) ~ 4.3 //iphone SE sqrt(17.59) ~ 4.1 And it is better to have documentation about it. And the archiving of images in the widget is not very fast. Especially it becomes a problem when using a long timeline. Even if the image is the same for all parts of the timeline, archiving is slow.

Thank you for your post and appeal. We're investigating and will contact you in App Store Connect to provide further assistance. 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 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 Experts 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.

Do your apps have the same icon ? Read those older posts: https://developer.apple.com/forums/thread/46910 https://developer.apple.com/forums/thread/114079 Did you consider inApp purchase, as recommended in guidelines ? 4.3 Spam Don’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 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.

Spam is not only a question of code, it may be also that is app looks too close to an existing app, so the experience is not unique or category is already too crowded. 4.3 Spam Don’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 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. Have you searched for other similar games on the App Store ?

Had an app denied due to spam saying an app with the same source code was submitted, which is basically impossible. Whenever I ask for more details, they slap me with the same line over and over again: For information regarding Guideline 4.3(a) - Design - Spam, you may want to refer to App Store Connect Developer Help. Should you require additional assistance, you can use the contact us page to request help with setting up or distributing your app through App Store Connect. Super unhelpful, roundabout conversations with absolutely no help or context or detail. Why don't I just contact them like they suggest you say? I click the contact link, and cant call them! it says: Phone support is currently unavailable.. Its been like this since as far as I can remember. The only way to get in touch is to email them and all they do is respond the same lines I gave above.

Let me try to understand what you are writing. Your app and device is on the market (#1 above) . Now you are trying to get approval for an additional app that interfaces with a similar device marketed by a different company (#2 above where with our own should be with their own). And the additional app has now been rejected under the guideline 4.3. Is that correct?You have two avenues forward -1) create a separate developer account under your clients name and submit the additional app under that account. Be sure that the additional app is really different from the user's perspective.2) (better IMHO) update your current app so that it is a generic app that can be used by either your device or your client's device (or future clients). Under that generic app create two branded options that the user selects. Advertise your device (and have your client advertise their device) as using the well-known generic controller for photo frames.

Thank you for your post and appeal. We're investigating this issue and will contact you in App Store Connect to provide further assistance. 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 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.

Just to clarify the situation in case someone can offer further insight: It's a new app and the reason it was rejected was 4.3(b) Spam - Your app primarily features astrology, horoscopes, palm reading, fortune telling or zodiac reports that duplicate the content and functionality of similar apps in a saturated category. -- but this seems to be a misunderstanding. My app’s purpose is quite the opposite of what was stated in the rejection. It’s a science-based educational experience that uses Greek mythology as a narrative hook, then guides users through constellations (not horoscopes or zodiac signs) to explore verified astronomical (not astrological) knowledge. The goal is to inspire curiosity about the universe through astronomy and not astrology. There is no horoscope, zodiac, or fortune telling content in the app. I’d really appreciate any additional feedback or help ensuring the app is accurately understood.

I believe your question is - how can I transfer IAPs purchased under one or more apps to a new 'container app' that I am creating to satisfy Apple's 4.3 issue.Revise the current app so it:1) flashes an introductory screen telling the user that the app functionality has been transferred to a new container app that they can download for free from the App Store. Include a link to that new app. Apologize for this inconvenience caused by Apple's new policy. Tell the user that this will allow them to access multiple 'thingies' (e.g. Barber shops, movie theaters, museums) all under the new app. 2) load the user's purchased IAPs into their key-value file in their iCloud account or use the shared space in the keychain or a shared NSUserDefaults file3) Tell App Review in the review notes that this revision is being pushed into the App Store to switch users to the new container app.Create a new container app that looks at the shared space to credit the user with their IAPs.

Precedent & Fairness in Enforcement Rove is an intentional, safety-forward dating product. It is neither spammy, low-effort, nor duplicative — and yet we continue to face rejections under Guideline 4.3(b). This raises serious concerns about selective enforcement of App Store policy. In the past 60 days, Apple has approved a wide range of new dating apps, including: • Ready: Dating & Relationships – Launched June 3, 2025. Marketed as a native app for “intentional dating,” with a thematic approach directly comparable to Rove. • Meetline – Launched May 15, 2025. A transit-based connection app that limits conversations, just like Rove limits user visibility to avoid overload. • Yuzu – Asian Dating & Friends – A non-swipe app tailored to a specific community — proof that niche dating concepts are not inherently duplicative. • Metya / DateGuard – Two safety-first apps that use community filters and moderation-centric design. These are directionally aligned with Rove’s own innovation in safety a

Excellent points raised. I believe that the problem with 4.3 rule is that Apple does not evaluate at what point the difference in content justifies the existence of a separate app.We are developing theory test apps for the UK market and were contacted last year demanding some consolidation. We've been able to resolve it with Apple by removing all our paid apps from sale and instead using in-app purchases. I thought that it was a great solution as it indeed reduced the number of apps while allowing us to keep one app per each vehicle category (Car, Motorcycle, etc.) Recently, we've been contacted by App Review, and they now demand that we make further consolidations.From a marketing point of view, further consolidation makes no sense. Users are accustomed to seeing learning materials being separated by a vehicle category and would be puzzled if such a real-life model did not exist on the App Store. Imagine if you search for Motorcycle Theory Test and all you see are a list of Driving Theory Tests.The

Oh my.... and I thought I was the only one having this problem with AppleI have four AppsPoolAppLive, DartsAppLive, SnookerAppLive and LeagueAppLive, all have different features, logos, text and all are marketed brands.All use a core scoring feature (obviously)All these were on the App Store before this 4.3 policy was introduced or changed.Now Apple wants me to produce one App that has an initial menu to pick one of the sportsCoding this is easy enough, but why would I want to do this?Each App has it's own identity and brand by design. Each is linked to a customer website , for example mktpl.poolapplive.com each has been advertised seperately at cost to myself. I want customers to find my App by simply typing in the brand name as they already do on both Android and iOSI am not spamming. I find this really quite insulting, if it wasn't for developers like myself Apple would be selling their devicesWe also pay for this service (unlike other app stores)I agree spamming should not be allowed, but this is

Same here. Can`t solve it. Getting this problem during the upload to ITC after a successful build. A collegue of mine can upload the exact same app but gets than an email with the following help:Invalid Binary Architecture - iOS 3.0 introduced support for multiple binary architectures. If your binary is built for multiple architectures, your Info.plist must have a MinimumOSVersion key with a value of at least 3.0. Additionally, if your app is intended to support earlier iPhone and iPod touch models, your app must contain at least an armv6 binary; thin armv7-only binaries will not be accepted unless the armv7required device capability is also present in the Info.plist UIRequiredDeviceCapabilities key or the MinimumOSVersion key has a value of 4.3 or higher.- our deployment targets are iOS 11 and watchOS 4- the Build Setting Valid Architectures for iOS is arm64- the Build Setting Valid Architectures for watchOS is arm64_32 armv7kIn the iOS info.plist we have in the Required device capabilities with arm

Hi meaton, Thanks for your reply. IANA has defined a well-known range, 192.0.0.0/29, in [RFC6333], which is dedicated for DS-Lite. Android implement CLAT since 4.3 version, i will got a 192.0.0.x ip address as expected when i connect to the NAT64 WIFI . iOS 15 /macOS 12 will not got a 192.0.0.x IP assigned on the same NAT64 WIFI. The same issue was found on https://www.reddit.com/r/ipv6/comments/10dylht/ipv6_ipad/. so, I think that 192.0.0.x is not vend back by the AP, but assigned by iOS 16/macOS 13. I doubt the latest macOS/IOS implement CLAT. Can you confirm it with the apple engineer？ ========================= https://www.rfc-editor.org/rfc/rfc7335.html https://www.rfc-editor.org/rfc/rfc6333 https://developer.apple.com/library/archive/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW1 https://www.reddit.com/r/ipv6/comments/10dylht/ipv6_ipad/

Running Xcode 6 or Xcode 7 on OS X 10.10 or 10.11, is there a way to test my app on iOS 4/5/6? Xcode 6 supports building for iOS 4.3 and laterXcode 7 supports building for iOS 6.0 and later Can older simulators work in these newer versions of Xcode? No. If no to both, is there a way to make old versions of Xcode run on 10.10 and 10.11? Will they work? The earliest version of Xcode supported on 10.10 is Xcode 6The earliest version of Xcode supported on 10.11 is Xcode 7 I'm working on a project which has contractual requirements for supporting super old iOS versions. The app also has some users on those versions, so dropping support for them isn't an option at the moment. It is not possible to build an iOS app that supports iOS 4.2 with tools that are capable of building for the App Store.If/when Xcode 7 is required, it will not be possible to build an app that supports iOS 5.x.