file uri scheme

Thanks for the post. Thank you for providing a screen recording and a focused sample of the bug filed. Your assistance is greatly appreciated. I believe this could be a bug, but please provide the engineering team with the opportunity to review your submission. They will communicate with you through the feedback assistant application. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

Thank you for your reply. Unfortunately, creating a package using productbuild results in the same zero-byte file written to /Applications. I used the command: productbuild --sign --component /Applications Interestingly, if my coworker creates the application on his machine, I can then use his application in my pkgbuild script and the installation succeeds. Both his application and the application I build on my machine are signed with the same company Developer ID Application and are notarized. Both applications also run on my machine and have the same functionality, as their source was pulled from the same branch. We are both using XCode 16.2. This problem only started to happen on my machine last week. Does the pkgbuild command have a cache that can be deleted? Thank you for your time.

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Thanks for the reply. I didn't see it personally however, can you file a bug including all the versions you are using to reproduce it? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

Hey @bradley_7, The 'init' for 'AVCaptureExternalDisplayConfigurator' refers to the CALayer as 'previewLayer'. Does it work on any CALayer or does it need to specifically be a need to be a 'AVCaptureVideoPreviewLayer'? As noted in the previewLayer property docs: You may specify either an AVCaptureVideoPreviewLayer or another CALayer instance that displays a camera’s video preview. When I call it like this the app crashes: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[AVCaptureExternalDisplayConfigurator initWithDevice:previewLayer:configuration:] shouldMatchFrameRate is not supported' It's unclear why this crash is occuring, is it because the CALayer is not a 'AVCaptureVideoPreviewLayer'? That exception is being thrown because isMatchingFrameRateSupported is reporting false for your external display, but your AVCaptureExternalDisplayConfiguration specified true for shouldMatchFrameRate. Also, in the past I have done extensive testing with 'AVCaptureVideoPreviewLaye

If you'd like Apple to consider adding the functionality you have described, please file an enhancement request using the Feedback Assistant. If you file the request, please post the Feedback number here. In this case since you have suggested a number of separate ideas I recommend filing a separate enhancement request for each one instead of lumping them all into one. That way each can be considered separately. Also, please review Apple's Unsolicited Idea Submission Policy. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

Hi Albert, thanks for the response. The Avenir Next font is included in iOS since forever (iOS 6?), so no need to declare it using the UIAppFonts key. I tried configureWithOpaqueBackground, it didn't make a difference. I've file FB21291879 and have attached a small demo project and screenshots there. It's pretty simple: use a default UITabBar and in viewDidLoad, change the appearance: self.tabBar.standardAppearance.compactInlineLayoutAppearance.normal.titleTextAttributes = [ .font: UIFont(name: AvenirNext-DemiBold, size: 28.0)! ] Run it on iOS 26.0. or 26.1 and the tab bar renders with a large font. Run it on iOS 26.2 and the font is a small San Francisco.

Bummer. In that case my advice is that you file an enhancement request against App Store Connect help asking for that RSS feedback. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868482022, Apple_Fox, /thread/807599?answerId=868482022#868482022, /profile/Apple_Fox'] Is SharePoint a server one that would cause issues with downloading docx files directly? [/quote] I expect that’ll depend on how the server is configured. I recommend that you write a small test project to fetch the URL and see what you get back. Usually this yields one of three results: The request succeeds with a 2xx status code and returns the right data. The request fails with a 4xx status code, indicating that you have to log in. In this case you may be able to gets things working using the authentication challenge mechanism in URLSession. The request success with a 2xx status code but the actual data is a login page. This is hard to deal with. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] I already feel bad asking you again [/quote] No worries. It gives me a good excuse to brush up on my debugging skills (-: [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. [/quote] Bah. This isn’t super surprising, and it’s the sort of thing I’d know if I had an iPhone 17 to play with. It’s definitely time to ping my boss about that. [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] Unfortunately, I didn't really understand where/what to look for in Xcode. [/quote] OK. Lemme run you through a non-MTE example: Using Xcode 26.1 on macOS 15.7.1, I created an iOS app with two buttons wired up to these two methods: var memory: UnsafeMutableRawPointer? = nil func mallocAction() { self.memory = malloc(1024) } func freeAction() { free(self.memory) } In the scheme editor,

You can find my general advice for problems like this in Investigating Third-Party IDE Code-Signing Problems. But I also want to address this specific point: [quote='809448021, nickblair, /thread/809448, /profile/nickblair'] I can create an ipa file with vs using the wildcard bundle identifier [/quote] There’s no such thing as a “wildcard bundle identifier”. A bundle ID is always explicit. If you’re trying to use a * in your bundle ID, stuff is not going to work. There is such a thing as a wildcard App ID, but App IDs and bundle IDs are not the same same thing. An App ID is a key input to a provisioning profile; it determines the apps to which that profile applies. I talk about this more in TN3125 Inside Code Signing: Provisioning Profiles. A wildcard App ID creates a wildcard provisioning profile that authorises execution of all App IDs that match the pattern. However, each app’s bundle ID, and hence its App ID, must be explicit. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @

The first error in that list is the most significant. In the App Clip view of the universe, every App Clip has a parent app, that is, the app in which it’s embedded. Xcode is having problems figuring out the App ID of that parent app, and things go wrong from there. If you create a new app from the built-in iOS > App template and then create a new App Clip target within that, you’ll see that Xcode creates a .entitlements file for the App Clip that lists the parent app in the com.apple.developer.parent-application-identifiers entitlement. I recommend that you check that that’s set up correctly in your real project. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com