Search results for

“missing package product”

52,398 results found

Post

Replies

Boosts

Views

Activity

Are read-only filesystems currently supported by FSKit?

I'm writing a read-only filesystem extension. I see that the documentation for loadResource(resource:options:replyHandler:) claims that the --rdonly option is supported, which suggests that this should be possible. However, I have never seen this option provided to my filesystem extension, even if I return usableButLimited as a probe result (where it doesn't mount at all - FB19241327) or pass the -r or -o rdonly options to the mount(8) command. Instead I see those options on the volume's activate call. But other than saving that readonly state (which, in my case, is always the case) and then throwing on all write-related calls I'm not sure how to actually mark the filesystem as read-only. Without such an indicator, the user is still offered the option to do things like trash items in Finder (although of course those operations do not succeed since I throw an EROFS error in the relevant calls). It also seems like the FSKit extensions that come with the system handle read-only strangely as well. For example, fo

App & System Services Core OS Files and Storage macOS FSKit

644

Transaction.currentEntitlements returning all transactions

[EDIT: Please ignore. Will delete in a second] Transaction.currentEntitlements is returning the complete history of transactions on a subscription product. I have a program with an In-App Purchase for a monthly subscription. I am testing with a local StoreKit file in Xcode. I configured the StoreKit test file to update every minute. When the program starts, I retrieve the current transactions from StoreKit to see if there is an active subscription. for await verificationResult in Transaction.currentEntitlements { guard case .verified(let transaction) = verificationResult else { continue } // update status for subscriptions This morning's testing is showing transactions for all transactions, both current and past. The current subscription renewal is sent plus all the past renewals that have expired. I thought in my previous testing that only one transaction (i.e., the latest/current) was sent per Product ID. Is this (all subscription transactions) the expected behavior, or should I file a bug

App & System Services StoreKit Subscriptions In-App Purchase

Reply to [Matter] Device cannot be commissioned to Google Home through iOS

is the issue fixed and may i know the root cause? Thank you This particular issue was determined to be an accessory failure, caused by the developer reducing the CHIP_IM_MAX_REPORTS_IN_FLIGHT constant from it's default value of 4 to 2. The difference between the working and failing cases where then caused by small differences pairing implementation, which then altered the report timing. I don't know why they original reduced that constant but, in general, altering this sort of constant in a hardware implementation is something I would recommend against. Part of the reason reference platforms exists is that, in practice, it's very difficult for platform and accessory implementors to create products the perfectly interoperate. Theoretically that's addressed by increasingly detailed specifications but anyone who's spent significant time reading a hardware specification knows that increased detail isn't necessarily all that helpful. Reference platforms help smooth out that process by providing a standard

App & System Services Hardware

Reply to QLThumbnailGenerator macOS 26.4 No Longer Honors Users 'Folder Color' Preference When Making Icons for Folders

A non-empty folder results in an icon with paper sticking out on macOS Tahoe but an empty folder doesn't have the paper sticking out. Interesting. I didn't realize that. However, it doesn't seem to always work. I just now figured out that if the folder has a . anywhere in the name, then it will display in the Finder as the old default, empty folder, even if it has contents. If you remove the . then it will add the paper. And Finder has its way of being exempt from all of this, natch! But of course! Edit: This is strange. There's some kind of heuristics in the Finder. You can put a . up towards the beginning of a folder name and it displays correctly. But if the . is towards the end, then it reverts to the default folder appearance, losing any modern folder customization. Ironically enough, adding a . doesn't affect the old folder icon customization method, which, from what I hear, is completely broken on Intel.

UI Frameworks AppKit

Reply to Enrollment frustration

after speaking on the phone, a support guy manually kicked off the email that gave me a link to https://developer.apple.com/contact/file-upload/upload/select to upload my ID, which I think was the missing step in the process. dunno if it'll work after that or not, but

Developer Tools & Services Apple Developer Program

Reply to Title: Clipboard manager rejected under Guideline 2.4.5 for using CGEvent.post — what is the correct approach?

There are two parts to this: Technical — What APIs are involved? And what TCC privileges do they need? App Review — What is or isn’t allowed on the App Store? I work for DTS, not App Review, so I’m only able to comment on the first part. I’ll come back to the second part at the end. From a technical standpoint, there are three TCC privileges involved: PostEvent — This controls the ability to post UI events, for example, by calling the CGEvent.post(tap:) method that you mentioned. ListenEvent — This controls the ability to monitor UI events on a system-wide basis, for example, with a CG event tap [1]. Accessibility — This is aimed at accessibility products, and controls a wide variety of things, including the ability to example the UI state of other apps. Note I’m using the service names that you would pass to tccutil, as explained in this post. These privileges are represented in System Settings > Privacy & Security, but in a non-obvious way: Both PostEvent and Accessibility map to Accessibili

App Store Distribution & Marketing App Review

Reply to Working Anti Virus - Apple Developer Account terminated

Hi, I read your post and it sounds like an incredibly tough situation. I’ve been through a Pending Termination Notice myself, so I truly understand how stressful this can be. I’d like to share my experience just in case it might be of some help. At this stage, it might be more effective to focus less on defending the anti-virus app’s innovation and more on protecting your developer account and your livelihood. In my own case, focusing on a few specific points in my appeal seemed to make a difference: Clarify your intent: Since the app was flagged as malicious, you might want to clearly explain that you had absolutely no intention of misleading users. While your personal situation (such as losing your source of income) is completely understandable, Apple’s review process is guideline-driven, so I think it might be more effective to keep the tone as professional as possible. Write a concrete preventative measure: I mentioned this in another thread recently, but I believe including a clear preventative

App Store Distribution & Marketing App Review

xcrun -v notarytool -> rc = 69

The following process to sign my .pkg installer for distribution outside the app store have been working for over a year and recently the notarization fails with a rc = 69. I not aware of any changes other then xtools updates for the latest macos 15.6.1. Admittedly I felt lucky to have gotten it all to work initially and I could really use help. Thanks in advance! Bill The signing (no errors): productsign --sign macos_cert myapp.pkg The notarization (rc=69): xcrun -v notarytool submit myapp.pkg --apple-id my_apple_id --team-id XXXXXXXXXX

Code Signing Notarization Developer Tools Notarization Signing Certificates

441

90919: Invalid entitlement error in ASC

I have an existing app in App Store Connect. I added the SharedWithYou functionality to the app code and tested it on several devices. Everything is working as expected. One of the first steps was to add the com.apple.developer.shared-with-you entitlement to the Entitlements.plist file. This required a round of updates for app identifiers and provisioning profiles. When I upload the production build for testing in TestFlight I receive the following error: 90919: Invalid entitlement. The “” bundle has the com.apple.developer.shared-with-you entitlement, but it doesn’t use the Shared with You framework. Please remove the entitlement and upload a new build. I'm using SWHighlight, SWHighlightCenter, and SWAttributionView in several places throughout my app... I filed an issue in the Feedback Assistant but so far, have not received any response.

Code Signing Entitlements Entitlements App Store Connect TestFlight Shared with You

355

Reply to test NEAppProxyProvider without MDM?

First up, have a read of TN3134 Network Extension provider deployment. This explains your deployment options for this technology. Specifically, for an app proxy on iOS the device must be managed. That’s because the MDM system is used to associate your app proxy with the apps that it proxies, by matching up the VPNUUID properties on both. During development you can use NETestAppMapping to establish this mapping. You’ll still need a configuration profile to enable your app proxy, because of the requirement to provide a VPNUUID property with the configuration. [quote='820572021, Davidbaraff2, /thread/820572, /profile/Davidbaraff2'] Is an app proxy the right tool for this? [/quote] Before you can answer that you have to first see if an app proxy will actually work. That is, in production: Are the target devices managed? Is the target app installed via MDM? If either of those is false, an app proxy won’t work and thus it’s definitely not the right tool (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer

App & System Services Networking

Reply to sysextd: "no policy, cannot allow apps outside /Applications" - NEFilterDataProvider system extension on macOS 26

It sounds like you’re using Developer ID signing for day-to-day development. That’s a mistake on multiple levels. I talk about this in general in The Care and Feeding of Developer ID, but there are extra issues with system extensions, where system policy requires that Developer ID signed sysexen be notarised. So my advice in this case. Use Apple Development code signing for day-to-day development. Use Developer ID for pre-release testing and distribution. There are a couple of key benefits with this approach: It lets you build and debug without enabling development mode, which is a big win IMO. Xcode’s automatic code signing works well with Apple Development signing. Even if you’re not using Xcode, you can create a small test project in Xcode, get it working, and then follow the same path it took. See Debugging a Network Extension Provider for specific advice on how to bring up a provider in Xcode. One thing that Xcode doesn’t handle is the -systemextension suffix )-: To learn more about that, read Exporting

App & System Services Networking

Apple Pay In-App Provisioning – HTTP 500 (HTML) on broker endpoint in production (TestFlight)

We are implementing Apple Pay In-App Provisioning (EV_ECC_v2) for our EU app. The same codebase and encryption logic works successfully for our main app (different bundle ID and Adam ID), but the EU app consistently fails with HTTP 500. Environment: Entitlement: Granted (Case-ID: 18772317) Encryption scheme: EV_ECC_v2 Issue: During In-App Provisioning, the iOS app successfully obtains certificates, generates cryptographic material (encryptedCardData, activationData, ephemeralPublicKey), and POSTs to Apple's broker endpoint. The request fails at: Endpoint: POST /broker/v4/devices/{SEID}/cards Response: HTTP 500 with an HTML error page (not a JSON business error) 500 Internal Server Error 500 Internal Server Error Apple Key observations: Our main app (different bundle ID/Adam ID) uses identical encryption code, private keys, and key alias — and works correctly in production. Manual card provisioning through Apple Wallet on the same device succeeds. The entitlement com.apple.developer.payment-pass-p

App & System Services Apple Pay Apple Pay

Reply to CKQuerySubscription on public database never triggers APNS push in Production environment

Hi Ziqiao, thanks for looking into this! I've verified using CKFetchSubscriptionsOperation.fetchAllSubscriptionsOperation() on both Development and Production (TestFlight) devices. All 5 subscriptions are present and correctly configured in both environments. The output is identical between both environments. Here are all 5 subscriptions as returned by CKFetchSubscriptionsOperation: fr-sub-v3 (FriendRequest) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=FRIEND_REQUEST_BODY, locArgs=[senderUsername] category=FRIEND_REQUEST, desiredKeys=[senderID, senderUsername] rec-sub-v3 (MediaRecommendation) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=RECOMMENDATION_BODY, locArgs=[senderUsername, mediaTitle] category=RECOMMENDATION, desiredKeys=[mediaTitle, mediaType, senderID, senderUsername] fs-a-sub-v3 (Friendship) Predicate: userAID == [userID] badge=true, sound=default, contentAvail=f

App & System Services iCloud & Data

Reply to Why don't my os_log entries show up until the second time my driver loads?

I'm in the process of writing a DriverKit USBHostInterface driver, and while I'm finally starting to get there, I've run into a bit of a frustration with logging. One unrelated question— what are you actually trying to do? More specifically, are you just doing vendor-specific communication or are you actually trying to integrate a USB device into the general system? It's gotten a bit lost by the introduction of DriverKit, but if you're only doing vendor-specific communication, you don't actually need a DEXT at all. The IOUSBHost Framework will do exactly what you need with a LOT less effort than DriverKit. Even if the system has a class driver that's getting in the way, a codeless DEXT will get that out of the way with minimal work. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

App & System Services Drivers

Reply to 3.2(f) triggered — account pending termination despite repeated attempts to comply

Thanks for the response, for context it was around 15 submissions over a few months and 30ish messages. I get your example, but I think my situation’s a bit different. The updates weren’t just micro changes trying to slip something through, there was a mix of both small tweaks and broader changes. The issue was the feedback stayed very generic (“overtly sexual”) without pointing to specific elements, so each update was essentially a best guess at what might be triggering it. Especially early on, when only metadata was flagged, I assumed the issue was relatively minor. By the end, I actually went in the opposite direction of evasion & submitted a build with everything unlocked and included screenshots showing all content upfront, so review had full visibility, as requested during a phone call. It’s possible I missed a couple of screenshots in earlier messages, but nothing was intentional. That’s why the 3.2(f) decision caught me off guard, there was no intent to hide or mislead, just trying to int

App Store Distribution & Marketing App Review