“missing package product”

Hello We have a pkg installer whose signing certificate is expiring next month. It has a trusted timestamp on it. As per https://developer.apple.com/support/certificates/ it states Developer ID Installer Certificate (Mac applications) If your certificate expires, users can still install packages that were signed with this certificate as long as the package includes a trusted timestamp. Previously installed apps will continue to run. However, new installations won’t be possible until you have re-signed your installer package with a valid Developer ID Installer certificate. If your certificate is revoked, users will no longer be able to install applications that have been signed with this certificate. Wanted to check on behavior for new installations post expiration date. Since the installer has a trusted timestamp we would not need to release a new installer with new cert ?? Any guidance here would be much appreciated.

All I want to do is re-write programs that I wrote in Realbasic years ago, so that I can get them to 64 bit code. I do not want to sell anything that I write on the App Store. They are for my personal use only. Can I do this with the $99 developer package? Or should I just go with Xojo? Thank You Dennis Edwards (edwardsx@mac.com)

Hi,I couldn't find a clear answer on this:The official links of notarizing you MacOS app, found below, only discuss notarizing and stapling an APP file, not a PKG file:https://developer.apple.com/documentation/xcode/notarizing_your_app_before_distributionhttps://developer.apple.com/documentation/xcode/notarizing_your_app_before_distribution/customizing_the_notarization_workflowHow do I this for the PKG installation file?Thanks,Yaron

Need help understanding if this is an XCode issue or user error. I created a XCFramework to distribute as a Swift Package. Manifest file ex: // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( ttname: MyFramework, ttplatforms: [ ttt.iOS(.v9) tt], ttproducts: [ tttt// Products define the executables and libraries a package produces, and make them visible to other packages. tttt.library( ttttttname: MyFramework, tttttttargets: [MyFramework]) tt], ttdependencies: [ tttt.package(name: Alamofire, url: https://github.com/Alamofire/Alamofire, .upToNextMajor(from: 4.8.2)), tttt... tttt], tttargets: [ tttt.binaryTarget( ttttttname: MyFramework, ttttttpath: ./Sources/MyFramework.xcframework) tt] ) When I import my Swift package in to a new XCode project, the modules in the dependencies are not found. Only when I manually import each dependency as a Swift Package

How can you distribute an XCFramework via Swift Package Manager when it has dependencies on other Swift packages? We accomplished this with CocoaPods in order to distribute our closed source SDK that has dependencies, but need to migrate to SPM. Note none of the types from the dependencies are used as part of our module’s public interface - usage is purely internal. I’ve made a lot of progress following these steps for a simple example: Create Framework Project Create a new iOS Framework project in Xcode and name it WallpaperKit In the project settings select the target and verify in Build Settings that Build Libraries for Distribution is Yes then set Skip Install to No Create a new UIViewController subclass, name it WallpaperPreviewViewController, make it public, and add some functionality to it to show a UIImageView Add a new Package Dependency in the project settings, for this example we’ll use https://github.com/onevcat/Kingfisher, and specify exact version 8.5.0 Add internal im

I've tried submitting a Safari extension multiple times to the Safari Extensions Gallery. I've received a 'Bad Package' email from safari-extensions@apple.com twice now.The extension was built on the latest version of OSX 10.10 and the latest version of Safari each time, and was built on a different MacBook Pro for the second submission to check that this was not where the problem was. Is there anything that I could be doing wrong other than not building the package on the latest version of Safari?This is the response I keep getting back from Apple:Thank you for submitting your extension Copyright Hub Safari Extension to be considered for a listing on the Safari Extensions Gallery. During our review, we found that the extension was built with an older versions of Safari.Your extension can be built using any version of Safari on Mac OS X 10.10.Please rebuild your extension with the latest version of Safari, then resubmit your extension so that it can be reviewed and considered for a listing o

I have an app built using python with pyinstaller. I was able to successfully get the app notarized and open it on my computer as well as a different one (OS 11.6.1). I can also get the pkg successfully notarized, but when I attempt to launch it on my own computer (or a different one), an error box immediately appears stating There was an error reading the package along with JavaScriptError. I looked at the log file corresponding to the notarization, and I saw no error messages or warnings. Neither java nor javascript appear anywhere. This was not a problem for me a couple weeks ago when using a slightly different version of my program. Is there a different log file of some type, associated with javascript, that might shed light on the problem? Update: I did just try to check whether package passed the gatekeeper test by typing spctl -a '/Users/..../application.pkg' at the terminal, which returned rejected

Hi There, I have a strange problem: the Swift package cannot be added to my iOS project. The problem might be due to the project settings, but despite trying for a long time, I still haven't been able to figure it out. My project is a React Native project and uses CocoaPods. When I drop the Swift package into my React Native project, the package becomes a folder. When I drop the Swift package into other iOS projects, it works without any problems. If I try to use Package Dependencies to add the Swift package, it gets stuck on Preparing to validate... My project seems unable to add any Swift packages; it cannot add other Swift packages either. The Swift package is local. However, it works fine in other projects, even in newly created React Native projects. The problem might be with my project itself, but I have no idea where to check now. please guide me with any advice, I will appreciate it!

I have started to make a Swift package to better organize my project, but I have noticed that when I try to use code from my package, some code will run much slower than when I use the same code in the project. How could this be solved? I have tried using @inlinable for functions, and it works for most functions, but some functions still fail to meet the performance standards that I see when I use the code in my project.

I have a normal UIKit project with a package dependency containing some SwiftUI. Opening the package on its own, I can preview the SwiftUI. However, when I have the package as a dependency, I get the dreaded message saying Active scheme does not build this file regardless of choosing the app or package scheme. Why can't I get a preview? Using Xcode 16

I maintain a library that has thus far used Cocoapods to manage dependencies and also distribute an xcframework of the library. I'd now like to also distribute the same library through Swift Packages but am running into issues. I'm using the same xcframework in a local Swift Package and have added all the necessary dependencies to Package.swift, but when I attempt to add this Swift Package to a test app, the app will build correctly but fail at runtime due to a missing .framework file for a dependency I'll just call THE_DEPENDENCY: dyld[61483]: Library not loaded: @rpath/THE_DEPENDENCY.framework/THE_DEPENDENCY Referenced from: <75074516-C1CD-3251-8807-94A7502176A7> /Users/ME/Library/Developer/Xcode/DerivedData/MY_TEST_APP-bwfsfwjjnagdurdnjrhhdppgitvr/Build/Products/Debug-appletvsimulator/MY_LIBRARY.framework/MY_LIBRARY Reason: tried: '/Users/ME/Library/Developer/Xcode/DerivedData/MY_TEST_APP-bwfsfwjjnagdurdnjrhhdppgitvr/Build/Products/Debug-appletvsi

Is there a recommended way to determine whether to use the development or the production server API endpoint for DeviceCheck? For App Attest, the authenticator data includes either appattest or appattestdevelop in a field of the cbor data. For IAPs, we're supposed to try the production endpoint and then retry with the development endpoint if we get a particular HTTP status code. But the docs for DeviceCheck say only to use the development endpoint in development and the production endpoint in production. What are others doing? Is there any clue in the docs that I have missed?