Search results for

missing package product

50,256 results found

Post

Replies

Boosts

Views

Activity

Reply to Unable to Staple Notarization Ticket – SSL Certificate Mismatch for oscdn.apple.com
Hello Apple Developer Support Team, I’m facing an issue stapling notarization tickets to my signed macOS installer package (.pkg). What I’ve done so far: Code-signed my .app with Developer ID certificate. Created a signed installer package (.pkg) using pkgbuild. Submitted the package to Apple notarization via xcrun notarytool submit ... --wait. Status: Accepted. Tried stapling using xcrun stapler staple -v IPMPlus_Arm_Installer_signed.pkg, but it fails with Error 65. xcrun stapler validate reports no ticket stapled. Observations: Curl tests to CloudKit endpoints return 404 or NOT_FOUND errors. Port 443 connectivity to api.apple-cloudkit.com and gs.apple.com works. Retried stapling from multiple networks, including a mobile hotspot. Same result. System time is synced; package signature is valid (pkgutil --check-signature). Questions: Is this a known issue with stapler / CloudKit endpoints? Is there a workaround to successfully staple a notarization ticket t
Topic: Code Signing SubTopic: Notarization Tags:
1w
HKObserverQuery and BackgroundDelivery Are Highly Unstable on watchOS 26
We are developing a health app that relies on HKObserverQuery and BackgroundDelivery to monitor Heart Rate data. On watchOS 10.6 and 11.6 , these data updates are typically delivered reliably every 8–12 minutes, occasionally exceeding 12 minutes, but generally not longer than 15 minutes. This frequency has been sufficient for the real-time data requirements of our app. However, after adapting our app to watchOS 26, we noticed that HKObserverQuery triggers much less frequently, with longer and very inconsistent intervals. This issue has had a major impact on our product: data collection for essential features is unreliable, resulting in a greatly diminished user experience on watchOS 26 and making the app essentially useless from the user’s perspective. Observed Behavior: HKObserverQuery and BackgroundDelivery are extremely unstable, with trigger intervals frequently exceeding 15 minutes, and sometimes even 20 minutes. When the user is sedentary, intervals become even longer; there are cases where no
2
0
140
1w
Reply to How to print WKWebView in Sequoia?
I swapped out my old deprecated code for the new WKWebView code similar to what you're using. It was surprisingly easy. It does require macOS 11. And I lose my custom headers and footers. But otherwise, it works fine. In my code, I'm using fit pagination for both horizontal and vertical. I think that may fix your ridiculously tall pages. Safari also generates such pages when exporting to PDF, so perhaps automatic is what's doing that. Otherwise, I have a document-based app and I don't call runModal on the print operation. As I said above, I'm using NSDocument's printDocumentWithSettings:... after the web view has completely loaded.
Topic: App & System Services SubTopic: Core OS Tags:
1w
FTDI USB-serial driver on iPadOS
Hello, We have developed a hardware product that embeds an FTDI USB-serial converter, and an application on MacOS that communicates with this device. We would like to port our application to iPadOS. I can see that when I plug the device into the iPad, it is recognized as a serial port, based on its console logs. When I attempt to enumerate serial ports on iPadOS using IOKit, I can see matching IOSerialBSDClient services, but the properties are sandboxed, including the IOCalloutDevice property, for example: 0 error 16:36:10.922450-0700 kernel Sandbox: ***(662) deny(1) iokit-get-properties iokit-class:IOUserSerial property:IOTTYSuffix Is there an entitlement that can be applied that allows access to the serial port properties of an attached USB device? Or do I need to implement my own USBDriverKit driver for this device, as seems to be implied in these forum threads: https://developer.apple.com/forums/thread/795202 https://developer.apple.com/forums/thread/655527
1
0
58
1w
Keychain and Local Data Loss After App Transfer Between Developer Accounts
Hello everyone, We recently transferred our iOS app from one Apple Developer account to another, and after the transfer, we encountered a serious issue where all previously stored Keychain data and the local database became inaccessible. As a result, all users are automatically logged out and lose access to their locally stored data (such as chat history) once they update to the new version signed with the new Team ID. We understand that Keychain items are tied to the App ID prefix (Team ID), which changes during an app transfer. However, we’re looking for possible workarounds or best practices to avoid user data loss. Questions: Is there any reliable method to maintain or migrate access to old Keychain data after an app transfer? Would reverting the app back to the original developer account and releasing an update from there (to persist or migrate data) before transferring it again be a viable solution? Has anyone faced a similar issue and found a practical way to handle data persistence d
1
0
96
1w
Reply to Example of DNS Proxy Provider Network Extension
[quote='861238022, GlacierSec, /thread/802691?answerId=861238022#861238022, /profile/GlacierSec'] So then it seems we would have to implement DNS Proxy to do what we want? [/quote] I don’t think that’ll actually work. Because of the DNS proxy deployment limitations [1], the ability to modify the proxy configuration is limited to development-signed apps. Once you sign your app for distribution, it’ll lose its ability to modify its DNS proxy configurations. Rather, the site admin is expected to configure the proxy using MDM payloads. Or at least that’s how it works with content filters. I can’t remember whether I’ve ever actually tested this with DNS proxies. However, both occupy a similarly privileged networking position and so I expect them to follow the same rules. A DNS proxy can (more or less) go into pass through mode by leaning in to the systemDNSSettings property. [quote='861238022, GlacierSec, /thread/802691?answerId=861238022#861238022, /profile/GlacierSec'] Or do you have other thoughts now
1w
Reply to "Application damaged and can't be opened' error prompt on 15.6.1 Sequoia
[quote='861351022, oddeyed, /thread/799110?answerId=861351022#861351022, /profile/oddeyed'] Yes, that is correct. [/quote] OK. That certainly does raise a world of possibilities. The approach I usually recommend for incremental Apple installers is to copy the app and then update the copy. See this post. However, I don’t think that’s feasible for an installer package, and I’m not 100% sure what the best option here is. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: General Tags:
1w
security add-trusted-cert asks password twice in some cases: The authorization was denied since no user interaction was possible
Hey devs, I have a really weird issue and at this point I cannot determine is it a Big Sur 11.1 or M1 issue or just some macOS settings issue. Short description programatically (from node, electron) I'd like to store x509 cert to keychain. I got the following error message: SecTrustSettingsSetTrustSettings: The authorization was denied since no user interaction was possible. (1) I could reproduce this issue on: a brand new mac mini with M1 chip and Big Sur 11.1 another brand new mac mini with M1 chip and Big Sur 11.1 a 2018 MacBook pro with Intel chip and Big Sur 11.1 I couldn't reproduce this issue on: 2020 MacBook pro with intel i9 chip and Big Sur 11.1 2020 MacBook pro with intel i9 chip and Big Sur 11.0 How am I trying to store the cert node test.js test.js const { exec } = require('child_process') exec( t`osascript -e 'do shell script security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain /Users/kotapeter/ssl/testsite.local.crt with prompt Test APP wants to store SSL certificatio
14
0
19k
1w
Resolving Tap to Pay on iPhone errors when building for App Store or TestFlight distribution
I am receiving an entitlement error from stripe terminal SDK when integrating Tap to Pay from apple in the info.plist. Im hoping that someone can give me their input on my error output rather than diving into the stripe sdk to point me in the right direction of something I may have missed with entitlements. I have been approved for tap to pay entitlement and am following the instructions here from apple: https://developer.apple.com/documentation/proximityreader/setting-up-the-entitlement-for-tap-to-pay-on-iphone com.apple.developer.proximity-reader.tap-to-pay
3
0
300
1w
Reply to Regression: Associated domain on NFC tag or through control does not open app
Every team works differently, but you would not necessarily get an acknowledgement for your feedback reports unless there is missing information they will ask for, or they might ask you to test and verify a fix or a change. That said, your Feedback report is open and being investigated. There is nothing much to report at this time. You can always check the status of your Feedback via the Feedback Assistant.
Topic: App & System Services SubTopic: Core OS Tags:
1w