Search results for

“missing package product”

52,926 results found

Post

Replies

Boosts

Views

Activity

Reply to Having a hard time notarizing a pkg.
It looks like you’re signing your package as code. That won’t work. You need to sign it as a package. My Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166 post has the relevant instructions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Aug ’20
How do i expand payload of 3rd party package?
Hi, I'm trying to notarise package file of our product. Notarization is success with some warnings on 3rd party package file. I see two executables in the 3rd party package file is not code signed properly. I need to expand, sign those binaries and flatten it again and include into our package file. I'm able to expand the 3rd party package file using the below command: pkgutil --expand directory name Now i'm able to see files of the above package file. But how do i expand pay-load files?
Topic: Developer Tools & Services SubTopic: General Tags:
1
0
1.3k
Oct ’19
Reply to In-App Purchases: Products vs Tiers
First, you don't need a different product for each country. You can localize the description. Second, yes, you can have only one 'product' at each price point and let the app describe the product. But then you lose some flexibility in being able to change the price of a product. You could have your app reference your website to get the description if that is an issue.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Jul ’16
Reply to EAS build works in Expo Go & Simulator, TestFlight app crashes on open
Solved this one myself, but for anyone experiencing an operator() crash, be sure to read through the react navigation docs, then find exactly which part of react navigation you used (ie. Stack, Drawer, etc) as there can be some additional packages to add to ensure it runs cleanly on TestFlight. My problem was one missing package that needed to be added.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Jul ’22
Storekit2 Fetch Products
I have more than 230 in app products which is Consumable, Non-Consumable & Auto Renewable subscription, So while Initialise Inapp products in storekit2 let productIds = [...your 300 identifiers...] let products = try await Product.products(for: productIds) I am getting repose only few products few missing in TestFlight build, So how to resolve this issue, it happen in only TestFlight or App Store its working?
Topic: App Store Distribution & Marketing SubTopic: General
0
0
106
May ’25
Reply to SMJobBless privileged helpers and granting permission
Thanks Quinn, Sorry, yes, my sloppy terminology of The Finder which I often use for unattached dialogs the user sees. I did not know this about the Full Disk Access being different so my experiments with plists for the priviledge helper need to be redone. One of the operations my helper is doing that needs Full Disk Access is downloading a pkg and checking it is signed. None of the normal security api's appear to work with pkg's, maybe I missed something there, I can check apps and so forth on disk. So I end up running /usr/sbin/pkgutil --check-signature instead as I could not figure out how pkgutil is implemented. Did I miss something in the security api, should I be able to look at a pkg's validity?
Topic: Privacy & Security SubTopic: General Tags:
Apr ’22
Reply to Xcode 11 how to work with .crash files?
Not sure how viewing crashes in Xcode is supposed to work either. Wasn't able to find anything useful when clicking Open in Project.For me, a couple of times I noticed vital information was missing when viewing the crash in Xcode (missing method calls on the stack but they were in the .crash log). So I right-clicked on the crash in the list on the left and choose Show in Finder which reveals a package with .xccrashpoint in Finder. I then right clicked that .xccrashpoint package in Finder and choose Show Package Contents and then dug through subfolders until I got to the Log folder with the .crash files in it. Then I just opened the .crash in Console. Reading the .crash in Console was a lot more useful. Was able to determine what caused the app to crash and was able to fix it in an update.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Mar ’20
This package is incompatible
This package is incompatible with this version of OS X and may fail to install.Heads up for anyone who makes packages. If you write to SIP protected locations, (even symlinks) you will get this warning.Example:Writing to /var - badWriting to /private/var - goodFrom now on it might be ideal to write to the full path as these are not SIP protected./private/etc/private/tmp/private/var
Topic: App & System Services SubTopic: Core OS Tags:
0
0
2.2k
Jun ’15
Reply to Notarization fails for flat installer package containing notarized app
You’re building your installer package using a third-party tool. Does the problem reproduce if you build it using Apple’s tools? You don’t need to build something production ready here; just use our tools to create a package you can test against the notary service. There’s a simple command for doing that in Packaging Mac Software for Distribution. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Feb ’23
Problem with swift package manager caching and binary package
I've setup my Xcode project to use a binary package, for which the manifest is stored in the private git repository. The dependency tracking is set to branch -- it just fetches the manifest from master branch of the repository. It seems, that after initial fetching Xcode or spm caches the commit hash used to fetch the manifest. If I push an update of Package.swift (i.e. containing updated artifact checksum) this change is not refreshed in the project (i.e. after resetting package cache it complains about the checksum mismatch between the actual binary artifact and the manifest). At the same time if I manually clone the repository I see valid checksum in the manifest. I've tried to use all 3 options in Xcode (i.e. reset package cache, resolve package versions, update to newest version). None of them solves the problem. It seems that to reset the cache I need to remove the package from the project and add it again. I'm looking for an elegant way to refresh the manife
Topic: Developer Tools & Services SubTopic: Xcode Tags:
1
0
2.2k
Sep ’22
Reply to Having a hard time notarizing a pkg.
It looks like you’re signing your package as code. That won’t work. You need to sign it as a package. My Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166 post has the relevant instructions. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Aug ’20
Reply to Swift Package that has `@objc` in Swift code can’t be used due to Objective-C module failure
Let me add extra observations here as well, Swift JIRA is also updated. This is caused by missing -Xcc -module-map-file for swift -frontend for the transitive Swift package dependency used for the Swift files in the application target. This is not happening if the module that Swift Package provided is written in Objective-C.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jun ’20
How do i expand payload of 3rd party package?
Hi, I'm trying to notarise package file of our product. Notarization is success with some warnings on 3rd party package file. I see two executables in the 3rd party package file is not code signed properly. I need to expand, sign those binaries and flatten it again and include into our package file. I'm able to expand the 3rd party package file using the below command: pkgutil --expand directory name Now i'm able to see files of the above package file. But how do i expand pay-load files?
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
1
Boosts
0
Views
1.3k
Activity
Oct ’19
Reply to In-App Purchases: Products vs Tiers
First, you don't need a different product for each country. You can localize the description. Second, yes, you can have only one 'product' at each price point and let the app describe the product. But then you lose some flexibility in being able to change the price of a product. You could have your app reference your website to get the description if that is an issue.
Topic: App Store Distribution & Marketing SubTopic: App Review Tags:
Replies
Boosts
Views
Activity
Jul ’16
Reply to Swift Package can be MAKE_MERGEABLE?
This is not a solution. it failed at the build time with error: The package product 'MyPackage' cannot be used as a dependency of this target because it uses unsafe build flags.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Dec ’23
Reply to Error while generating a DocC based documentation for a Swift Package
This sounds like it may be a general Swift Package Manager dependency resolution issue. If you see the same error when you try to build from the command-line using: $ swift build --product InternalFramework then I would recommend either opening an issue on the open-source Swift Package Manager repository or filing a Feedback.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to EAS build works in Expo Go & Simulator, TestFlight app crashes on open
Solved this one myself, but for anyone experiencing an operator() crash, be sure to read through the react navigation docs, then find exactly which part of react navigation you used (ie. Stack, Drawer, etc) as there can be some additional packages to add to ensure it runs cleanly on TestFlight. My problem was one missing package that needed to be added.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
Boosts
Views
Activity
Jul ’22
Storekit2 Fetch Products
I have more than 230 in app products which is Consumable, Non-Consumable & Auto Renewable subscription, So while Initialise Inapp products in storekit2 let productIds = [...your 300 identifiers...] let products = try await Product.products(for: productIds) I am getting repose only few products few missing in TestFlight build, So how to resolve this issue, it happen in only TestFlight or App Store its working?
Topic: App Store Distribution & Marketing SubTopic: General
Replies
0
Boosts
0
Views
106
Activity
May ’25
Reply to SMJobBless privileged helpers and granting permission
Thanks Quinn, Sorry, yes, my sloppy terminology of The Finder which I often use for unattached dialogs the user sees. I did not know this about the Full Disk Access being different so my experiments with plists for the priviledge helper need to be redone. One of the operations my helper is doing that needs Full Disk Access is downloading a pkg and checking it is signed. None of the normal security api's appear to work with pkg's, maybe I missed something there, I can check apps and so forth on disk. So I end up running /usr/sbin/pkgutil --check-signature instead as I could not figure out how pkgutil is implemented. Did I miss something in the security api, should I be able to look at a pkg's validity?
Topic: Privacy & Security SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’22
Reply to Testflight down
My issue has been solved. A new installed package make the microphone on as default and I have to add NSMicrophoneUsageDescription in my info.plist. Some mails from app store has pointed out the problem but I missed them.
Topic: App Store Distribution & Marketing SubTopic: TestFlight Tags:
Replies
Boosts
Views
Activity
Oct ’24
Reply to Xcode 11 how to work with .crash files?
Not sure how viewing crashes in Xcode is supposed to work either. Wasn't able to find anything useful when clicking Open in Project.For me, a couple of times I noticed vital information was missing when viewing the crash in Xcode (missing method calls on the stack but they were in the .crash log). So I right-clicked on the crash in the list on the left and choose Show in Finder which reveals a package with .xccrashpoint in Finder. I then right clicked that .xccrashpoint package in Finder and choose Show Package Contents and then dug through subfolders until I got to the Log folder with the .crash files in it. Then I just opened the .crash in Console. Reading the .crash in Console was a lot more useful. Was able to determine what caused the app to crash and was able to fix it in an update.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Mar ’20
This package is incompatible
This package is incompatible with this version of OS X and may fail to install.Heads up for anyone who makes packages. If you write to SIP protected locations, (even symlinks) you will get this warning.Example:Writing to /var - badWriting to /private/var - goodFrom now on it might be ideal to write to the full path as these are not SIP protected./private/etc/private/tmp/private/var
Topic: App & System Services SubTopic: Core OS Tags:
Replies
0
Boosts
0
Views
2.2k
Activity
Jun ’15
Reply to Notarization fails for flat installer package containing notarized app
You’re building your installer package using a third-party tool. Does the problem reproduce if you build it using Apple’s tools? You don’t need to build something production ready here; just use our tools to create a package you can test against the notary service. There’s a simple command for doing that in Packaging Mac Software for Distribution. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Feb ’23
Problem with swift package manager caching and binary package
I've setup my Xcode project to use a binary package, for which the manifest is stored in the private git repository. The dependency tracking is set to branch -- it just fetches the manifest from master branch of the repository. It seems, that after initial fetching Xcode or spm caches the commit hash used to fetch the manifest. If I push an update of Package.swift (i.e. containing updated artifact checksum) this change is not refreshed in the project (i.e. after resetting package cache it complains about the checksum mismatch between the actual binary artifact and the manifest). At the same time if I manually clone the repository I see valid checksum in the manifest. I've tried to use all 3 options in Xcode (i.e. reset package cache, resolve package versions, update to newest version). None of them solves the problem. It seems that to reset the cache I need to remove the package from the project and add it again. I'm looking for an elegant way to refresh the manife
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
1
Boosts
0
Views
2.2k
Activity
Sep ’22
Reply to ios14 "Notifications are not allowed" ERR
In my case, Build Settings - Packaging - Product Name was not English. Changed to English and worked. It was okay to set the name in other languages in iOS 13 though.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Sep ’20