“missing package product”

I am using powermetrics to collect the cpu_power information. I have a small command-line utility that uses some blas functions in Accelerate and I'd like to quantify the energy consumption of the algorithm. My workflow is to start powermetrics, wait 1 second, start my program, and then stop powermetrics. During that 1 second waiting period, Package Power is: If GPU power is 0, Package power is exactly equal to CPU power even though DRAM power is not 0 If GPU power is not 0, Package power is usually (but not always) equal to CPU + GPU power even though DRAM power is not 0 When my algorithm is running, Package power is sometimes greater than the sum of everything else, but sometimes not. I've tried using powermetrics with other programs and am seeing similar results. It appears that whatever Package Power means, it does not include DRAM Power. The man page doesn't have any information, and other internet searches turn up empty or are definitely wrong. Using blas fun

Is it possible to determine the location of the pkg file being ran from inside of an InstallerJS block? If so what would the function invocation be?

Hello, we have a product package which is structured like this: / Installer.pkg / Distribution / Main Component.pkg / Scripts / preinstall / postinstall / helper [ Mach-O executable ] / Payload / Application Bundle.app / Another Component.pkg ... The helper is our custom CLI helper tool which we build and sign and plan to use it in pre/post install scripts. I'd like to ask if we need to independently notarize and staple the helper executable or just the top level pkg notarization is sufficient in this case? We already independently notarize and staple the Application Bundle.app so it has ticket attached. But that's because of customers who often rip-open the package and pick only the bundle. We don't plan to have helper executable used outside of installation process. Thank you, o/

I have developed this shared package - https://github.com/RiftValleySoftware/RVS_Spinner. It works fine. In the package test harnesses (3 iOS apps), it works great, and also, the IB storyboard renders the control (It's an IBDesignable). However, when I include it as a package in another app (I can't share the source), I get these really weird render failure messages:Error: 'UIPickerView' is unavailable in tvOS And so on. There's a bunch of not available in tvOS errors. Well...DUH. It's an iOS package and utility, and leverages a lot of things like haptics. The package explicitly states that it is iOS(12), and I can't see any indication of why my storyboard is insisting on trying to render as tvOS. What am I missing?

I have an expensive app ($300) that my users depend on for their daily work. I would like to have some of those users Flight Test an update I have prepared. But I don't want to erase the private data that the current production version has stored for each of them. Can they safely use TestFlight to load the beta version of my app without losing the data currently associated with the production version? And can they easily dump the beta version and return to the production version without losing that data? I know that if they uninstall the production version first, the private data store and settings they had developed on the production version will be lost. So I want to ensure that my testers will be able to test the beta version the same as if they had updated from the app store, in which case the private data for the app would be preserved.

Hello, I submitted a Request for a Deployment Package. However, I have not received any emails yet. Could you please let me know when I can expect a confirmation message? Thank you.

I have an app I'm returning to after a several years I'd like to freshen up, but am daunted by the changes since; 2018 WWDC - session 415: behind the scenes of Xcode Build process, points out the many changes just that year.It's Objective-C only, features several sub-projects both private and GitHub, whose .xcodeproj file I'd had dragged in as the then practice, which my main project has as dependencys; all was good.But have few but widespread problems:* IB plugins* framework headers not getting found* sub-builds failing - deprecated or now not viable code* what to do re: BWToolkit which appears stagnant?The 2nd is odd as they build ok invividually.So my question is to whether to continue the sub-project route, or try migration to modernize like envelop them as swift packages. This is not all viable as some have assets, but otherwise, what to do? I think the missing header issue is due to naming:i.e. `import foo.h` should now be `import <MyFramework/foo.h>`.But I suspect some m

I'm having an issue resolving some dependencies in the test suite for my app when using a Swift Package in my test target. Here's the setup: We have a Swift Package that contains two products. One product is the main library that is used throughout our app. The other product is a library of testing utilities, like mocks and such. This is a simplified version of its Package.Swift file with actual package/target/library/dependency names changed. let package = Package( name: Library, platforms: [ .iOS(.v14) ], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: Library, targets: [Library]), .library( name: LibraryTestUtilities, targets: [LibraryTestUtilities] ), ], dependencies: [ // Dependencies declare other packages that this package depends on. // .package(url: /* package url */, fr

When using Swift Packages in Xcode, is there a way to exclude files conditionally (in DEBUG or similar)? I know I can exclude files but I want them while in development. I have a package that contains developments resource/assets (used to seed a Core Data database for the simulator + for Previews, with images and files), but I don't want to include these files in the package used by the real app when archiving. Can we achieve that?

Hello, I have a repo with only packages (includes snapshot tests). Is there a possibility to add package to the Xcode Cloud (package does not contain a application - it's only design system)

A month ago I joined a team and cloned the project from git, and when building the project in Xcode 13 (which I had recently installed) I ran into build issues: I reviewed my integration with git (ssh keys) and after I ran File>Packages>Reset Package Caches everything started working. Not sure whether the package cache reset fixed it, but all is good. Until I just got my new 16 M1 MacBook pro. I did a time machine backup, restored to the new machine, and the same problem is back. Except that I can't get past the issue. The other Xcode source functions work (fetch, change branch, etc.) but no luck with authenticating to pull the packages. I don't consider myself a git guru - I prefer to use GitHub Desktop over the command line, but I use the command line when I need to. In Xcode File>Preferences>Accounts the GitHub account is set up there. So what am I missing? Any help appreciated.