“missing package product”

I'm building a package for my custom fonts. But not be able to register custom .ttf file in a Swift Package. Any recommendations for this?

Hello Apple community ! I'm facing an issue regarding xcstrings in a local package in my project. It's an iOS application with a local package containing multiple targets. The Localizable.xcstrings is located in the app target and contains keys for the app and targets of the local package (Views in the targets look for keys in the main bundle) My issue is that auto detection/extraction seems to work only for keys used inside the app bundle. It doesn't look in the package. However, if I add a Localizable.xcstrings inside a package target, it gets populated. Is this normal behaviour & is there any way to make extraction put the keys in the main bundle xcstrings instead ? I feel like it should be normal behaviour if no xcstrings is found in the package My fallback would be to set all keys in manual extraction state but it's not ideal ;) Thanks in advance for the great work Eric

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.

I am running into an issue mainly on my CI, but the issue is present either way. I have a project with multiple Swift Packages as dependancies, most are remote but i have a couple that are local swift packages. On first load of xcode, it will fail to fetch the local packages, if i keep xcode open, around 10 minutes later, it will automatically try and fetch the packages but this time will succeed. Has anybody had this issue? Apart from deploying these packages remotely, is there any other solutions? xcode 13, 13.1, 13.2 all tried and have the same behaviour. Thanks!

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

Hi, I'm trying to hook up some test in app purchases to test purchase code between our app and our app's backend. When I try to load products (requestProductData) with my Sandbox account, my product identifiers come back in the invalid product identifiers member of the response. My product says it's in waiting for review status in app store connect, and I'm logged in to the app store with my sandbox account on my device. We just accepted the paid apps agreement as well--is there some propagation time to that? The product ID I'm using (both in app store connect and in-app) is test_durable. Do I need to append the package name to that or something? I've dug through the docs and through the forums here and come up empty. I tried using the Xcode storekit test harness and the issue there is that because that doesn't actually talk to the store apis, I can't use that to test my backend correctly validating/processing the transactions. Thanks!

I'm working on an iOS project that uses Swift Package Manager to download and link a private package to it. The package is developed internally in our company, and it contains over 4000 files. The package creates namespaces using extensions, eg: /* Core.swift */ public enum Core { public enum Blobs { } t/* More enum declarations here */ } /* SomeBlob.swift */ public extension Core.Blobs { public class SomeBlob { /* implementation here */ } } The issue that we're facing is that we are unable to access all the classes, structs and enums from the Package, even though they've all been declared public. We are only able to access approximately a quarter of the files (up to the ones beginning with the letter C). Has anyone had this issue before ? Any suggestions are welcome. Thanks in advance :)

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