Search results for

missing package product

51,072 results found

Post

Replies

Boosts

Views

Activity

Reply to InApp purchase and testing
Hello, I've made all the steps as the author did and I do not get any products. I'm using react-native with expo-in-app-purchases package. Product IDs from App Store Connect are 1000credits, 2200credits and 6000credits. ... const { responseCode, results } = await InAppPurchases.getProductsAsync(['1000credits', '2200credits', '6000credits']) console.log(responseCode, responseCode); console.log(results, results); ... responseCode: 0 results: [ ] I tried to enter products using bundle identifier com.xxx.1000credits or com.xxx.xxx.1000credits as well and I have the same problem.
Topic: App & System Services SubTopic: StoreKit Tags:
Jul ’20
Reply to Code Sign PKG file error "this identity cannot be used"
When I do that I get the error: Developer ID Installer: XYZ123: this identity cannot be used for signing code Right. That error is correct, but misleading. You have two signing identities: A code signing identity, Developer ID Application: TTT An installer signing identity, Developer ID Installer: TTT You use the first for signing code (and disk images) and the second for signing installer packages. If you attempt to cross the streams, bad things will happen. The issue here is that you’re trying to signing your installer package as if it were code. This will actually work [1] but it won’t produce anything useful. It’ll create an installer package that’s code signed, rather than an installer package that’s installer signed. To sign an installer package, use productsign. For general advice on how to package Mac products for distribution, see Packaging Mac Software for Distribution. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical
Topic: App & System Services SubTopic: Core OS Tags:
Aug ’22
My .pkg is being rejected after notarize it
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.
3
0
729
Apr ’20
Reply to TFOD on M1 Mac
I got the TensorFlow object detection tutorial page (https://www.tensorflow.org/hub/tutorials/tf2_object_detection) running. I had successfully installed tensorflow-macos and tensor flow-metal before, so that I could do already the image classification task shown on the TensorFlow hub site, but object detection was not possible for me as the installation mentioned on TensorFlow hub did not work. Initially I was struggling with the cell containing the installation of the object_detection-package, mainly because of missing packages or package conflicts. I mean this piece of code: %%bash sudo apt install -y protobuf-compiler cd models/research/ protoc object_detection/protos/*.proto --python_out=. cp object_detection/packages/tf2/setup.py . python -m pip install . The failure always occurred with the last line. I could overcome them with the following steps (as it was a longer trial and error I hope I don't miss any steps): The missing tensor flow-te
Topic: App & System Services SubTopic: Core OS Tags:
Apr ’22
Swift Packages + Module Stability
Hi! Support for binary dependencies in Xcode 12.0 is really a great addition to the whole ecosystem built around Swift Package Manager. Last year we learned that the non-binarySwift Packages don't work well with the module stable frameworks. Is there a plan to add a module stability to open-source Swift Packages, too? In a way that closed-source binaries could depend on open-source Swift Packages? Thanks!
0
0
622
Jun ’20
SKProductRequest return 0 product with production-signed app
Hi,I have an iOS application which uses in-app purchases.I have already set the environment for IAP:Set all the Agreements Tax and Banking sections,Created IAP products on iTunes connectTurned on In app purchases in the capabilities tabImplemented my code to retrieve the product list and to perform a purchase validating the receipt server-sideI have also tested all with a sandbox environment and all works as expected: the list of products is correctly received by the store I can purchase a product validating the corresponding receipt.I have also tested the application using Testflight which creates automatically a sandbox user for all testers and all works as expected.I submitted my application to the Apple store and the revision has been passed so that at the moment the application is in Pending Developer Release status, all the products have been approved.In order to try an actual purchase (using a real credit card) I have generated a promo code with iTunes conne
2
0
1.5k
Nov ’18
Failing in Notarization a pkg file
I have a flattened pkg file to notarize. It is signed at the build time by the Developer ID installer. Here is the output of a series of commands. check notarization status submit notarization and status check tatus of notarization after notarization complete. mtnview@C02YC2G0JGH5 ~/D/s/d/h/c/pkgs>spctl -a -vvv -t install ./foo.mac11.x86_64.pkg ./foo.mac11.x86_64.pkg: rejected source=Unnotarized Developer ID origin=Developer ID Installer: foo, Inc. (69Q4FM6AL9) mtnview@C02YC2G0JGH5 ~/D/s/d/h/c/pkgs> xcrun notarytool submit ./foo.mac11.x86_64.pkg --keychain-profile AC_PASSWORD --wait Conducting pre-submission checks for foo.mac11.x86_64.pkg and initiating connection to the Apple notary service... Submission ID received id: cc2d06be-fb07-4794-a92a-996ac07985fd Successfully uploaded file id: cc2d06be-fb07-4794-a92a-996ac07985fd path: /Users/mtnview/Documents/shared_vm/dev/hawkeye/cmake-macos/pkgs/foo.mac11.x86_64.pkg Waiting f
5
0
1.3k
Mar ’22
Reply to Problem using test plans with local Swift Packages
I was able to resolve this. As far as I can tell, it's an Xcode bug.The short version is that Xcode seems to assume that at least one test configuration will use the shared (default) test configuration, unmodified. That assumption can of course be wrong; it's possible that no test configuration exactly matches the defaults. The mistake can prevent Xcode from finding the test target bundles for local Swift Packages.The long version...* A test plan has a shared (default) test configuration.* A test plan has one or more actual test configurations.* Xcode places build products in directories whose names are based on their differences from the shared (default) configuration.* The build products for test configurations that don't have any meaningful differences are placed under the root, e.g.: /Products/xxx/....* The build products for test configurations that do have meaningful differences are placed under subirectories whose names are derived from the differences, e.g.: /Products
May ’20
notarization: ".pkg could not be extracted."
Hi, after a software update of our previously successfully notarizated installion .pkg we now receive a cryptic notarization issue refusing the entire .pkg: { logFormatVersion: 1, jobId: 5cff2d71-7228-4fb4-a39d-329084cd2713, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: my_installer.pkg.zip, uploadDate: 2024-12-04T23:17:14.016Z, sha256: 2f26d0376506abe130ac904d7cb0d0cd5428666624428da9f44da7756352844f, ticketContents: null, issues: [ { severity: error, code: null, path: my_installer.pkg.zip, message: Package my_installer.pkg.zip has no signed executables or bundles. No tickets can be generated., docUrl: null, architecture: null }, { severity: warning, code: null, path: my_installer.pkg.zip/my_installer.pkg, message: The contents of the package at my_installer.pkg.zip/my_installer.pkg could not be extracted., docUrl: null, architecture: null } ] } What could be the reason for that? We've also submitted the .pkg
3
0
560
Dec ’24
Renaming notarized ZIP packages
Dear support team, is it possible to rename a notarized ZIP package and not to loose the notarized status? One of our ZIP package contains resources and binaries which are code signed. The archive itself is accepted after submitting and uploading during the notarization process (online notarization). Unfortunately, the ZIP cannot be stapled (offline verification). So, is the filename part of the notarized ZIP package or can a ZIP package be renamed? Best regards, Stefan
1
0
212
1w
the package was signed with a certificate that has expired
I am very new to this, so apologies if this is a noob question. I am creating a package using Packages. I have a Developer ID certificate that expires in 2027. If I set my project to use that certificate before building in Packages, the build fails. So I am certifying after using terminal. However, in both the Terminal certification and running the installer for my .pkg, it says that the certificate is expired. I don't understand how a certificate that expires in 2027 can already be expired. Any ideas out there? I found a post with the same problem from 7 years ago and there were no responses. Thanks all!
1
0
930
Jan ’23
Xcode Export Localizations for an iOS app using Swift Package Manager packages fails: No such module UIKit
I'm building an iOS app (the supported destinations in the app target are iOS, iPad and Mac - Designed for iPad). I've many SPM frameworks in order to split my codebase in different features. I want to export the localisations for the different packages and the app using Xcode but it fails. I followed the Apple guide regarding SPM localization: the packages contains a Resources folder with a folder for each language supported. I specified the platforms .iOS(.v16) in the packages. But it seems that exporting the localisations using the Product > Export Localizations feature in Xcode compiles also the packages and app for macOS. Here is the error message: Showing Recent Messages /Users/axel/Developer/AppName/Packages/Helpers/Sources/Helpers/UIKit/UIImage+Extension.swift:7:14: No such module 'UIKit' /Users/axel/Developer/AppName/Packages/Helpers/Sources/Helpers/UIKit/UIImage+Extension.swift:7:14: UIKit is not available when building for macOS. Con
2
0
2.2k
Feb ’23
Reply to Discontinuing consumable IAP Products
1) Under Apple guidelines, what are our obligations to support Product A (a consumable IAP) in Version Y?I don't believe Apple guidelines speak to this issue. Your users who still have a quantity of Product A will be disappointed. Is there any way you could allow the new version to continue using already purchased Product A but not be able to buy any more?2) What happens if someone updates from Version X to Y and tries to restore? Is that a scenario we have to support (unconsumed Product A’s)? No, you cannot restore a consumable IAP. But when you update the app you don't lose any files so there is no reason why the consumable should disappear if it was retained in a file (e.g. NSUserDefault). If the user deleted the app and then reinstalls (the new or the old version) then they lose all consumable IAPs and would need to repurchase. That's common practice.
Topic: App & System Services SubTopic: StoreKit Tags:
Sep ’17