missing package product

Hi! Support for binary dependencies in Xcode 12.0 is really a great addition to the whole ecosystem built around Swift Package Manager. Last year we learned that the non-binarySwift Packages don't work well with the module stable frameworks. Is there a plan to add a module stability to open-source Swift Packages, too? In a way that closed-source binaries could depend on open-source Swift Packages? Thanks!

With every package I install / deploy I get an error The package was signed with a certificate that has expired I view the cert, and it expires in 2020 (Office 2016 15.15.0 patchs). But it's with any .pkg file that i try on 10.11.1 (all betas). Allow from anywhere is selected in Security and Privacy.

I made a pkg install my APP but failed to install to other macbooks because of digital signature invalid warning : Signed.pkg can't be installed because its digital signture is invalid. I signed again,but failed to install again with same warning. bogon:Desktop tanhuang$ productsign --timestamp --sign Developer ID Installer: Tan Huang (NGMD5RC85D) HuionDriver.pkg Signed.pkgproductsign: using timestamp authority for signatureproductsign: signing product with identity Developer ID Installer: Tan Huang (NGMD5RC85D) from keychain /Users/tanhuang/Library/Keychains/login.keychain-dbproductsign: adding certificate Developer ID Certification Authorityproductsign: adding certificate Apple Root CAproductsign: Wrote signed product archive to Signed.pkgbogon:Desktop tanhuang$ codesign -dvvv Signed.pkgSigned.pkg: code object is not signed at allbogon:Desktop tanhuang$ spctl --assess -v Signed.pkgSigned.pkg: rejectedsource=no usable signaturebogon:Desktop tanhuang$ spctl --assess -v --type instal

I've been trying all morning to get a trivial Swift package (local) working. I'm using macOS 11.2 with Xcode 12.4 on an iMac Pro. In all cases, I'm left with a compile error of Module 'MyPackage' has no member named 'some symbol'. Setup: Simple iOS single view app. Swift package with a simple Utility class with a static func named doWork that just prints a message. I've of course imported my package in the app's file where I need to use the utility function. What I've tried... Created a standalone Swift Package first. Then, the app project and dragged the Swift Package into it. As above but with a workspace instead of a project. Started with just an app project. Created my Utility.swift file in that project. Then, created the Swift package and dragged that Utility.swift file into the package's main source folder. This is basically what is demoed in Creating Swift Packages (WWDC 2019). During the first part showing how to create a local package

I'm notarizing my .pkg installer and even stapling the ticket after, but I still get rejected after checking it with the following command:spctl -vvv --assess --type install path/to/my/notarized.pkg path/to/my/notarized.pkg: rejected origin=3rd Party Mac Developer Installer: My Certificate Name (XXXXXXXXX)My pkg is being created with the packages app and then signed using pkgutils. Then it's notarized and after the success response from Apple I'm stapling the ticket into it. The pkg contains an app that is also signed of course.How can I find more information about what's going on? Is there a log somewhere?Thanks in advance.

Hi,I have an iOS application which uses in-app purchases.I have already set the environment for IAP:Set all the Agreements Tax and Banking sections,Created IAP products on iTunes connectTurned on In app purchases in the capabilities tabImplemented my code to retrieve the product list and to perform a purchase validating the receipt server-sideI have also tested all with a sandbox environment and all works as expected: the list of products is correctly received by the store I can purchase a product validating the corresponding receipt.I have also tested the application using Testflight which creates automatically a sandbox user for all testers and all works as expected.I submitted my application to the Apple store and the revision has been passed so that at the moment the application is in Pending Developer Release status, all the products have been approved.In order to try an actual purchase (using a real credit card) I have generated a promo code with iTunes conne

Hi, after a software update of our previously successfully notarizated installion .pkg we now receive a cryptic notarization issue refusing the entire .pkg: { logFormatVersion: 1, jobId: 5cff2d71-7228-4fb4-a39d-329084cd2713, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: my_installer.pkg.zip, uploadDate: 2024-12-04T23:17:14.016Z, sha256: 2f26d0376506abe130ac904d7cb0d0cd5428666624428da9f44da7756352844f, ticketContents: null, issues: [ { severity: error, code: null, path: my_installer.pkg.zip, message: Package my_installer.pkg.zip has no signed executables or bundles. No tickets can be generated., docUrl: null, architecture: null }, { severity: warning, code: null, path: my_installer.pkg.zip/my_installer.pkg, message: The contents of the package at my_installer.pkg.zip/my_installer.pkg could not be extracted., docUrl: null, architecture: null } ] } What could be the reason for that? We've also submitted the .pkg

I am very new to this, so apologies if this is a noob question. I am creating a package using Packages. I have a Developer ID certificate that expires in 2027. If I set my project to use that certificate before building in Packages, the build fails. So I am certifying after using terminal. However, in both the Terminal certification and running the installer for my .pkg, it says that the certificate is expired. I don't understand how a certificate that expires in 2027 can already be expired. Any ideas out there? I found a post with the same problem from 7 years ago and there were no responses. Thanks all!

I'm building an iOS app (the supported destinations in the app target are iOS, iPad and Mac - Designed for iPad). I've many SPM frameworks in order to split my codebase in different features. I want to export the localisations for the different packages and the app using Xcode but it fails. I followed the Apple guide regarding SPM localization: the packages contains a Resources folder with a folder for each language supported. I specified the platforms .iOS(.v16) in the packages. But it seems that exporting the localisations using the Product > Export Localizations feature in Xcode compiles also the packages and app for macOS. Here is the error message: Showing Recent Messages /Users/axel/Developer/AppName/Packages/Helpers/Sources/Helpers/UIKit/UIImage+Extension.swift:7:14: No such module 'UIKit' /Users/axel/Developer/AppName/Packages/Helpers/Sources/Helpers/UIKit/UIImage+Extension.swift:7:14: UIKit is not available when building for macOS. Con

Dear support team, is it possible to rename a notarized ZIP package and not to loose the notarized status? One of our ZIP package contains resources and binaries which are code signed. The archive itself is accepted after submitting and uploading during the notarization process (online notarization). Unfortunately, the ZIP cannot be stapled (offline verification). So, is the filename part of the notarized ZIP package or can a ZIP package be renamed? Best regards, Stefan