“missing package product”

I think I finally did it! I eventually gave up and switched to a different gateway: https://github.com/gruberb/ohttp-gateway Once configured properly, everything started flowing, even from TestFlight (which I hope means that it will be the same from the App Store). Feels kinda unreal that this is actually happening, I had lost hope. Thanks to everyone who helped out!

I'm trying to release an app with this kind of business model right now. Review team is bullying me for my products, asking stupid questions like: Please explain why free trial period is submitted as separated in-app purchase instead of being included in the paid 'Lifetime Unlock' in-app purchase. So tiresome -_-

I had to explicitly update the Package.swift file by adding the resources key. For example, I added Resources so I would have to create a Resources/ folder, add my .mp3 to that folder, and it should work. Read more in article Bundling resources with a Swift package targets: [ .executableTarget( name: AppModule, path: ., resources: [ .process(Resources) ] ) ],

Kevin, First, I wanted to apologize for not replying for a full month, as well as thank you very much for your reply. I was pulled away from this project for a couple weeks, and when I got back I was still spinning my wheels getting the driver installed. I only today found my issue, which wasn't something you could have helped with since I hadn't thought to include the correct context in my original comment. I only found the issue after careful log monitoring in the Console app during the install process as my main installer app was running. It turns out that my bundle ID was too long. It was 67 characters and, apparently the maximum is 63. Seems like an arbitrarily short max in this day and age, and you'd think both XCode and the Developer Portal would catch that, but that's what it was. When I redid my bundle IDs more succinctly (and all my permissions on the Apple Developer Portal), I was able to successfully install/register/enable the driver. I have granted it permission in System Settings, it shows up u

macOS 26.4 Beta appears to have changed how built-in MacBook keyboard events are routed through IOHIDSystem. Third-party virtual HID devices loaded via DriverKit no longer receive events from the built-in keyboard. As a small side note here, I have no idea why anyone is using DriverKit to create virtual HID devices. CoreHID provides its own virtual device API which, as far as I can tell, should be able to do everything you could do with a virtual device created through DriverKit. It's possible I've overlooked some limitation (and, if so, please let me know!) but as far as I can tell a number of products have chosen a much more difficult implementation without any real benefit. https://developer.apple.com/documentation/corehid/hidvirtualdevice External keyboards are unaffected. This is already confirmed across multiple users: I'd normally ask you to file a bug on this but the engineering team is aware of the issue, so I don't think additional bugs are necessary in this particular case. https://github.

Found the solution it seems to be missing CFBundle... keys even though Xcode auto generated parts of it and then it thought its a no code dext. Next problem it has an included embedded provisioning profile but the console shows its missing the entitlement that is included in the embedded provisioning profile...

Yes, users will be able to reach your Unlisted app's App Store product page using the provided URL. The unlisted app URL can be found in App Store Connect -> Pricing and Availability -> App distribution Methods