xcode github

You are not being overly paranoid here. Supply chain attacks are real. I see two parts to this: Making sure you got the right framework. Signing your final product. I’m gonna tackle them in reverse order. Imagine an app that, under rare circumstances, erases all the users files. If that happens to a user, they’re not going to be satisfied by the app vendor saying “I got that code from some other vendor.” So, regardless of the legal side of this — and I’m not a lawyer and thus can’t comment on that — it’s clear that, from a reputation standpoint, you are responsible for all the code you ship. How that’s reflected in code signing depends on your deployment channel: For App Store apps, all code in the app must be signed by your Apple Distribution signing identity. So, yep, you will have to re-sign this framework before submitting it [1]. For a directly distributed app, using Developer ID signing, it is possible to include a framework that was Developer ID signed by another developer. Such an app will be accepted

What platform are you developing for? This matters because there are important platform-specific differences between iOS (and its ‘child’ platforms) and macOS when it comes to NE. Also, I have some general advice on how to debug problems like this in Debugging a Network Extension Provider. I recommend that you start there and then, if you aren’t able to fix things, come back here with your latest results. [quote='799336021, QuentinIQ, /thread/799336, /profile/QuentinIQ'] It's not entirely clear what kind of executable the network extension is meant to be … [/quote] Network Extensions providers are packaged as either an app extension or a system extension, depending on the platform and distribution channel. TN3134 Network Extension provider deployment shows all the options. If you’re using Xcode, create your NE target from the appropriate target template, for example, choose File > New > New Target and then select iOS > Network Extension. Xcode will then do the right thing. If you’re

Currently on Xcode 26.0 beta 7 (17A5305k), macOS 15.6.1 (24G90) For our main Phonepe app (https://apps.apple.com/in/app/phonepe-secure-payments-app/id1170055821) dSYM size went from 281 MB (xcode-16) to 584 MB (xcode-26) Tried replicating the issue for Alamofire Example app (https://github.com/Alamofire/Alamofire), there as well dSYM size went from 2.7 MB (xcode-16) to 5.8 MB (xcode-26). All Build were all release builds

I didn't file the following as I'm not sure if it is correct flow or not: on macOS: run the attached app in Xcode tap Pick File and select a file set withSecurityScope=on in the UI tap Create bookmark - that fails That flow works fine for me. What error are you getting? And what file are you picking? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

I didn't file the following as I'm not sure if it is correct flow or not: on macOS: run the attached app in Xcode tap Pick File and select a file set withSecurityScope=on in the UI tap Create bookmark - that fails

My question at this point is whether there's this other bug on macOS worth filing that when creating a bookmark with withSecurityScope=on option I'm getting an error. Very easy to demonstrate using my test bench. The flows have gotten a bit confused so, making this explicit, the failure here: on macOS: run the attached app in Xcode tap Pick File and select a file tap Stop Access set withSecurityScope=on tap Create bookmark - that succeeds Create fails with error. ...is expected behavior. Your app released it's access at #4, so it's no longer allowed to make a bookmark. __ Kevin Elliott DTS Engineer, CoreOS/Hardware