Hey everyone, I’m developing an app can’t say the name at the moment but here is a similar scenario not very good, its the best I could come up with, say its a meditation app called ‘Fl0wr’. I’ve noticed there’s an existing app named ‘Flower’ in a different category, local news. Say for my app I add the following to the name Fl0wr - mindful and meditation. ’Will adding that to the name get it approved under Apple’s naming guidelines, considering the different spelling and the specific industry focus? Do I need to remove the dash make apart of the name. Hope that example makes sense. Any insights on this would be greatly appreciated. Thanks

Hello, Our account is experiencing very long review times for multiple (if not all) our applications. Some takes up to two weeks to be reviewed, which affects our business a lot. We often push multiple versions a week, including bug fixes and performance improvements. When we're unable to push these new versions out, our end users are affected and may experience issues with critical functionality. Our strategy is based on the availability of fast reviews, to be able to ship updates in a timely manner, but we are greatly hindered right now. We have not experienced review times taking this long ever. We understand that we're moving towards summer and holiday season, but haven't received any information about these sort of delays. Can you give any insight to why this is taking so long, and if there's any way to handle this? Example of review times for app (1395997293) version 1.9.28 Added 1.9.28 for review on the 4th of June Waited two weeks, still not reviewed Added 1.9.28 for review again, different build, same content Added 1.9.28 for review again, different build, same content - ACCEPTED This is just one example from our account, we've seen multiple versions on multiple applications experiencing this issue. Thank you, looking forward to your reply.

I have a big problem approving my app. My app contacts the backend with api calls to our server; we and our customers contact the bees without any problem but when the apple test to approve it, our server does not receive any requests so it would seem that the network used by apple testers does not reach our server. The verification team replies that they cannot carry out any tests/trials and that the app must work from anywhere in the world. has this happened to anyone? Can anyone help us solve the problem or at least understand where the problem might be? Thank you

Dear reviewers, Hello One of our products (id: 6477375218) released on Apple Vision Pro is currently experiencing an issue in the product backend, which has been ongoing in South Korea for over 24 hours. We suspect that there may be an issue in the backend and hope for assistance in resolving it. We need it to be in a supply state. Thank you sincerely

Hello, My app has gotten rejected because of guideline 5.1.1. My app required an account and a subscription to be used. Can someone please let me know how they were able to get approved? Would adding Apple sign in work? Would letting the user browse the empty app work? They cant of anything without a subscription so I don’t know why this is getting declined. I’ve asked if any of them would comply but the reviewer says they won’t offer any suggestions on app design, when that wasn’t the question. I just wanted to know if anything would make the app comply before I waste my time implementing anything.

Reason for rejection by reviewer: Guideline 2.1 - Performance - App Completeness We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue. Review device details: Device type: iPad Air (5th generation) and iPhone 13 mini OS version: iOS 17.5.1 Would anyone know why this is happening?

