missing package product

Hi Apple Developer Forums,Apoliges if this is a silly question - but I can't seem to find all of the product images for both iOS, OSX, and watchOS.The following links have most of the product images, but for example the new MacBook is missing from the mac guidelines:App Store GuidelinesMac App Store Guidelines

In sandbox testing, I was able to get auto-renewing subscription to work, but decided to switch to one-time in-app purchase. I've read many how-to's, but I'm missing something. My app has Bundle ID com.myname.id1 and IAP capability added. The IAP has Product ID com.myname.id2. My agreements are up-to-date (auto-renewing subscription worked). The In-App Purchases screen lists my IAP under Drafts (1); is this expected? [SKPaymentQueue canMakePayments] returns true. [[SKProductsRequest alloc] initWithProductIdentifiers:set] (where set contains com.myname.id2) responds to [request start]. In the delegate, NSArray *product = response.products comes back empty. Does the IAP have its own Bundle ID? What am I doing wrong? What have I not told you that's important? I've been stuck for a few days on this. Thanks!

Hello everyone, I am trying to create a macro that depends on an external package to abstract some of the packages logic. The point is that the dependency does not support macOS which results in a build failure when trying to build the macro. Since macOS 10.15 is required for creating macros, any thing can be done to get it to work? Here is a sample to what I'm trying to do import PackageDescription import CompilerPluginSupport let package = Package( name: Stringify, platforms: [ .macOS(.v10_15), .iOS(.v13), .tvOS(.v13), .watchOS(.v6), .macCatalyst(.v13) ], products: [ .library( name: Stringify, targets: [Stringify] ), .executable( name: StringifyClient, targets: [StringifyClient] ), ], dependencies: [ .package(url: https://github.com/apple/swift-syntax.git, from: 509.0.0), .package(url: https://github.com/MyDependency, from: 1.0.0), ], targets: [ .target( name: Stringify, dependencies: [StringifyMacros] ), .executableTarget( name: StringifyClient

In regular projects, there is an Export Localizations option in the Product menu, but for Swift Packages, this is not available. Adding local Swift Packages as dependencies of a regular project and using Export Localizations on the regular project doesn't include the Localizable strings from the Packages' sources either. The command-line version (xcodebuild -exportLocalizations) has the same restrictions. Is there a way to export NSLocalizedString occurrences to an xliff for Swift Packages? Or are we supposed to do things manually for now?

Hello! I encountered an issue while packaging and uploading the project to the Mac store. I received an email stating: ITMS-90296: App Sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. Though you are not required to fix the following issues, we wanted to make you aware of them: ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to

I created PKG installer in command line (see below, command's output is in italic). Installer is opening on my MBP, but after uploading on server and download by link, macOS shows TestApp.app.2.0(32).pkg” can’t be opened because Apple cannot check it for malicious software. TestApp.app is application signed by Developer ID Application certificate and notarised with Xcode. Check TestApp.app signing: codesign --verify --verbose TestApp.app TestApp.app: valid on disk TestApp.app: satisfies its Designated Requirement spctl --assess --verbose TestApp.app TestApp.app: accepted source=Notarized Developer ID Build package component pkgbuild --identifier --version '2.0(32)' --sign 'Developer ID Installer: ….’ --install-location /Applications --component TestApp.app component.pkg pkgbuild: Adding component at …../Create PKG/TestApp.app pkgbuild: Using timestamp authority for signature pkgbuild: Signing package with identity Developer ID Installer: …” from keychain …./Librar

My company requested a Fairplay deplpyment package. How do I follow-up on the status? The email ID mentioined in the acknowledgement fps@apple.com seems to be down.

Hi, I'm writing a custom step to our installer using IntallerPlugins.framework and class InstallerPane. Is it possible to get path and name of the pkg file from InstallerPane object? I tried solution from this page but it seems right now the delegate is not set. http://s.sudre.free.fr/Stuff/Installer/Installer_Plugins/InstallerPlugins-FAQ002.html. Also there's no appropriate tag for this framework.

Hello, I have an Xcode project (not a workspace), that depends upon a swift package found on GitHub. You can find the PR here that demonstrates the problem. https://github.com/bolsinga/MissingArt/pull/2 My project has a Swift Package dependency. It's a macOS target. If I Cmd-B in Xcode it will build and run just fine (finding the package and building it too). If I xcodebuild -verbose from the command line in CI, it will fail. The problem is that when the application files compile and import the module found in the Swift Package, the module is not found. If this were ObjC, I'd know that the search path was not found. I do not see anything about my module on the link line. I have followed the instructions about adding a Swift Package Mgr dependency, and it works locally. I'm sure that I'm missing one small thing; I'm not sure if xcodebuild with no options (thus getting the default behavior) is the proper thing to do. Any ideas? Thank you, -- Greg