Could I implement a button in my application that would open an external link where people could register their account? Just like the Netflix or Disney Plus app has. I think my application falls under the category of "reader" app, just like Netflix and Disney Plus. While I was developing the app, the apple review team rejected my app because of the button to the external registration page. But I see that all other applications that belong to the Reader app have a button, so I'm interested if someone can help me, what do I need to do to enable the button to the external user registration page? best regard Nemanja Nedelkov

Hi, Thank you for your feedback regarding our app submission. We understand that the latest version was rejected under Guideline 4.3(a) - Design - Spam. We would like to confirm that our app is unique, combining casual gaming and video chat to deliver an engaging and distinct user experience. This update is critical for ensuring optimal performance on iOS 18 and providing a seamless experience for users who have already upgraded. We hope to resolve this matter fully and avoid encountering similar issues with this guideline in future submissions. We kindly request that the review team re-evaluate our app’s uniqueness and design. Additionally, we would greatly appreciate your assistance in expediting the review process so we can release this important update to our users. If further clarification or additional information is needed, please don’t hesitate to reach out. Thank you for your understanding and support. Best regards, The Fachat Team

Not using beginRefundRequest like method from client side code, Can I ask apple to refund specific order from website or help center? If it possible where is the ask to refund menu in appstore connect or other?

Hi, I was notified about quarantine files but I don't know why? ITMS-91109: Invalid package contents - The package contains one or more files with the com.apple.quarantine extended file attribute The mentioned file is to project logo as PNG image. The PNG file is located here: MyApp.app/Contents/Resources

Hi everyone, I’m experiencing a frustrating issue with my iTunes Connect account and could really use some advice or insights. Here’s the situation: I recently added my banking information on iTunes Connect. The system initially stated that the updates would process within 24 hours. However, it’s now been nearly two weeks, and nothing has progressed. I’ve contacted Apple Support, and my concern was referred to the Financial Support team, but I’ve only received generic responses stating that my account is under review. Here’s what I’ve done so far: Sent follow-up emails to the Financial Support team, requesting a status update and asking to speak to a supervisor. Reached out to the original support engineer and asked them to escalate my case to their manager. Despite these efforts, the issue remains unresolved. The delay is preventing me from releasing my free app. Has anyone encountered a similar issue with banking updates taking this long to process? If so, how did you resolve it? Are there any additional escalation steps or alternative channels I can try?

