Search results for

“missing package product”

52,405 results found

Post

Replies

Boosts

Views

Activity

Reply to Notarization services is not returning notarization status
Hi @DTS Engineer, I have put the verbose output log from xcrun command to give some information on what is happening. I have put the log on quote option provided in the reply. Looks like all our notarization request for different packages has been put for in-depth analysis. This makes our deliverables or commitments to customers in trouble. Not sure why Apple is giving such surprises in production systems without giving intimation to users who use those systems. Our request which is In progress status has passed 48 hours (its used to finish in 10 minutes). Waiting for few more days is going to affect our business. Is there anything we can do from our side to expedite the process? regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
2w
Rejected for Guideline 4.1(c) Copycats - Accused of copying my own brand
Hello everyone, I am seeking some guidance on how to break out of what appears to be an automated App Review rejection loop. My app has been rejected three times in a row for the exact same reason, and my replies in the Resolution Center seem to be getting ignored. The Issue: My app is named Linkwise (associated with my web platform, linkwise.app). I am being rejected under Guideline 4.1(c) - Design - Copycats. The rejection message specifically states: The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Linkwise. The bizarre part is that I am the developer of Linkwise. I am being accused of impersonating my own brand and product. Submission Details: App Name: Linkwise Submission ID: fa557f1b-3724-4e01-aa85-bf05ced4801f Version: 1.0.1 Review Device: iPhone 17 Pro Max What I've Tried: I have replied to the rejection message in App Store Connect three times explaining that I am the owner of the Linkwise brand and domain. Despite this, I keep
2
0
94
2w
App multiple times rejected - 4.3.0 Design: Spam
Hello everyone, I’m looking for some advice or shared experiences regarding an app rejection under App Store Review Guideline 4.3(b) – Design – Spam. Our app was rejected and, after an appeal to the App Review Board, Apple maintained that the app “duplicates the content and functionality of similar apps in a saturated category.” We strongly disagree with this classification and are struggling to understand how Guideline 4.3(b) has been applied in our case. The app was developed as an original product: Custom-designed content (including original cards and interactions) A unique visual style and UI A distinct interaction flow focused on encouraging social interaction between users This was not a template-based or reskinned app, nor is it part of a series of similar submissions. We fully respect the App Store Review Guidelines and are open to making adjustments to better align with them. However, what we find difficult is the lack of specific, actionable feedback. We have not received clear guidance on
Topic: Design SubTopic: General Tags:
3
0
1.6k
2w
App group broken on Sequoia
We've got an in-house Swift macOS desktop app with a FileProvider extension, which has been working fine on various machines up through Sonoma (and still does). We've just installed it on a Sequoia machine, and on it the FileProvider extension has lost the ability to access the shared app group. It can neither log to the Group Containers folder under ~/Library, nor access the pipe to the main app. The group name is formatted as group.XXXXXXXXXX.com.orgname.appname in both targets. I'm not sure why it combines the iOS and macOS conventions, with both the group prefix and the teamIdentifier one -- it was first built some time before the point in 2025 when macOS supported iOS-style groups -- but again, it's been working. For the record, The provisioning profile for EMPFileProvider has the App Groups capability enabled, and the App Groups capability is present in both build targets in Xcode. The existing group identifier is registered on the website; I've also manually registered the team-ID-less group n
8
0
308
2w
Notarization submission stays In Progress for over 45 minutes
Hello, We are experiencing repeated notarization delays for our macOS app distributed outside the Mac App Store. Current submission ID: 45d7cac0-bd8a-4d48-b886-1cad7649adf4 Previous affected submission ID: ff61de1e-15f5-4bbe-8b34-a91a6f73b978 Issue description: xcrun notarytool submit succeeds and returns a submission ID. xcrun notarytool info keeps returning In Progress for a very long time. In the current case, the submission has remained In Progress for more than 45 minutes. This issue has happened repeatedly across multiple submissions. What we have already checked: We are not using a local proxy for notarization requests. We separated submit and polling in our build script to verify the exact stage. We retried multiple times. We reduced package contents to rule out newly introduced app content. Could someone from Apple please help check whether these submission IDs are stuck in the notarization pipeline, or advise what additional diagnostics we should provide? Thank you.
4
0
144
2w
Reply to Notarization submission stays In Progress for over 45 minutes
lingyun1998 wrote: I have submitted it for review repeatedly for more than 30 times. Submitting the same request over and over again isn’t going to help. In my previous post I suggested you read Q&A with the Mac notary service team, which says: If your app [requires additional analysis], rest assured that we’ve received your file and will complete the analysis, though it may take longer than usual. and: In addition, if you’ve made changes to your app while a prior upload has been delayed, it’s fine to upload a new build. So, it’s fine to submit a new build if you’ve made meaningful changes to your product, but submitting the same build multiple times is pointless. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
Notarization submissions stuck in “In Progress” for >24 hours (CI / REST API) – production impact
We are experiencing notarization submissions that remain in the “In Progress” state for an extended period (over 24 hours), with no status transition and no submission log available. This is occurring in an automated CI environment using the Notary REST API (non-interactive submission and polling). Re-submitting the same package only results in additional submissions also stuck in “In Progress”. There does not appear to be any API mechanism to cancel, clear, or expire these submissions once they are created. We have already opened an Apple Developer Support case regarding this issue (Case ID: 102818066745 & 102819008943), but have not yet received clarification on what is causing these long-running “In Progress” states. This issue is impacting our production release pipeline, as we are unable to reliably complete notarization for signed packages within an expected timeframe. Based on other reports in this forum (including thread 811968), this behavior appears similar to cases wh
5
0
553
2w
Unable to enable eligibility for External Purchase Link APIs — seeking clarification
Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.st
2
0
237
2w
Significant delay in Transaction ID availability via App Store Server API (Error 4040010)
Hi everyone, I’ve been encountering a recurring issue with the App Store Server API over the past 48 hours, specifically regarding the Get Transaction Info endpoint. Endpoint: GET /inApps/v1/transactions/{transactionId} Environment: Production Error Code: 4040010 (TransactionIdNotFound) The Issue When a user completes a purchase in our app, the client-side sends the transactionId to our backend for validation. However, when our server immediately calls the Get Transaction Info API using that ID, it frequently returns a 4040010 error, stating that the transaction ID cannot be found. Key Observations Eventual Consistency Delay: If we implement a retry logic and wait for 2 to 5 minutes, the exact same transactionId eventually becomes queryable and returns a valid signedTransactionInfo. Notifications vs. API: Interestingly, our server receives the App Store Server Notifications V2 (webhook) for these transactions almost instantly. The notifications contain the correct data, but the Pull API seems to lag
1
0
89
2w
AppIntent search schema opens app as only option
I am trying to use @AppIntent(schema: .system.search) to search in my app via a Siri voice command, but I want to be able to return a .result that does not open the app, yet still get the model training benefits from the schema. Very new to this, this is my first app, so I would appreciate some guidance. I haven't gotten to the voice part, I tested on Shortcuts. Do I need to do AppIntents without the schema and wait until there is a search schema that does not open the app, or should I be using a different schema? What am I missing?
2
0
578
2w
Reply to question about migrating `Sign in with Apple`
Hi @Dick_Long, Thanks for your questions. You wrote: A. From the document above, can I performed the Steps 1&2 before the app transfer? if so, is there a maximum lead time for these transfer_subs? To migrate their users, the transferring team (Team A) must obtain their user access token(s) and generate a transfer identifier(s) prior to initiating the app transfer. If the app belongs to an app group, Team A must also ungroup them before initiating the transfer. If the app is configured with a Services ID, it will also transfer. If Team A wants to keep the Services ID, they must remove the association with the app before initiating the transfer. Important: If a user doesn’t use any other applications from Team A, Team A will no longer be able to communicate with the migrated user using their private email address after the transfer. Next, you wrote: B. Regarding Step 5(Team B exchanging transfer identifiers via https://appleid.apple.com/auth/usermigrationinfo) are there specific rate limits (requests per se
2w
Reply to Is calling different SBApplication objects from different threads bad?
I've made a change to our app. We have a faceless helper app that we used to use for running all our scripts. It uses XPC for communication between it and the main app. It was developed many years ago when we needed to stop blocking the main thread when multiple jobs were running scripts. I updated it a few days ago to use ScriptingBridge (like we'd previously done to the main app). This has been used in production now for a couple of days. We no longer experience crashes caused by the low-level AE system (AECreateEmptyEvent, etc.). That's the good news—the AE errors for one job no longer take out the app and any other jobs. Fabulous! I do still get problems that appear to be empty replies from telling the InDesignApplication (an SBApplication subclass) to doScript:ourScript. This mostly happens when running multiple jobs at once and when I switch our main app in and out of the foreground. I assume doing that jiggles a lot of Jell-O. I don't know what would cause that; the AE system, SB, or InDesign.
2w
Reply to Update for existing app (6759172913) waiting for review – verifying submission
Small update regarding our submission: The build is still currently in “Waiting for Review”, so I just wanted to kindly check whether everything looks correct on our side in App Store Connect. Since the previous version of the app was already approved and is currently live on the App Store, we wanted to make sure that this update — which mainly includes a few UI improvements and small usability adjustments — does not have any missing metadata or configuration that could delay the review process. If anyone from the App Review team happens to see this and can confirm that the submission looks complete from your side, we would really appreciate it. Thank you very much for your time and for the work you do supporting developers. Kind regards, José Rodríguez
2w
Reply to App stuck in “Waiting for Review” for over a month – multiple contacts with Apple but no progress
Same here, we already lost a lot of money because of these delays. Why they don't have AI doing this reviews? like google.
Replies
Boosts
Views
Activity
2w
Reply to Notarization services is not returning notarization status
Hi @DTS Engineer, I have put the verbose output log from xcrun command to give some information on what is happening. I have put the log on quote option provided in the reply. Looks like all our notarization request for different packages has been put for in-depth analysis. This makes our deliverables or commitments to customers in trouble. Not sure why Apple is giving such surprises in production systems without giving intimation to users who use those systems. Our request which is In progress status has passed 48 hours (its used to finish in 10 minutes). Waiting for few more days is going to affect our business. Is there anything we can do from our side to expedite the process? regards Prema Kumar
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
2w
Rejected for Guideline 4.1(c) Copycats - Accused of copying my own brand
Hello everyone, I am seeking some guidance on how to break out of what appears to be an automated App Review rejection loop. My app has been rejected three times in a row for the exact same reason, and my replies in the Resolution Center seem to be getting ignored. The Issue: My app is named Linkwise (associated with my web platform, linkwise.app). I am being rejected under Guideline 4.1(c) - Design - Copycats. The rejection message specifically states: The app's icon and name contain an icon, brand, or product name that belongs to the following developer: Linkwise. The bizarre part is that I am the developer of Linkwise. I am being accused of impersonating my own brand and product. Submission Details: App Name: Linkwise Submission ID: fa557f1b-3724-4e01-aa85-bf05ced4801f Version: 1.0.1 Review Device: iPhone 17 Pro Max What I've Tried: I have replied to the rejection message in App Store Connect three times explaining that I am the owner of the Linkwise brand and domain. Despite this, I keep
Replies
2
Boosts
0
Views
94
Activity
2w
App multiple times rejected - 4.3.0 Design: Spam
Hello everyone, I’m looking for some advice or shared experiences regarding an app rejection under App Store Review Guideline 4.3(b) – Design – Spam. Our app was rejected and, after an appeal to the App Review Board, Apple maintained that the app “duplicates the content and functionality of similar apps in a saturated category.” We strongly disagree with this classification and are struggling to understand how Guideline 4.3(b) has been applied in our case. The app was developed as an original product: Custom-designed content (including original cards and interactions) A unique visual style and UI A distinct interaction flow focused on encouraging social interaction between users This was not a template-based or reskinned app, nor is it part of a series of similar submissions. We fully respect the App Store Review Guidelines and are open to making adjustments to better align with them. However, what we find difficult is the lack of specific, actionable feedback. We have not received clear guidance on
Topic: Design SubTopic: General Tags:
Replies
3
Boosts
0
Views
1.6k
Activity
2w
App group broken on Sequoia
We've got an in-house Swift macOS desktop app with a FileProvider extension, which has been working fine on various machines up through Sonoma (and still does). We've just installed it on a Sequoia machine, and on it the FileProvider extension has lost the ability to access the shared app group. It can neither log to the Group Containers folder under ~/Library, nor access the pipe to the main app. The group name is formatted as group.XXXXXXXXXX.com.orgname.appname in both targets. I'm not sure why it combines the iOS and macOS conventions, with both the group prefix and the teamIdentifier one -- it was first built some time before the point in 2025 when macOS supported iOS-style groups -- but again, it's been working. For the record, The provisioning profile for EMPFileProvider has the App Groups capability enabled, and the App Groups capability is present in both build targets in Xcode. The existing group identifier is registered on the website; I've also manually registered the team-ID-less group n
Replies
8
Boosts
0
Views
308
Activity
2w
Notarization submission stays In Progress for over 45 minutes
Hello, We are experiencing repeated notarization delays for our macOS app distributed outside the Mac App Store. Current submission ID: 45d7cac0-bd8a-4d48-b886-1cad7649adf4 Previous affected submission ID: ff61de1e-15f5-4bbe-8b34-a91a6f73b978 Issue description: xcrun notarytool submit succeeds and returns a submission ID. xcrun notarytool info keeps returning In Progress for a very long time. In the current case, the submission has remained In Progress for more than 45 minutes. This issue has happened repeatedly across multiple submissions. What we have already checked: We are not using a local proxy for notarization requests. We separated submit and polling in our build script to verify the exact stage. We retried multiple times. We reduced package contents to rule out newly introduced app content. Could someone from Apple please help check whether these submission IDs are stuck in the notarization pipeline, or advise what additional diagnostics we should provide? Thank you.
Replies
4
Boosts
0
Views
144
Activity
2w
Reply to Notarization submission stays In Progress for over 45 minutes
lingyun1998 wrote: I have submitted it for review repeatedly for more than 30 times. Submitting the same request over and over again isn’t going to help. In my previous post I suggested you read Q&A with the Mac notary service team, which says: If your app [requires additional analysis], rest assured that we’ve received your file and will complete the analysis, though it may take longer than usual. and: In addition, if you’ve made changes to your app while a prior upload has been delayed, it’s fine to upload a new build. So, it’s fine to submit a new build if you’ve made meaningful changes to your product, but submitting the same build multiple times is pointless. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
2w
Notarization submissions stuck in “In Progress” for >24 hours (CI / REST API) – production impact
We are experiencing notarization submissions that remain in the “In Progress” state for an extended period (over 24 hours), with no status transition and no submission log available. This is occurring in an automated CI environment using the Notary REST API (non-interactive submission and polling). Re-submitting the same package only results in additional submissions also stuck in “In Progress”. There does not appear to be any API mechanism to cancel, clear, or expire these submissions once they are created. We have already opened an Apple Developer Support case regarding this issue (Case ID: 102818066745 & 102819008943), but have not yet received clarification on what is causing these long-running “In Progress” states. This issue is impacting our production release pipeline, as we are unable to reliably complete notarization for signed packages within an expected timeframe. Based on other reports in this forum (including thread 811968), this behavior appears similar to cases wh
Replies
5
Boosts
0
Views
553
Activity
2w
Unable to enable eligibility for External Purchase Link APIs — seeking clarification
Hello, I am currently implementing External Purchase Link and External Purchase Custom Link and am encountering an issue where both ExternalPurchaseLink.canOpen and ExternalPurchaseCustomLink.isEligible always return false under all test conditions. I would like to confirm whether my setup is missing any required steps or whether this behavior is expected. Below are the details of my current environment and configuration: 🔧 1. Development Environment Xcode: 16.3, 16.4, 26.0 beta 4 Devices: iPhone running iOS 26.2 beta iPhone running iOS 16.7.12 macOS 15.5 (real device testing) Simulator iOS 18.0 Build Type: Local development build using a Developer Provisioning Profile Sandbox account signed in during testing 🔑 2. Entitlements (Developer site & Xcode) In Certificates → Identifiers → App ID, both capabilities are enabled: StoreKit External Purchase StoreKit External Purchase Link The .entitlements file in Xcode includes: com.apple.developer.storekit.external-purchase = YES com.apple.developer.st
Replies
2
Boosts
0
Views
237
Activity
2w
Significant delay in Transaction ID availability via App Store Server API (Error 4040010)
Hi everyone, I’ve been encountering a recurring issue with the App Store Server API over the past 48 hours, specifically regarding the Get Transaction Info endpoint. Endpoint: GET /inApps/v1/transactions/{transactionId} Environment: Production Error Code: 4040010 (TransactionIdNotFound) The Issue When a user completes a purchase in our app, the client-side sends the transactionId to our backend for validation. However, when our server immediately calls the Get Transaction Info API using that ID, it frequently returns a 4040010 error, stating that the transaction ID cannot be found. Key Observations Eventual Consistency Delay: If we implement a retry logic and wait for 2 to 5 minutes, the exact same transactionId eventually becomes queryable and returns a valid signedTransactionInfo. Notifications vs. API: Interestingly, our server receives the App Store Server Notifications V2 (webhook) for these transactions almost instantly. The notifications contain the correct data, but the Pull API seems to lag
Replies
1
Boosts
0
Views
89
Activity
2w
AppIntent search schema opens app as only option
I am trying to use @AppIntent(schema: .system.search) to search in my app via a Siri voice command, but I want to be able to return a .result that does not open the app, yet still get the model training benefits from the schema. Very new to this, this is my first app, so I would appreciate some guidance. I haven't gotten to the voice part, I tested on Shortcuts. Do I need to do AppIntents without the schema and wait until there is a search schema that does not open the app, or should I be using a different schema? What am I missing?
Replies
2
Boosts
0
Views
578
Activity
2w
Reply to question about migrating `Sign in with Apple`
Hi @Dick_Long, Thanks for your questions. You wrote: A. From the document above, can I performed the Steps 1&2 before the app transfer? if so, is there a maximum lead time for these transfer_subs? To migrate their users, the transferring team (Team A) must obtain their user access token(s) and generate a transfer identifier(s) prior to initiating the app transfer. If the app belongs to an app group, Team A must also ungroup them before initiating the transfer. If the app is configured with a Services ID, it will also transfer. If Team A wants to keep the Services ID, they must remove the association with the app before initiating the transfer. Important: If a user doesn’t use any other applications from Team A, Team A will no longer be able to communicate with the migrated user using their private email address after the transfer. Next, you wrote: B. Regarding Step 5(Team B exchanging transfer identifiers via https://appleid.apple.com/auth/usermigrationinfo) are there specific rate limits (requests per se
Replies
Boosts
Views
Activity
2w
Reply to Is calling different SBApplication objects from different threads bad?
I've made a change to our app. We have a faceless helper app that we used to use for running all our scripts. It uses XPC for communication between it and the main app. It was developed many years ago when we needed to stop blocking the main thread when multiple jobs were running scripts. I updated it a few days ago to use ScriptingBridge (like we'd previously done to the main app). This has been used in production now for a couple of days. We no longer experience crashes caused by the low-level AE system (AECreateEmptyEvent, etc.). That's the good news—the AE errors for one job no longer take out the app and any other jobs. Fabulous! I do still get problems that appear to be empty replies from telling the InDesignApplication (an SBApplication subclass) to doScript:ourScript. This mostly happens when running multiple jobs at once and when I switch our main app in and out of the foreground. I assume doing that jiggles a lot of Jell-O. I don't know what would cause that; the AE system, SB, or InDesign.
Replies
Boosts
Views
Activity
2w
Reply to Update for existing app (6759172913) waiting for review – verifying submission
Small update regarding our submission: The build is still currently in “Waiting for Review”, so I just wanted to kindly check whether everything looks correct on our side in App Store Connect. Since the previous version of the app was already approved and is currently live on the App Store, we wanted to make sure that this update — which mainly includes a few UI improvements and small usability adjustments — does not have any missing metadata or configuration that could delay the review process. If anyone from the App Review team happens to see this and can confirm that the submission looks complete from your side, we would really appreciate it. Thank you very much for your time and for the work you do supporting developers. Kind regards, José Rodríguez
Replies
Boosts
Views
Activity
2w
Xcode 26.4 Beta 2 - Missing Capability, Family Controls App & Website Usage
Hi One of the new Family Control API's requires the new Family Controls App & Website Usage capability but it appears to be missing in the latest Xcode beta (26.4 B2). MacOS and iOS all running 26.4 Beta 3. Does anyone know if we have to wait for Xcode 26.4 Beta 3 and it's associated SDK's for this one to become available?
Replies
3
Boosts
0
Views
115
Activity
2w