Search results for

“missing package product”

52,430 results found

Post

Replies

Boosts

Views

Activity

Reply to Sharing all container content
I want to share all the content of a CloudKit database at once between different iCloud accounts. For example, to manage products storage between users. Once the database has been shared or an invitation has been accepted, any additions/modifications/deletions to storage or products must be shared between all users without additional sharing. To be short after the first sharing, everything must be shared without additional new sharing. I think I can't do this in SwiftData (would be the best solution for me as all the current app is based on SwiftDaa) and that I need to use move to CoreData. Is that correct? Or does a mixed solution may be possible (ie .storage with SWiftData and sharing with CoreData)? It seems that “Zone Wide Sharing” could be the solution? But I can't find a sufficiently comprehensive example and I wasn't able to make something working. Ultimately, I realize that this is not a very common use case. With the ZoneWide Sharing does it means that we must do a affectedStores or
Mar ’26
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in
2
0
142
4w
stuck in “Waiting for Review” since February 7
Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 7, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I kindly ask for a specific and personalized response regarding my case, as my previous inquiries received only general or automated replies without addressing the actual issue. Apple ID: 6758804549 Thank you.
5
0
285
Mar ’26
App stuck in “Waiting for Review” for 3+ weeks (Case ID: 20000107493507)
Hi everyone, My iOS app “TaskCal: Task Manager” (version 1.2.8) has been stuck in “Waiting for Review” for more than 3 weeks, and I’m not sure what else I can do at this point. Here are the key dates (GMT+8): Jan 30, 2026 – Version 1.2.3 was approved and marked “Ready for Distribution”. Jan 31 – Feb 8, 2026 – I submitted version 1.2.8 multiple times. Several submissions were later marked as “Removed” in App Store Connect. Feb 9, 2026, 12:39 AM – I submitted version 1.2.8 again. This submission has been in “Waiting for Review” ever since. Today is Mar 3, 2026 (Taipei time) – The status is still “Waiting for Review” with no change. Because of this, I contacted Apple Developer Support multiple times through Contact Support. I only received one reply, on Feb 21, 2026, which said: Hello Alan, Thank you for reaching out to Developer Support about your app, “TaskCal: Task Manager.” I understand that you’re concerned. After reviewing your app’s submission history, I can confirm that your apps is still in the “Waiting
2
0
222
Mar ’26
On M4 macmini, Xcode 26 cannot debug iOS 12 on iPhone 6
As stated in the title, my device is M4 macmini, running macOS 26, with Xcode version 26.1. The error message is : retrying debugserver without secure proxy due to error: Error Domain=com.apple.dtdevicekit Code=811 UserInfo={NSUnderlyingError=0xc42b07930 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653150 UserInfo={MobileDeviceErrorCode=, com.apple.dtdevicekit.stacktrace=, DVTRadarComponentKey=261622, NSLocalizedDescription=}}, NSLocalizedRecoverySuggestion=Please check your connection to your device., DVTRadarComponentKey=261622, NSLocalizedDescription=}, the official documentation does state that debugging is supported for devices running at least iOS 15. However, my 2019 MacBook Pro, with macOS 15.7.2 and Xcode 26.1 installed, can debug iOS 12 devices normally. The product manager has asked me to identify the issue, but I am at a loss. If anyone can provide a solution or confirm that support for iOS 12 is no longer available, we would be very grateful. Additionally, iOS 13
2
0
128
Mar ’26
Reply to Frequent providerDidReset Callbacks in Production
We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). How frequent is frequent? The documentation states that providerDidReset signals the provider has been reset and all calls should be considered terminated. Should we be calling CXProvider.invalidate() on the old instance before creating a new one? Or is assigning a new CXProvider to cxProvider (which releases the old instance) sufficient? My recommendation would be that you destroy all existing call infrastructure (both CXProvider and all other CallKit crashes), call invalidate as well, then recreate a new CXProvider and recreate all other call infrastructure. Having said that, the EXACT details of that process generally don't matter all that much. All existing CallKit objects will be non-functional; most VoIP apps don't persist long enough that issues like small amounts of leaked memory actually become relevant. What could be causing providerDidReset to fire so frequently, and how
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’26
Frequent providerDidReset Callbacks in Production
Hello, We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). I'd like to understand both the correct way to handle this delegate method and strategies to reduce its frequency. Background The callback occurs across all iOS versions we support and is not isolated to a specific device or region. The callback can occur in any app state (foreground, background, inactive), however it is most dominant in the background state — particularly during VoIP push notification handling. The callback is more prevalent during long app sessions — for example, when the app has been running continuously for a day or overnight. We do not call CXProvider.invalidate() anywhere in our codebase explicitly. After providerDidReset fires, subsequent transactions fail with CXErrorCodeRequestTransactionErrorUnknownCallUUID (error code 4). Re-initializing the provider via initializeProvider() resolves this error. Our Implementation We use a singleton proxy class (Ca
1
0
147
Mar ’26
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
Hello again, Kevin, and thank you again for your help. I notice that you commented 18 hrs ago, but I could have sworn I checked yesterday and there wasn't anything here. I ended up getting matching working by also specifying version number, which increased my probe score. And... you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. you definitely predicted my next issue. I prefer date-based build and version numbers, and this one was problematic, but your link helped me fit a date based number into that parsing code. If anyone else wants to try that, I used BUILD_NUMBER=$(date '+%Y.%m%d.%H%Mf%S') in my update script, which yields a version number e.g. 2026.0303.1749f09. The arbitrary f enables me to get past that 4[letter]3 format. I picked f only because it looks similar to an s. Before I move onto my current problem... Can you do that, perhaps by operating at the device instead of interface level? Could you explain what you mean
Topic: App & System Services SubTopic: Drivers Tags:
Mar ’26
Question about Unlisted App direct link behavior
Hello, I am planning to distribute my iOS app as an Unlisted App. I would like to confirm the following: If users access the standard App Store URL in the format below: https://apps.apple.com/app/idXXXXXXXXXX Will users be able to reach the Unlisted app’s App Store product page via this URL? Or is the specific Unlisted distribution link generated by App Store Connect required for access? My goal is to ensure that in-app update guidance directs users to the correct App Store page. Thank you for your support.
3
0
124
Mar ’26
Reply to Is calling different SBApplication objects from different threads bad?
Hooboy, knowing if we've seen it on Intel machines will take some digging. The M1 Studios we have are 2022. Our ScriptingBridge code was added in June 2023. The first internal mention of errOSAInternalTableOverflow is December 2023. The M1 Studios weren't put into production until March 2024 (that's how slow our IT department moves). By this timeline, it appears we were seeing errOSAInternalTableOverflow on Intel. As for the actual crash described in this thread and bug, that I'm not sure about. I'm assuming that getting errOSAInternalTableOverflow and this crash are caused by the same underlying bug. No PowerPC Macs have been in use during my tenure at this job. Naturally, I figured it would be a very long time until a possible Apple fix would reach our production machines. Time to diagnose + time to fix & test + time to release + time for our IT department to OK the user of that version of macOS. I just might be retired by then. Moving the bulk of the job code to a separate helper app
Mar ’26
Reply to FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
Thanks again for the reply, and especially for such a thorough and helpful one! For example, I suspect this doesn't happen if you start with a security-scoped bookmark, which you resolve to a bookmark before each save. Out of curiosity I just tested this, and I still see the bug. To see it yourself, just use the code from my first post but change the savingURL accessor to use a security-scoped bookmark, as follows: private var bookmarkData: Data? // Ask user to choose this via a save panel. var savingURL: URL? { get { var isStale = false if let bookmarkData, let url = try? URL(resolvingBookmarkData: bookmarkData, options: .withSecurityScope, relativeTo: nil, bookmarkDataIsStale: &isStale) { if isStale { // Should really update the bookmark data here... } return url } else { return nil } } set(newURL) { bookmarkData = try? newURL?.bookmarkData(options: .withSecurityScope) setUpSpamSave() } } Then add the following to the top of spamSave() after checking savingURL is non-nil: let didAccess = savingURL.start
Topic: App & System Services SubTopic: Core OS Tags:
Mar ’26
First Auto-Renewable Subscription – getSubscriptions returns empty in TestFlight
Hi, I am submitting auto-renewable subscriptions for the first time for a brand new iOS app (never approved before). Setup: App ID has In-App Purchase capability enabled Subscriptions created under a subscription group All metadata (pricing, localization, availability) completed Subscriptions currently show In Review Testing via TestFlight build Bundle ID matches App Store Connect Using react-native-iap (StoreKit under the hood) When calling: await getSubscriptions({ skus }) I consistently get: products fetched: 0 ProductsUnavailableError Also, the app version page does not show the “In-App Purchases and Subscriptions” section. Question: For a brand new app, will StoreKit return empty products while the first subscriptions are in review? Do the first subscriptions need to be approved and/or attached to a new app version before they become available in TestFlight sandbox? Thanks for any clarification.
1
0
92
Mar ’26
App review stuck in “Waiting for Review” for over 3 weeks (TaskCal: Task Manager)
Hi everyone, I’m an iOS indie developer based in Taipei, and I’m running into a strange App Review delay that I haven’t been able to resolve through the usual channels. My app “TaskCal: Task Manager” (iOS), version 1.2.8, has been in the “Waiting for Review” status since February 9, 2026 in App Store Connect. It’s now been more than 3 weeks with no movement at all — no change to “In Review”, no rejection, no message from App Review. Here are some details: Platform: iOS App name: TaskCal: Task Manager Version: 1.2.8 Status: Waiting for Review Submitted: 2026-02-09 (Asia/Taipei time) Region: App Store Connect account registered in Taiwan I’ve already tried the following: Used App Store Connect → Contact Us → App Review to submit a support request. Got one reply from Developer Support saying they “understand my concern” and that they would “reach out to the appropriate team.” After that, there’s been no further update — the status is still stuck on “Waiting for Review,” and I haven’t received any additional emai
1
0
205
Mar ’26
App stuck in review after resubmitting with requested changes
Hi developer community, First time iOS developer here. I originally submitted my iOS app for review on Friday February 20th and was asked to make a small change on Monday February 23rd, which I did promptly and resubmitted with a new build that evening. It's been a week since I resubmitted and wondering if I may have done something incorrectly when reattaching a new build to the review submission. I requested an expedited review on Friday February 27th and contacted support this morning but haven't seen any movement on the waiting in review status yet. My app is highly dependent on seasonality (winter sports) and I missed a key opportunity at an event last week to promote the app while the app has been stuck in review. Any guidance or assistance would be super welcome so I can get my app out into the world before we get into the Spring season! App ID: 6759411804 Thanks
1
0
143
Mar ’26
Reply to Sharing all container content
I want to share all the content of a CloudKit database at once between different iCloud accounts. For example, to manage products storage between users. Once the database has been shared or an invitation has been accepted, any additions/modifications/deletions to storage or products must be shared between all users without additional sharing. To be short after the first sharing, everything must be shared without additional new sharing. I think I can't do this in SwiftData (would be the best solution for me as all the current app is based on SwiftDaa) and that I need to use move to CoreData. Is that correct? Or does a mixed solution may be possible (ie .storage with SWiftData and sharing with CoreData)? It seems that “Zone Wide Sharing” could be the solution? But I can't find a sufficiently comprehensive example and I wasn't able to make something working. Ultimately, I realize that this is not a very common use case. With the ZoneWide Sharing does it means that we must do a affectedStores or
Replies
Boosts
Views
Activity
Mar ’26
App Stuck in “Waiting for Review” for Over 2 Weeks (Since Feb 20)
Hello everyone, I am an iOS developer based in South Korea, and I’m currently experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. My app has been stuck in “Waiting for Review” for more than two weeks, and there has been no progress at all during this time. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. App Information Platform: iOS App Name: WOOTA Apple ID: 6759412826 Status: Waiting for Review Submission Date: February 20, 2026 Developer Account Region: South Korea What I Have Already Tried: I have already attempted the following steps: Submitted an inquiry via App Store Connect → Contact Us → App Review Received a response from Developer Support saying they understand my concern and that they contacted the review team However, since then there have been no updates at all. The app status remains “Waiting for Review”, and there are no messages in
Replies
2
Boosts
0
Views
142
Activity
4w
stuck in “Waiting for Review” since February 7
Hello Apple Developer Support, My app has been stuck in “Waiting for Review” since February 7, and I have submitted multiple inquiries without receiving any response. This delay has now become extremely concerning. Missing a planned launch due to an indefinite review timeline is very difficult for independent developers. If there is an issue with the submission, I would appreciate clear communication. If there are review delays, transparency would help us plan accordingly. I respect the review process, but the lack of updates after this amount of time is frustrating. I would sincerely appreciate clarification on the status. I kindly ask for a specific and personalized response regarding my case, as my previous inquiries received only general or automated replies without addressing the actual issue. Apple ID: 6758804549 Thank you.
Replies
5
Boosts
0
Views
285
Activity
Mar ’26
App stuck in “Waiting for Review” for 3+ weeks (Case ID: 20000107493507)
Hi everyone, My iOS app “TaskCal: Task Manager” (version 1.2.8) has been stuck in “Waiting for Review” for more than 3 weeks, and I’m not sure what else I can do at this point. Here are the key dates (GMT+8): Jan 30, 2026 – Version 1.2.3 was approved and marked “Ready for Distribution”. Jan 31 – Feb 8, 2026 – I submitted version 1.2.8 multiple times. Several submissions were later marked as “Removed” in App Store Connect. Feb 9, 2026, 12:39 AM – I submitted version 1.2.8 again. This submission has been in “Waiting for Review” ever since. Today is Mar 3, 2026 (Taipei time) – The status is still “Waiting for Review” with no change. Because of this, I contacted Apple Developer Support multiple times through Contact Support. I only received one reply, on Feb 21, 2026, which said: Hello Alan, Thank you for reaching out to Developer Support about your app, “TaskCal: Task Manager.” I understand that you’re concerned. After reviewing your app’s submission history, I can confirm that your apps is still in the “Waiting
Replies
2
Boosts
0
Views
222
Activity
Mar ’26
On M4 macmini, Xcode 26 cannot debug iOS 12 on iPhone 6
As stated in the title, my device is M4 macmini, running macOS 26, with Xcode version 26.1. The error message is : retrying debugserver without secure proxy due to error: Error Domain=com.apple.dtdevicekit Code=811 UserInfo={NSUnderlyingError=0xc42b07930 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653150 UserInfo={MobileDeviceErrorCode=, com.apple.dtdevicekit.stacktrace=, DVTRadarComponentKey=261622, NSLocalizedDescription=}}, NSLocalizedRecoverySuggestion=Please check your connection to your device., DVTRadarComponentKey=261622, NSLocalizedDescription=}, the official documentation does state that debugging is supported for devices running at least iOS 15. However, my 2019 MacBook Pro, with macOS 15.7.2 and Xcode 26.1 installed, can debug iOS 12 devices normally. The product manager has asked me to identify the issue, but I am at a loss. If anyone can provide a solution or confirm that support for iOS 12 is no longer available, we would be very grateful. Additionally, iOS 13
Replies
2
Boosts
0
Views
128
Activity
Mar ’26
Reply to Frequent providerDidReset Callbacks in Production
We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). How frequent is frequent? The documentation states that providerDidReset signals the provider has been reset and all calls should be considered terminated. Should we be calling CXProvider.invalidate() on the old instance before creating a new one? Or is assigning a new CXProvider to cxProvider (which releases the old instance) sufficient? My recommendation would be that you destroy all existing call infrastructure (both CXProvider and all other CallKit crashes), call invalidate as well, then recreate a new CXProvider and recreate all other call infrastructure. Having said that, the EXACT details of that process generally don't matter all that much. All existing CallKit objects will be non-functional; most VoIP apps don't persist long enough that issues like small amounts of leaked memory actually become relevant. What could be causing providerDidReset to fire so frequently, and how
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’26
Frequent providerDidReset Callbacks in Production
Hello, We're seeing a high rate of providerDidReset callbacks in production across a large user base (iOS 16, 17, 18, and 26). I'd like to understand both the correct way to handle this delegate method and strategies to reduce its frequency. Background The callback occurs across all iOS versions we support and is not isolated to a specific device or region. The callback can occur in any app state (foreground, background, inactive), however it is most dominant in the background state — particularly during VoIP push notification handling. The callback is more prevalent during long app sessions — for example, when the app has been running continuously for a day or overnight. We do not call CXProvider.invalidate() anywhere in our codebase explicitly. After providerDidReset fires, subsequent transactions fail with CXErrorCodeRequestTransactionErrorUnknownCallUUID (error code 4). Re-initializing the provider via initializeProvider() resolves this error. Our Implementation We use a singleton proxy class (Ca
Replies
1
Boosts
0
Views
147
Activity
Mar ’26
Reply to Driver Activation failure error code 9. Maybe Entitlements? Please help
Hello again, Kevin, and thank you again for your help. I notice that you commented 18 hrs ago, but I could have sworn I checked yesterday and there wasn't anything here. I ended up getting matching working by also specifying version number, which increased my probe score. And... you should also be aware of the version number limitation described here, which is another arbitrary restriction the kernel enforces. you definitely predicted my next issue. I prefer date-based build and version numbers, and this one was problematic, but your link helped me fit a date based number into that parsing code. If anyone else wants to try that, I used BUILD_NUMBER=$(date '+%Y.%m%d.%H%Mf%S') in my update script, which yields a version number e.g. 2026.0303.1749f09. The arbitrary f enables me to get past that 4[letter]3 format. I picked f only because it looks similar to an s. Before I move onto my current problem... Can you do that, perhaps by operating at the device instead of interface level? Could you explain what you mean
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Mar ’26
Question about Unlisted App direct link behavior
Hello, I am planning to distribute my iOS app as an Unlisted App. I would like to confirm the following: If users access the standard App Store URL in the format below: https://apps.apple.com/app/idXXXXXXXXXX Will users be able to reach the Unlisted app’s App Store product page via this URL? Or is the specific Unlisted distribution link generated by App Store Connect required for access? My goal is to ensure that in-app update guidance directs users to the correct App Store page. Thank you for your support.
Replies
3
Boosts
0
Views
124
Activity
Mar ’26
Reply to Is calling different SBApplication objects from different threads bad?
Hooboy, knowing if we've seen it on Intel machines will take some digging. The M1 Studios we have are 2022. Our ScriptingBridge code was added in June 2023. The first internal mention of errOSAInternalTableOverflow is December 2023. The M1 Studios weren't put into production until March 2024 (that's how slow our IT department moves). By this timeline, it appears we were seeing errOSAInternalTableOverflow on Intel. As for the actual crash described in this thread and bug, that I'm not sure about. I'm assuming that getting errOSAInternalTableOverflow and this crash are caused by the same underlying bug. No PowerPC Macs have been in use during my tenure at this job. Naturally, I figured it would be a very long time until a possible Apple fix would reach our production machines. Time to diagnose + time to fix & test + time to release + time for our IT department to OK the user of that version of macOS. I just might be retired by then. Moving the bulk of the job code to a separate helper app
Replies
Boosts
Views
Activity
Mar ’26
Reply to FileManager.replaceItemAt(_:withItemAt:) fails sporadically on ubiquitous items
Thanks again for the reply, and especially for such a thorough and helpful one! For example, I suspect this doesn't happen if you start with a security-scoped bookmark, which you resolve to a bookmark before each save. Out of curiosity I just tested this, and I still see the bug. To see it yourself, just use the code from my first post but change the savingURL accessor to use a security-scoped bookmark, as follows: private var bookmarkData: Data? // Ask user to choose this via a save panel. var savingURL: URL? { get { var isStale = false if let bookmarkData, let url = try? URL(resolvingBookmarkData: bookmarkData, options: .withSecurityScope, relativeTo: nil, bookmarkDataIsStale: &isStale) { if isStale { // Should really update the bookmark data here... } return url } else { return nil } } set(newURL) { bookmarkData = try? newURL?.bookmarkData(options: .withSecurityScope) setUpSpamSave() } } Then add the following to the top of spamSave() after checking savingURL is non-nil: let didAccess = savingURL.start
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Mar ’26
First Auto-Renewable Subscription – getSubscriptions returns empty in TestFlight
Hi, I am submitting auto-renewable subscriptions for the first time for a brand new iOS app (never approved before). Setup: App ID has In-App Purchase capability enabled Subscriptions created under a subscription group All metadata (pricing, localization, availability) completed Subscriptions currently show In Review Testing via TestFlight build Bundle ID matches App Store Connect Using react-native-iap (StoreKit under the hood) When calling: await getSubscriptions({ skus }) I consistently get: products fetched: 0 ProductsUnavailableError Also, the app version page does not show the “In-App Purchases and Subscriptions” section. Question: For a brand new app, will StoreKit return empty products while the first subscriptions are in review? Do the first subscriptions need to be approved and/or attached to a new app version before they become available in TestFlight sandbox? Thanks for any clarification.
Replies
1
Boosts
0
Views
92
Activity
Mar ’26
App review stuck in “Waiting for Review” for over 3 weeks (TaskCal: Task Manager)
Hi everyone, I’m an iOS indie developer based in Taipei, and I’m running into a strange App Review delay that I haven’t been able to resolve through the usual channels. My app “TaskCal: Task Manager” (iOS), version 1.2.8, has been in the “Waiting for Review” status since February 9, 2026 in App Store Connect. It’s now been more than 3 weeks with no movement at all — no change to “In Review”, no rejection, no message from App Review. Here are some details: Platform: iOS App name: TaskCal: Task Manager Version: 1.2.8 Status: Waiting for Review Submitted: 2026-02-09 (Asia/Taipei time) Region: App Store Connect account registered in Taiwan I’ve already tried the following: Used App Store Connect → Contact Us → App Review to submit a support request. Got one reply from Developer Support saying they “understand my concern” and that they would “reach out to the appropriate team.” After that, there’s been no further update — the status is still stuck on “Waiting for Review,” and I haven’t received any additional emai
Replies
1
Boosts
0
Views
205
Activity
Mar ’26
App stuck in review after resubmitting with requested changes
Hi developer community, First time iOS developer here. I originally submitted my iOS app for review on Friday February 20th and was asked to make a small change on Monday February 23rd, which I did promptly and resubmitted with a new build that evening. It's been a week since I resubmitted and wondering if I may have done something incorrectly when reattaching a new build to the review submission. I requested an expedited review on Friday February 27th and contacted support this morning but haven't seen any movement on the waiting in review status yet. My app is highly dependent on seasonality (winter sports) and I missed a key opportunity at an event last week to promote the app while the app has been stuck in review. Any guidance or assistance would be super welcome so I can get my app out into the world before we get into the Spring season! App ID: 6759411804 Thanks
Replies
1
Boosts
0
Views
143
Activity
Mar ’26
Reply to stuck in “Waiting for Review” since February 7
yeah, defiantly BS from @apple on this. My clients are waiting, opportunities are being missed. I understand things happen, but be transparent and let us plan accordingly. i submitted apps in the begining of feb and they were approved in a day or two. I submittted one for a new client on feb 12th and its still waiting for review
Replies
Boosts
Views
Activity
Mar ’26