“4.3”

I've had an app on the App Store since 2011'ish with a Pro and Lite version.This week, updates to both apps were rejected for 4.3 Spam. My guess from searching forums is that this is not allowed anymore.How have you guys been able to resolve this issue? Do I have to delete 1 app so the other can be updated?This is really a bad catch-22 situation for me. If I delete Pro version, then lots of users are hurt. If I delete Lite version, then upgrade users are hurt and leaves users with no way to try out the full app.I don't want to do anything rash/permanent so please let me know your experiences.Thanks,Robert

I'd like to build an enterprise white label iOS app - that is, apply different branding to identical templates. Guidelines 4.2.6 and 4.3 seem to prohibit this as spam. However, I found these apps which clearly share the same template: ADM Farmview Valero Cornnow Scoular View Purefield Ingredients Graincraft Grower Connect Townsend Grain ...etc There are dozens more. To see them all search: site:apps.apple.com developed by the industry-leading Bushel platform. They have identical screenshots, description text, even version number. How can I do this, without being rejected for spam?

I am trying to upload a new build of my app from the new Xcode 14.1 RC but it keeps failing with the below error: ITMS-90428: Invalid Swift Support - The files libswift_Concurrency.dylib don’t match /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. Make sure the files are correct, rebuild your app, and resubmit it. Don’t apply post-processing to /Payload/MY_APP.app/MY_APP_WatchOS.app/libswift_Concurrency.dylib. My bundle contains a watchOS 4.3 app which I thought might have been an issue, so I tried increasing it to watchOS 7.0 but still got the error. Bitcode is disabled for all targets. I don't have post-processing enabled either.

Since a recent upgrade - Xcode 9.4, WatchOS 4.3, iOS 11.4, the Request Authorization at Launch Time in my watchApp is no longer generating the request authorization pop-up on the phone.My requests are appearing as if the user had provided authorization.Yes, I have uninstalled the app and rebooted all devices many times to see if there was something left hanging around.In itself, that's not a problem, as I want my users to accept Notifications, they are intrinsic to my app, but the problem is that the Simulator is not requesting authorization and denying it incenter.requestAuthorization(options: [.alert, .sound]) { (granted, error) in print(granted: (granted), error: (error!)) } }

Hi everyone, I’ve been reading Apple’s App Store Review Guidelines, especially the part about avoiding similar or duplicate apps (Section 4.3 on Spam). I noticed that the apps 航旅纵横 and 航旅纵横 Pro are both on the App Store. From what I can see, the two apps have some overlapping features, but the Pro version adds a few extra ones. I’m wondering how Apple approves apps like these. Are there specific rules or justifications developers need to follow to get similar apps approved? Thank you for any advice or insights!

Hello, I want to ask a question: about the problem that domestic copyrighted music content cannot be displayed to users in non-China regions. Specifically: There are some music in our APP (copyright only in China). Our APP needs to be localized internationally to support users to download and use it in China or other countries. Shows music that is not copyrighted. Like this kind of demand, Apple generally recommends how to do it? Do we need to create a Chinese version of the APP and a foreign version of the APP separately? How to avoid the repeated application of 4.3 audit problems? How to achieve better international display differences?

Hi all, I am dealing with a confusing issue relating to a beta build that I am trying to share over TestFlight. I have followed all steps and managed to upload a build to App Store Connect, but I mistakenly selected Internal Only when submitting from XCode. This build was accepted (See image), but then when I submitted a build that would be shareable externally, it was rejected under Guideline 4.3(a). I am unsure what had changed between the first and second build I submitted, and I have since updated the app page with more information and screenshots clearly explaining how this is different to other items available on the app store with no luck. Does anyone have any clue what I could do? Signed hopefully, Luke

I'm looking to distribute multiple versions of an iOS app, each customized with different branding for various clients. I understand that for public App Store submissions, guideline 4.3(a) prohibits multiple Bundle IDs of the same app to prevent spam. My question: Do these same restrictions apply to Custom App Distribution (unlisted apps)? Is it permissible to submit multiple white-labeled versions of the same core app through Custom App Distribution? I've reviewed the Custom Apps documentation but couldn't find clear guidance on this specific scenario. Any insights from developers who have experience with similar situations would be appreciated. Thank you in advance for your help!

Hi Apple,you forced my client to rethink it's valid white lable app solution due to the 4.3 rule (Spam restriction). Your only acceptable suggestion was to get a developer account for each of the customers for the correspondig app. The developer account forces to activate a two-factor authentication, which has to be activated on a Mac. Well it seems, that each Mac can only do it for 3 accounts, after that my client see an error, that the maxmum number of accounts is reached. My client has to migrate about 100 apps to the new accounts, how to do that without purchasing new Macs for every three accounts...?Cheers,Frustrated Developer

I've used PyInstaller to create an arm mach-o of a hello world python file. I then tried to sign the file using codesign and got the following error: language main executable failed strict validation When I create an x86_64 mach-o using the same method the codesign works without any issues. I'm using an arm64 only python 3.9 and PyInstaller version 4.3 I've tried codesigning on both M1 and intel, and codesigning a hello world compiled from C file with gcc works. Also, I've tried looking at the file compiled with PyInstaller using otool and haven't seen any issues.

I started the Xcode 7.1 update and it seems to have downloaded 4.5GB in the process.App Store is now showing xcode 7.1 as part of Updated Installed in the Last 30 days. However, when I open Xcode, it still shows 7.01. I checked files in Applications/Xcode and many files have latest timestamp (for example frameworks etc) so something seems to be updated. I restarted Mac but no help. Strangely, now it shows Xcode 7.1 in both Updates Available and also in Updated Installed in the Last 30 days. When I click Update, it again starts 4.3 GB download. Any idea what's going on ?Thanks

Hi, I got this problem and for more than 2 weeks and made all my applications to the app store are in the state of Waiting for review, because can not update that cause most users leave :(. I Do not know what to do, may help.From Apple4. 3 Design: SpamGuideline 4.3 - DesignWe 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.The next submission of this app may require a longer review time, and this app will not be eligible for an expedited review until this issue is resolved.

Our 13 engineers spent 197 days developing a live broadcast application, and we were very happy on August 23 because it was completed. Then came the indifferent bad news. The first time we submitted the app it was rejected. We noticed your app shares a similar binary, metadata, and/or concept as apps previously submitted by a terminated Apple Developer Program account. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Next Steps Since we do not accept spam apps on the App Store, we encourage you to review your app concept and submit a unique app with distinct content and functionality. Resources Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar a

We are preparing to submit a new app that shares some functionality and with an app we have previously distributed on the App Store. The Codebase will be different (the existing one was developped using React JS and the Second one usinf SWIFT). While the new app includes updated features, a redesigned interface, and is intended for a different user audience, we would like to confirm in advance whether submitting it as a separate app (with a new Bundle ID) is acceptable under current App Store Review Guidelines. In particular, we would appreciate clarification regarding Guideline 4.3 (Spam), to ensure that the submission will not be considered a duplicate or unnecessarily repetitive version of our existing app. Could you please advise on this matter?