Posts under Developer Tools & Services topic

Post

Replies

Boosts

Views

Activity

iOS xcode app, During "Distribute app" get error The archive contains nothing that can be signed
I had successfully distributed my app months ago and trying same today and get "The archive contains nothing that can be signed. Verify that your build process has compiled binaries and copied in bundled resources." message when I click the "Distribute app" button. My project is a simple iOS xcode project that I had success in same operation back on Feb 8, 2024, same project code and settings. Verbose log: 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodWatchOSAdHoc: 0x600004700d70> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodWatchOSEnterprise: 0x600004700c30> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodTVOSEnterprise: 0x600004700c90> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Accepted distribution method <IDEDistributionMethodiOSEnterprise: 0x600004700c70> 2025-01-22 00:49:43 +0000 [MT] Accepted distribution method <IDEDistributionMethodDevelopmentSigned: 0x600004700c80> 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodTVOSDevelopmentSigned: 0x600004700d30> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodWatchOSDevelopmentSigned: 0x600004700d90> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodDeveloperIDNotarizedApp: 0x600004700d40> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodDeveloperID: 0x600004700cf0> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodSaveBuiltProducts: 0x600004700ca0> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodDevelopmentSignedMac: 0x600004700d60> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodExportArchive: 0x600004700c60> because it doesn't support distributing archive 2025-01-22 00:49:43 +0000 [MT] Rejected distribution method <IDEDistributionMethodMacApplication: 0x600004700d80> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodTVOSAppStoreDistribution: 0x600004700cd0> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Accepted distribution method <IDEDistributionMethodiOSAppStoreDistribution: 0x600004700d10> 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodiOSAppStoreValidation: 0x600004700d20> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodTVOSAppStoreValidation: 0x600004700cc0> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodMacAppStoreDistribution: 0x600004700c40> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodMacAppStoreValidation: 0x600004700c50> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodInAppPurchaseContentPackage: 0x600004700d50> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodMacAdHoc: 0x600004700d00> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Accepted distribution method <IDEDistributionMethodiOSAdHoc: 0x600004700cb0> 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodTVOSAdHoc: 0x600004700ce0> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodWatchOSAdHoc: 0x600004700d70> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodWatchOSEnterprise: 0x600004700c30> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodTVOSEnterprise: 0x600004700c90> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Accepted distribution method <IDEDistributionMethodiOSEnterprise: 0x600004700c70> 2025-01-22 00:49:45 +0000 Accepted distribution method <IDEDistributionMethodDevelopmentSigned: 0x600004700c80> 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodTVOSDevelopmentSigned: 0x600004700d30> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodWatchOSDevelopmentSigned: 0x600004700d90> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodDeveloperIDNotarizedApp: 0x600004700d40> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodDeveloperID: 0x600004700cf0> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodSaveBuiltProducts: 0x600004700ca0> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodDevelopmentSignedMac: 0x600004700d60> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodExportArchive: 0x600004700c60> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Rejected distribution method <IDEDistributionMethodMacApplication: 0x600004700d80> because it doesn't support distributing archive 2025-01-22 00:49:45 +0000 Available distribution methods: {( <IDEDistributionMethodiOSAppStoreDistribution: 0x600004700d10>, <IDEDistributionMethodiOSAdHoc: 0x600004700cb0>, <IDEDistributionMethodiOSEnterprise: 0x600004700c70>, <IDEDistributionMethodDevelopmentSigned: 0x600004700c80> )} 2025-01-22 00:49:45 +0000 Step failed: <IDEDistributionAnalyzeArchiveStep: 0x6000084ddd40>: Error Domain=IDEDistributionErrorDomain Code=5 "The archive contains nothing that can be signed." UserInfo={NSLocalizedDescription=The archive contains nothing that can be signed., NSLocalizedRecoverySuggestion=Verify that your build process has compiled binaries and copied in bundled resources.}
0
0
294
Jan ’25
Scipy problems with OpenBLAS and Accelerate
I'm using M1pro and have successfully installed Numpy with Accelerate following, and it really speedup my programs. I also ran np.test() to check the correctness and every test passed. However, I can't install Scipy with Accelerate, since the official document said Accelerate has a LAPACK of too old version. I can't even find a scipy that can pass scipy.test(). I tried the codes below: conda install numpy 'libblas=*=*accelerate' conda install scipy np.test() as fails, sp.test() can't even finish conda install numpy 'libblas=*=*openblas' conda install scipy Both np.test() and sp.test() can finish, but with many failures. I believe the bugs are due to Conda. pip install --no-binary :all: --no-use-pep517 numpy pip install scipy np.test() has no failure and went fast, sp.test() uses OpenBLAS and has 3 failures. This is the best version I have found. So my question is: can we find a reliable version of scipy on M1? Considering the popularity of scipy, I think it's not a high-living expectation. And a question for Apple: is there really a plan to upgrade the LAPACK in Accelerate?
2
0
2.7k
Jan ’25
Apple support unresponsive
I've been contacting Apple Developer support for over 3 weeks now regarding new agreement that is not visible anywhere in account and no option to accept it either. Submitted ticket twice but no response at all. All they have to say is "Thank you for contacting us. We’ve received your support request and will get back to you as soon as possible. Your case ID is 102320028158. If you have any additional information you’d like to provide or would like a status update on your case, please reply back to this email."
2
0
858
Feb ’25
Apple is not granting access to the developer account, but funds have already been partially charged
Hello, We are facing a serious issue while trying to gain access to our developer account. We have submitted all the required documents (passport scan, payment information), but we still have not received access. At the same time, funds have already been partially charged from our card, yet there has been no progress from Apple. Support is not providing clear answers, and the process is being delayed. This is seriously affecting our work! Has anyone encountered a similar situation? How can we speed up the resolution? Any advice would be greatly appreciated. Thank you!
0
0
127
Feb ’25
Error When Trying to Switch from ADEP to AdHoc for iOS App Deployment
I have created two different apps using ADEP, and they were working on iPad with iOS 14.6 and 14.7.1. The environments are as follows: Environment: 1.Mac mini (Mac OS X 10.7.5) Xcode 8.3.2 2.iMac (OS X El Capitan 10.11.6) Xcode 7.3 The certificates were exported from the environment in 1 and imported into 2. When I tried to switch from ADEP to AdHoc for app creation, I encountered an error. Specifically, the app worked fine on an iPad running iOS 12.5.7 in environment 1, but on devices with iOS 14.6, 14.7.1, and 17.7, the installation was successful, but when I tried to open the app, the following error message appeared: “XXXXX” needs to be updated To run this app on this version of iOS, the developer needs to update the app. Additionally, in environment 2, I’m unable to archive the app. Is it possible to create a working app by simply switching from ADEP to AdHoc without making any other changes to the environment?
0
0
122
Feb ’25
Verification Error in Production: Should I Submit My App with the Backend in Sandbox Mode?
Hello, My payment system works correctly when my backend is in sandbox mode, but when I submit my app for review, I get the following error: VerificationException [Error] at SignedDataVerifier.verifyNotification (/Users/---/node_modules/@apple/app-store-server-library/dist/jws_verification.js:126:19) at SignedDataVerifier.verifyAndDecodeNotification (/Users/---/node_modules/@apple/app-store-server-library/dist/jws_verification.js:121:14) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async file:///Users/---/src/api/routes/apple.routes.js:22:18 { status: 2, cause: undefined } Main Question For Apple to approve in-app purchases, should I submit my app for review with the backend in sandbox mode or production? Possible Causes of the Error I would appreciate any suggestions on what might be causing this error and how to fix it. Thanks in advance! 🚀
1
0
209
Feb ’25
Error Apple Git-154
I have an error when I use Apple Git-154 to clone the repository: My OS version: Sequoia 15.2 tannguyen@Mys-MacBook-Pro ~ % git -v git version 2.39.5 (Apple Git-154) tannguyen@Mys-MacBook-Pro ~ % git clone https://github.com/nestjs/nest.git Cloning into 'nest'... remote: Enumerating objects: 187515, done. remote: Counting objects: 100% (118/118), done. remote: Compressing objects: 100% (42/42), done. error: inflate: data stream error (incorrect data check)10 MiB/s fatal: pack has bad object at offset 212760331: inflate returned -3 fatal: fetch-pack: invalid index-pack output
0
0
372
Jan ’25
Missing Developer Kit for build 22H417
I cannot find this specific KDK for my build 22H417. I need help locating and downloading this Developer Kit. Error Domain=KMErrorDomain Code=34 "Missing Developer Kit: As of macOS 13.0, you will need to install a KDK matching your build 22H417 to rebuild kernel collections." UserInfo={NSLocalizedDescription=Missing Developer Kit: As of macOS 13.0, you will need to install a KDK matching your build 22H417 to rebuild kernel collections.} I
0
0
335
Feb ’25
Unresponsive Developer Support
My business is trying to renew our Apple Account. On renewal we get a message saying we’ll receiving an enrollment status email soon - we are yet to receive one and it’s been over a week. Our Apps have since been removed from the App Store. We have multiple cases open with Developer Support, the only response to date was with a number to call. That number was for consumer support and thus couldn’t help. How can we get hold of someone to assist? This is having a massive impact on our business.
0
0
123
Feb ’25
I have a bone to pick with Xcode
Despite Xcode being the one and most used IDE for iOS, it is far from perfect. I have used many tools in my career and here are some features, that would make it much better or what I miss from other IDEs. I encourage others to chip in discussion and lets all hope, Apple starts to improve Xcode. Will put each issue in separate comment below. Slow debugger: not sure what bloat Xcode has or what it is doing, but sometimes it can take more than 10 seconds from breakpoint firing to actually see values. Moreover when debugging SwiftUI or something objC I have to drill down to see value of property or use po and p command and hope it works. SwiftUI views and states are a big pain to debug, to see what is changing a value I have to always use didSet trick or some other black magic. Is it too hard to make it easier? Breakpoints with condition can take up to 1 minute to load and I have M1 Max MBP. Just tried cursor IDE few days ago and breakpoints are much faster and without too much bloat in variable inspector.
7
0
352
Feb ’25
The Apple Developer Program enrollment is taking too long!
My Apple ID is linked to several organizations for which I developed apps in the past, and I want to enroll myself as a solo developer in the Apple Developer Program. I paid the $99 fee more than a week ago and received an “Order Acknowledgement” email stating that processing would take up to two business days. However, it has now been eight days, and my enrollment is still marked as pending on the Apple Developer website.
0
0
260
Jan ’25
Can't compile asset catalog when including iMessage App Icon asset
I'm trying to add an iMessage extension to my app, and upon adding the iMessage App Icon set, I ran into an issue with one specific icon size: 1024x768px, aka 1x 1024x768pt. When I remove this one icon from the icon set, it compiles and runs fine, however I can't push it to the App Store as I get the error: "Asset validation failed. Missing Image Asset. Your app is missing the Large App Icon asset 'AppIcon' in 'Payload/Runner.app/PlugIns/MessagesExtension.appex'." I'm assuming this refers to 1024x768px, as this size placeholder appears upon adding a New Messages Extension Icon to my assets folder, and 1024x1024 is already included and compiles fine with it. However, when I add the 1024x768 icon, and try to run the app, I get the error: "Command CompileAssetCatalog failed with a nonzero exit code" The app icon's filename is correct, it is exactly 1024x768 px, and my contents.json correctly includes : { "filename" : "AppIcon_1024x768.png", "idiom" : "ios-marketing", "platform" : "ios", "scale" : "1x", "size" : "1024x768" } as is the same format for all of my other icons that work. Why am I running into this issue upon inclusion of this one required size? How do I fix it?
2
0
763
Jan ’25
Ask for help and solutions about the Apple developer account ban
Our team has not been involved in the Apple development field for a long time, and due to the lack of deep enough understanding of Apple's development related rules in the early stage, there were some mistakes in the operation process, resulting in the account being blocked. In the more than a year since the account was blocked, we have actively engaged in learning, deeply studied the rules and requirements of Apple's development through various channels, and continuously improved our professional quality to ensure that future development work can fully comply with the specifications. Now, we'd like to see if there's a viable way to unblock our account. We've learned from the lessons we've learned and are confident that we'll be able to follow Apple's rules in our future development to bring users a high-quality and compliant app."
0
0
285
Jan ’25