Hi everyone, I have seen a few posts talking about how restrictive Apple has become regarding the publishing of astrology apps (along with related themes such as tarot, moon phases, etc.). From what I saw, most of those discussions took place 2 - 3 years ago. I haven't seen many posts recently (just a few), but heard some people talking about a similar matter those days. Looks like Apple is again becoming restrictive on astrology apps: a) because there are already too many of them b) because they can be deemed as misleading for users c) because they all look similar & don't offer enough innovation. Some even implied that >80% apps were rejected those days. Do you have any information about this or heard of similar cases? How does that rejection rate compare to other categories? More specifically, I am curious about one thing: Even when trying to create an innovative astro app, developers have to at least create a baseline of features that are extremely similar from one app to another. For instance, they need to include birth chart, horoscope, etc. (without those, the app won't have any good baseline to build up innovation on top). How can this be handled without being accused of delivering a similar app? Best regards

My app, which only shows ads one day after it is first launched, keeps being rejected due to Guideline 2.1 - Information Needed (App Tracking Transparency framework related). Here is the rejection message from Apple: Guideline 2.1 - Information Needed We're looking forward to completing our review, but we need more information to continue. Your app uses the AppTrackingTransparency framework, but we are unable to locate the App Tracking Transparency permission request when reviewed on iOS 17.5.1. Next Steps Please explain where we can find the App Tracking Transparency permission request in your app. The request should appear before any data is collected that could be used to track the user. If you've implemented App Tracking Transparency but the permission request is not appearing on devices running the latest operating system, please review the available documentation and confirm App Tracking Transparency has been correctly implemented. If your app does not track users, update your app privacy information in App Store Connect to not declare tracking. You must have the Account Holder or Admin role to update app privacy information. We have provided a detailed step-by-step guide to trigger the App Tracking Transparency. We also attached videos demonstrating how to adjust the date to one day ahead in order to show the ads. Here is our reply: Dear Reviewer, *** will start displaying ads one day after the app is first launched. To see the App Tracking Transparency permission request and subsequent ads, please follow these steps: 1. Launch *** for the first time. 2. Close and completely exit the *** app. 3. Adjust the date on your device to one day ahead. 4. Re-launch ***. You will see the App Tracking Transparency permission request. For a visual guide, please refer to the attached videos: https://youtube.com/shorts/07qsYuFkPBY - Demonstrates when the user allows tracking. https://youtube.com/shorts/voQfgjAN7h0 - Demonstrates when the user does not allow tracking. If you need further explanation, please contact me at +xxxx-xxxxxxx. Thank you. P.S. I frequently receive similar inquiries with each submission of my app. Could you please add a note to my app to prevent this recurring issue in future reviews? Thank you for your attention. However, Apple continues to reject our update, despite our clear instructions for showing App Tracking Transparency. Do you have any suggestions on what we can do next? Thank you.

I have a simple little Mac app that embeds a Python interpreter. I wrote this app almost ten years ago and completely forgot about it. Anyway I submitted an update to it with a new version of Python but it's being rejected by App review for the following reason: Your app uses or references the following non-public or deprecated APIs: Symbols: • _Tcl_NewByteArrayObj • _Tcl_ResetResult • _Tcl_MutexLock • _Tcl_GetBooleanFromObj • _Tcl_SetObjResult • _Tcl_CreateInterp • _Tcl_ThreadQueueEvent • _Tcl_UnsetVar2 • _Tcl_GetBignumFromObj • _TclBN_mp_to_unsigned_bin_n • _Tcl_ListObjLength • _Tcl_ConditionWait • _Tcl_GetDouble • _Tcl_GetDouble • _Tcl_DeleteFileHandler • _Tcl_SetVar • _Tcl_SetVar • _Tcl_SetVar • _Tcl_DoOneEvent • _TclFreeObj • _Tcl_Eval • _Tcl_Eval • _Tcl_Eval • _Tcl_FindExecutable • _Tcl_NewLongObj • _Tcl_CreateTimerHandler • _Tcl_Init • _Tcl_ConditionFinalize • _Tcl_GetByteArrayFromObj • _Tcl_ListObjIndex • _Tcl_ExprLong • _Tcl_NewDoubleObj • _Tcl_GetDoubleFromObj • _Tcl_ExprString • _TclBN_mp_read_radix • _Tcl_DeleteTimerHandler • _Tcl_CreateFileHandler • _Tcl_GetVar • _Tcl_GetVar • _Tcl_CreateObjCommand • _Tcl_SetVar2Ex • _Tcl_GetStringFromObj • _Tcl_NewStringObj • _Tcl_GetObjType • _Tcl_MutexUnlock • _Tcl_DeleteCommand • _TclBN_mp_init • _Tcl_GetCurrentThread • _Tcl_ExprDouble • _Tcl_AddErrorInfo • _Tcl_Free • _Tcl_GetStringResult • _Tcl_SetVar2 • _Tcl_SetVar2 • _Tcl_GetBoolean • _Tcl_GetBoolean • _Tcl_RecordAndEval • _Tcl_EvalFile • _Tcl_GetLongFromObj • _TclBN_mp_clear • _Tcl_ThreadAlert • _Tcl_ExprBoolean • _Tcl_DeleteInterp • _TclBN_mp_unsigned_bin_size • _Tcl_AttemptAlloc • _Tcl_GetObjResult • _Tcl_GetWideIntFromObj • _Tcl_NewListObj • _Tcl_ConditionNotify • _Tcl_NewBooleanObj • _Tcl_SplitList • _Tcl_EvalObjv • _Tcl_GetThreadData • _Tcl_GetVar2Ex • _Tcl_NewWideIntObj • _Tcl_NewBignumObj • _Tcl_ListObjGetElements • _Tcl_GetString • _Tcl_GetString • _Tcl_GetString The use of non-public or deprecated APIs is not permitted on the App Store, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms. I read online that this is a sort of a widespread issue right now with apps that embed Python (would share links but then my post will have to be approved by a moderator). Anyone have a workaround?

I created an App. This app has been approved and is in distribution. Recently, I decided to change the name of the app which required me to create a whole new distribution, SKU, bundle ID, etc. I copied all the assets codebase of this already approved app to a new bundle and I am hitting a brick wall on approval. My app is continuing to be rejected for violating Section 4.8 (Login Services) for having a button on the log-in page that fetches the users Gmail address from the device and uses my own API for authentication and logging in. We have gone back and forth 10+ times with me explaining how this is not in violation per Section 4.8 language here: "Another login service is not required if: Your app exclusively uses your company’s own account setup and sign-in systems." Each time I submit the app for review the "reviewer" continues to just copy and paste the same template language with a couple of screenshots showing me my own app. Despite my efforts to prove and illustrate how this continues to be in check with Apple's guidelines, I must add that this is an exact copy and paste from another app that I have. I'm honestly trying to change the name, SKU, and Bundle ID of an existing app that is already approved (with the same login, etc.). This has become moderately frustrating and unhelpful leading to a poor experience. Can someone with Apple give me more information than continuing to regurgitate the same template language.

Dear Reviewer, I am writing to express my concern regarding the extended review time for my app. (App ID: 6503052240)This product has been under review for a week and there has been no response. In order to smoothly carry out the subsequent promotion plan, we hope that this product can be launched as soon as possible. I understand that there can be varying factors affecting review times, but I would greatly appreciate any information or updates you could provide regarding the status of my app's review. Thank you for your attention to this matter. I look forward to your prompt response.

Dear App Review： We are an image processing software that undergoes regular iterations and updates with new features every month. At present, our updated version has been waiting for almost 2 weeks in the "waiting for review" state. During this waiting process, we have made the following actions but are unable to enter the review process: We requested an expedited review and informed that it was successful, but no progress was made; Contacted "App Review Status" via email; Please inform us that everything is normal and wait for the review; Refused by oneself, resubmit for review; Our users have been anxiously asking us when to update the new features, and they are very eager to use them. Apple ID of the App:1401783711 and 911261462 Looking forward to your reply, thank you!

Dear Apple Review Team, I hope this message finds you well. I am writing to express my concern regarding the extended review time for my app. The review process for this submission has now exceeded three months, which is significantly longer than what I have experienced in the past. Given the usual efficiency of the review process, this extended delay is unexpected and has started to impact our release schedule and user experience. I understand that there can be varying factors affecting review times, but I would greatly appreciate any information or updates you could provide regarding the status of my app's review. Thank you for your attention to this matter. I look forward to your prompt response. App ID: 6479209268

I currently have an iPhone 7 that I use to test and send my apps to the store, but I know that I won't be able to continue with iOS 15 for a long time due to the updates required by Apple, I'm on xcode 15.1 and sonoma 14.2. My question is, can I get a good lifespan with an iPhone 12? Another question, is it really mandatory for me to have a physical device to launch applications in the store?

Hi, we were able to migrate our solution from Xamarin to MAUI (.net 8). After a 2 weeks fight, the app is finally working on my dev devices. Unfortunately, after sending the app to review, it gets rejected because of the following: ITMS-90338: Non-public API usage - The app references non-public symbols in [Our app name]: _SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ From what I understand, this is because the 4 methods (_SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys) exists in the generated Mach-O binary. Those methods are not used directly by our application but because of HttpClient we are using to request our business API The methods are implemented in the System.Net.NetworkInformation assembly which is referenced in the System.Net.Http assembly Given to the MAUI Team those methods are public and should not be rejected (https://github.com/dotnet/maui/issues/23210#issuecomment-2186038540) Kind regards

I didn’t see any mention on whether there’s an upper limit on the number of subscription groups an app can offer. Is there an upper limit? To be compliant with 3.1.1 and 3.1.3(b), I would need tens of thousands of subscriptions groups.

Hi, My app has been rejected twice for the reason mentioned in subject. Has anybody faced a similar issue ? My app does actually reward users for doing digital tasks like surveys and watching ads.

Hello, Apple community and support team. We would like to get your input on a recent rejection we got in our latest app submission. The app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1. Specifically, your app utilizes the NEVPNManager APIs for non-approved uses. Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed. We are currently uncertain about the specific ways in which the NEVPNManager APIs are being misused in our app, as we have diligently followed the instructions documented on Apple’s website. Our app uses a Packet Tunnel Provider and configures it to use a local proxy server for reducing network traffic, especially for video streaming services. We initially don't send any of the received traffic to a VPN server and instead, traffic is only handled by the Proxy Server. We are committed to ensuring our app complies with all guidelines and appreciate your assistance in resolving this matter. Your guidance will be invaluable in helping us make the necessary adjustments. Thank you for your support.

Dear App Review: We are an e-commerce shopping software, and we regularly update new features every month. We have been waiting for nearly 10 days for the new update version released on June 19th. Now the review status remains in the review status. According to the experience of the past two years, the review of the updated version usually takes about 2-3 days. We are confused about the extension of this review time and are worried about whether there is any problem with our App, causing the current situation. Our users have been anxiously asking us when to update new features, and they are very eager to use them. Apple ID of the App: 905869418 Looking forward to your reply, thank you!

Hello there! Two weeks ago our app store submission was rejected, citing 2.3.3 (inaccurate metadata) - specifically, screenshots that were out-of-date. We happily replaced the screenshots with ones of the current version and resubmitted, but were once again rejected on the same grounds. After quite a few attempts at fixing the issue and our noticing with every rejection that the reviewers' explanations always reference the original now-replaced screenshots, we are starting to wonder if there isn't a bug somewhere that is preventing them from seeing the ones we've uploaded since. Since we haven't heard back from Apple Support or the appeals team, we thought we'd ask here: Has anyone experienced something like this before? Does anyone possibly have any advice on what to do in this situation? Thanks in advance for your help!