"keychainAccess" is my embedded framework. Error installing '/Users/santoshkumar/Downloads/FieldWorkSTG_V1826.ipa', ERROR: Error Domain=com.apple.dt.CoreDeviceError Code=3002 "Failed to install the app on the device." UserInfo={NSURL=file:///Users/santoshkumar/Downloads/FieldWorkSTG_V1826.ipa, NSUnderlyingError=0x600009f27090 {Error Domain=IXUserPresentableErrorDomain Code=1 "Unable to Install “FieldWork STAGE”" UserInfo={NSUnderlyingError=0x600009f27360 {Error Domain=MIInstallerErrorDomain Code=71 "FieldWork.app/Frameworks/KeychainAccess.framework is missing its bundle executable. Please check your build settings to make sure that a bundle executable is produced at the path "FieldWork.app/Frameworks/KeychainAccess.framework/KeychainAccess"." UserInfo={NSUnderlyingError=0x600009f273c0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo=0x600004c8c940 (not displayed)}, FunctionName=-[MIExecutableBundle executableExistsWithError:], SourceFileLine=1580, NSLocalizedDescription=FieldWork.app/Frameworks/KeychainAccess.framework is missing its bundle executable. Please check your build settings to make sure that a bundle executable is produced at the path "FieldWork.app/Frameworks/KeychainAccess.framework/KeychainAccess".}}, NSLocalizedDescription=Unable to Install “FieldWork STAGE”, NSLocalizedRecoverySuggestion=FieldWork.app/Frameworks/KeychainAccess.framework is missing its bundle executable. Please check your build settings to make sure that a bundle executable is produced at the path "FieldWork.app/Frameworks/KeychainAccess.framework/KeychainAccess"., NSLocalizedFailureReason=Please try again later.}}, NSLocalizedDescription=Failed to install the app on the device.} Domain: com.apple.dt.DVTCoreDevice Code: -1 User Info: { DVTErrorCreationDateKey = "2024-11-13 07:28:18 +0000"; } -- Error installing '/Users/santoshkumar/Downloads/FieldWorkSTG_V1826.ipa', ERROR: Error Domain=com.apple.dt.CoreDeviceError Code=3002 "Failed to install the app on the device." UserInfo={NSURL=file:///Users/santoshkumar/Downloads/FieldWorkSTG_V1826.ipa, NSUnderlyingError=0x600009f27090 {Error Domain=IXUserPresentableErrorDomain Code=1 "Unable to Install “FieldWork STAGE”" UserInfo={NSUnderlyingError=0x600009f27360 {Error Domain=MIInstallerErrorDomain Code=71 "FieldWork.app/Frameworks/KeychainAccess.framework is missing its bundle executable. Please check your build settings to make sure that a bundle executable is produced at the path "FieldWork.app/Frameworks/KeychainAccess.framework/KeychainAccess"." UserInfo={NSUnderlyingError=0x600009f273c0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo=0x600004c8c940 (not displayed)}, FunctionName=-[MIExecutableBundle executableExistsWithError:], SourceFileLine=1580, NSLocalizedDescription=FieldWork.app/Frameworks/KeychainAccess.framework is missing its bundle executable. Please check your build settings to make sure that a bundle executable is produced at the path "FieldWork.app/Frameworks/KeychainAccess.framework/KeychainAccess".}}, NSLocalizedDescription=Unable to Install “FieldWork STAGE”, NSLocalizedRecoverySuggestion=FieldWork.app/Frameworks/KeychainAccess.framework is missing its bundle executable. Please check your build settings to make sure that a bundle executable is produced at the path "FieldWork.app/Frameworks/KeychainAccess.framework/KeychainAccess"., NSLocalizedFailureReason=Please try again later.}}, NSLocalizedDescription=Failed to install the app on the device.} Domain: com.apple.dt.DVTCoreDevice Code: -1 -- System Information macOS Version 14.5 (Build 23F79) Xcode 15.4 (22622) (Build 15F31d) Timestamp: 2024-11-13T12:58:18+05:30

Hi, I’m a developer working on iOS applications, and I need access to a TestFlight invitation code. This will help me test [briefly describe your purpose, e.g., a beta app or a tool]. Could you please provide me with the code or guide me on how to access it? Thank you so much! Best regards, [Edris Rahimi]

Third-party analytics SDKs, such as Firebase, can collect and analyze in-app purchase data without requiring explicit coding by developers. How do they achieve this? Does Apple provide a mechanism to monitor in-app purchases, or do these SDKs implement runtime monitoring of the system’s in-app purchase process themselves? Additionally, I noticed that when using StoreKit 2 for in-app purchases, Firebase require developers to explicitly write code to enable the collection of in-app purchase data. Is this because the StoreKit 2 framework no longer supports arbitrary services implementing runtime monitoring of in-app purchases?

We have an app that’s been in the store for a year, and the latest version was rejected for Guideline 5.6 - Developer Code of Conduct. The app attempts to manipulate customers into making unwanted in-app purchases. Specifically, the app shows a one time offer for subscription when the user closes the initial subscription page launched upon opening the app. Essentially we have a soft paywall at the end of onboarding, and if the user closes that paywall we pop a second paywall with a one-time offer with an introductory offer (2 months for $1, “Once you close your one-time offer, it’s gone!”). We’ve had this in the last few versions of the app, but not been flagged for it. The strategy of having a one time offer after end of the onboarding paywall is not uncommon, and we are copying the approach used by many other apps in the app store. Limited time offers are a staple of marketing across all types of B2C stores. Does anyone have any experience with this type of rejection? Should we stick to our approach and escalate to a phone call? Change the one-time offer to a “limited time offer” (e.g. reduced price for 12 hours) so there is less pressure to decide right then? It’s a strange rejection because it doesn’t seem like we are doing anythign unusual. An onboarding soft-paywall followed by a one time offer is less of a push than a hard paywall (which is approvable), and offers some people an appealing way to test the app before committing to pay for a subscription (which doesn’t offer free trials). However, we don’t want to get flagged as a bad actor by the App Store reviewers.

I'm currently in the process of submitting a new app with a single non-consumable In-App Purchase. After creating the IAP in AppStore Connect, I created a synced StoreKit config in Xcode which correctly loaded the purchase. After making sure that the transaction works as expected within the app, I submitted the app in AppStore connect, including the In-App Purchase. Since then, the In-App Purchase can not be found in the StoreKit configuration and isn't displayed in the app, which lead to the submission being rejected. As requested by the review team, I have resubmitted the In-App Purchase, so it's currently "Waiting for Review" but still not showing up in the StoreKit configuration in Xcode. I'm not quite sure what I'm doing wrong here. I have other apps live in the AppStore with IAPs and no outstanding agreements to sign.

My iOS app has been in beta via TestFlight for 2 months without any issue. I use FlutterFlow and Firebase for my app build. I added the RevenueCat paywall and entitlement queries per their integration documentation. Within an hour or two of testing paid app subscriptions I lose access to iMessage on my iPhone and when I call Apple they say it's because the device/number has been reported as spam. This has now occurred on two separate devices with two different cell carriers which is frustrating since Apple representatives mention that they only perform a "one time exception" to reinstate iMessage privileges. The paywall and subscription to content is working perfectly. However, I don't feel confident releasing the app until I can confirm this won't happen to customers in production. I have no clue how to begin to test and troubleshoot this sort of issue outside of risking my personal phone numbers since it seems out of my control. Any insight or ideas?? Thanks so much!

Hi, I am stuck at "Design Spam", I have done numerous revisions but still i am getting "We still 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." from app review team. The app which I am trying to submit is a simple social media app, and its been almost a month it could not pass the review. I have updated meta data, updated assets but still app is getting rejected. Has anyone faced similar case, if yes then how did they solved it? Any help would be appreciated. Thanks

I published an app to TestFlight today and the invitation email has the wrong company name. The invitation has the correct icon image and below it, the [app name] By [company name] for iOS. The problem is, the company name is actually a different app name that I had reserved and not the name of the company for which the developer account is associated. How do I ensure that future builds will have the correct company name in the TestFlight invitations?

My app was denied because the 6.7" screenshots are outdated. But I can't find the 6.7" screenshots to update them. So I am stuck I can't update my app.

Hello everyone! I hope I'm on the right forum topic... I have a question about payments on the app store. I am in the process of developing a mobile application that allows families to post photos on the application. Each month, all the content posted is put into a journal which is then printed and sent to the family's grandparents. So my app sells a physical product. I'd like to know more about the 30% tax on in-app purchases. I don't think I'm eligible since it's a physical product, but I'm not sure. My question also arises if I offer a monthly subscription system to receive the newspaper each month? Thank you very much in advance for your answers! Loïc

In TestFlight, it normally takes 24 hours to process a new build. However, I've been waiting for the last 3 days to test our new build. Why is it taking so long? Can someone please explain the reason?

What should I do when my Development or App Store certificates in my developer account under Certificates, Identifiers & Profiles are almost expired or when the certificates are already expired? What should I do so that I can still use the certificates? What happens when the certificates expire and when I already have an application in the App Store?

I am developing a watchOS app that uses the uses the Fall Detection API. After requesting the entitlement, and receiving the entitlement and adding it to my app, I managed to implement the feature, and run the app on the simulator in Xcode and it works fine. But when I try to distribute the app to TestFlight internal testing, Xcode refuses and shows the following message: "Provisioning profile failed qualification: Profile doesn't support Fall Detection Notifications" and "Provisioning profile failed qualification: Profile doesn't include the com.apple.developer.health.fall-detection entitlement" I am using an Xcode managed provisioning profile, and when I checked the profile from "signing and capabilities", it says that the fall detection capability and the entitlement are included in the profile. When I check my app's capabilities from "Certificates, Identifiers & Profiles" in the apple developer website, it says that the fall detection capability for my app has provisioning support for Ad hoc and Development only, is this the reason why I can't upload my app to TestFlight, or am I missing something? If it is the reason, then is there a way to change the provisioning support so that I can distribute the app? Thanks in advance

I’ve been following the Apple documentation on Configure Multiple Product Page Versions. However, I still have some questions about the functionality. https://developer.apple.com/help/app-store-connect/create-custom-product-pages/configure-multiple-product-page-versions/ A user clicks a UniversalLink from a webpage (with parameters attached) that leads them to the App Store multiple product, and downloading and installing the app. I’d like to confirm that the original UniversalLink parameters are still accessible and can be used on the app’s first launch? Are there any special configurations required to enable this? Thank you!

App ID: 6470781599 After receiving the mail below, my developer account was canceled and my app was taken down. I contacted Apple and they said they are reviewing it and haven't gotten back to me in 3 weeks. I was wondering if anyone has experienced the same situation and if anyone knows how much longer I should wait? Since it's a company app, I'm getting a lot of resentment from existing app users. Should I upload a new app? As previously advised, App Store Review Guidelines 5.6.4 (App Quality) states, "[Customers expect the best quality in the App Store, and maintaining high-quality content, service, and experience increases customer confidence. Signs that this expectation is not being met include excessive customer reporting and excessive refund requests for concerns about apps such as negative customer reviews. The inability to maintain high quality can be a factor in determining whether developers comply with the developer code of conduct," it states. You have not done enough to tailor your Apple Developer Program account to the Developer Code of Product. Therefore, Apple is exercising its right to terminate your status as an Apple developer under the DPLA. As an Apple developer, I would like to remind you of your obligations under DPLA regarding all software and other confidential information obtained from Apple. You must immediately cease and desist from any use of these materials and comply with all other termination obligations set forth in Section 11.3 of DPLA and Section 10 of ADA. If applicable, no additional payment will be made in accordance with Section 7.1 of the Paid Application Agreement (DPLA Schedule 2 and 3). This letter is not a complete description of the facts in this matter, and nothing in this letter should be construed as waiving any rights or remedies Apple may have. All such rights or remedies are hereby protected.