eskimo

Please post a full Apple crash report, per the advice in Posting a Crash Report. Also, is this crash new in iOS 26.2? Or did you see it on earlier releases as well? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

In general, I recommend that you escalate questions like this via the support channel for the third-party tools you’re using. In this case, however, I have some suggestion before you do that, all related to this: [quote='812438021, lucksp, /thread/812438, /profile/lucksp'] For this new project, however, I am not the owner. [/quote] First, check that this team is an Organization team. If it’s an Individual team, you’ll like run into problems per the note at the top of the Permissions in App Store Connect section of Developer > Program Roles. Assuming this is an Organization (or Enterprise) team, the next step is to ensure that your operation is compatible with your program role. See the big table at the top of Developer > Support > Articles > Program Roles. Finally, try to do an equivalent operation on the Developer website itself. If that fails, you can seek help via Apple > Developer > Contact Us. But if that works, this is something for your tools vendor to investigate. Share and Enjoy — Q

Thanks for filing FB21588346. I read through your bug report and it’s pretty bare bones. I recommend that you update it with more specifics, like the info you shared in your comment above. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I think you’ve started off on the wrong path and now you’re starting to realise just how wrong it is )-: I’d like to clarify your requirements here. You only want to customise the app’s icon. That is: You’re using -setActivationPolicy: as a workaround for the fact that you’re setting the icon programmatically. Not because your app pops in and out of the background. Is that right? Also, where are you getting these icons from? Is it a small set that’s built in to your app? Or something more complex? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve responded on the other thread where you asked this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Again, the key reference here is TN3134 Network Extension provider deployment. [quote='871848022, lilan, /thread/773414?answerId=871848022#871848022, /profile/lilan'] I set it to 17 for now. [/quote] I’m not talking about the deployment target (the OS version), but rather the deployment channel (Development, Ad Hoc, or App Store, including TestFlight). TN3134’s focus on deployment leads to an important subtlety that it doesn’t cover. During development, iOS allows you to save a NE filter configuration using NEFilterManager. This allows you to develop your content filter without messing around with configuration profiles. However, that affordance isn’t enabled during deployment, at which point you have to follow the rules in TN3134. Network Extension determines whether your app is Development or Distribution sign based on the get-task-allow entitlement (com.apple.security.get-task-allow on macOS, get-task-allow on other platforms). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @

Let’s start with the trivial: [quote='812323021, charlieMonroe, /thread/812323, /profile/charlieMonroe'] MyApp.app/Contents/Resources/mytool [/quote] Contents/Resources is not the right place for a helper tool. Rather, I recommend Contents/MacOS. See Placing content in a bundle. Also check out Embedding a command-line tool in a sandboxed app for general background. However, none of that is the cause of the really issue here. Rather, consider the error your got: exec of /Users/charliemonroe/Library/Containers/com.charliemonroe.MyApp/Data/tmp/par-636861726c69656d6f6e726f65/cache-9c78515c29320789b5a543075f2fa0f8072735ae/mytool denied …` Note the path. It’s not Contents/Resources/mytool but rather something in your app’s temporary directory. I suspect that the wrapper applied by the pp tool is actually unpacking code into the temporary directory and then running that. This won’t work because sandboxed apps aren’t allow to create and execute code. Specifically, when a sandbox program creates a file, that file is a

[quote='871830022, matthewruzzi, /thread/812360?answerId=871830022#871830022, /profile/matthewruzzi'] Are there any other places that I should post this to get more discussion? [/quote] I can think of least two: JavaScriptCore is open source as part of WebKit project, and they have their own community discussions. Likewise, Swift is open source and has Swift Forums. The best approach kinda depends on who you want to do the work. If you just want Apple to fix something, Feedback Assistant is your best option [1]. But if you want to engage with other developers then things get more nuanced, especially with regards to where the changes land, which is a big factor in what work gets done and who does it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For more about that process, see Bug Reporting: How and Why?. And if you do file this in Feedback Assistant, please post your bug number, just for the record.

Are you developing a VPN product that’s affected by this? Or are you reporting this from the perspective of someone using a VPN product created by some third-party developer? If it’s the latter, I recommend that you discuss this with the VPN product’s developer. If it’s the former, the first thing I’d like to do is clarify whether your VPN product is based on the Network Extension architecture? Or whether it’s using legacy VPN techniques? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You’ve written your post like a bug report, which suggests you are in the wrong place. The Apple Developer Forums are here for developers to get help using Apple APIs, developer tools, and so on. For cases like this, where you’d like to request a change to Apple systems — well, a change back — the place to go is Feedback Assistant. See Bug Reporting: How and Why? for lots of info on how to use that tool effectively. Once you’re done, 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

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

In general, the notary service should include all Mach-O images in your submission in the ticket that it issues. Thus, you shouldn’t have to notarise helper independently, or Application Bundle.app for that matter [1]. However, I recommend that you check this, just to be sure. To do that: Submit your package for notarisation. On successful notarisation, fetch the notary log. See if it lists the cdhash values for helper. IMPORTANT If your helper has multiple architectures, check that both cdhash values are present. For more on cdhash values, see TN3126 Inside Code Signing: Hashes. For more background on how this stuff works, see Notarisation Fundamentals. For links to lots of other notarisation info, see Notarisation Resources. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Although it’s fine to do that if, for example, you also distribute the app via some other channel that doesn’t involve this installer package.

OK. Thanks for confirming. When you see this, is there only one user involved? That is: You’ve log in via the GUI. And are working with networking, including your VPN. Without logging out. Or fast user switching to a different user. Is that right? This matters because appex packaging only really works in the context of a single user, so if you add other users into the mix things get complicated. Also, you wrote: [quote='811887021, disinghal, /thread/811887, /profile/disinghal'] internet goes away on machine leading to a connection stuck state. [/quote] Can you clarify what this means? I see two possibilities: Networking goes away for other apps on the system but the system doesn’t start your packet tunnel provider. Alternatively, the system starts your packet tunnel provider and it attempts to connect to your VPN server and that connection acts like there’s no Internet. Is it either of these? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail =

[quote='812219021, madsodgaard, /thread/812219, /profile/madsodgaard'] I have read most of the Background Tasks Resources here [/quote] Cool. But there are some network specific ones you should also read: Moving to Fewer, Larger Transfers Testing Background Session Code The first one is probably most relevant to your issue. Networking Resources has these links and a lot more. [quote='812219021, madsodgaard, /thread/812219, /profile/madsodgaard'] But, what if they just stay with the app in the foreground? Will it start uploading immediately? [/quote] I would expect so. However, that’s not guaranteed. The nature of background sessions is that the system gets to choose when to run the transfer, based on its global view of the device state. IMPORTANT A lot of this stuff is not documented, and deliberately so. These policies are considered to be implementation details. They’ve changed in the past and it wouldn’t surprise me if they changed again in the future. So, when you ask “Will it do X?” the only real answer

[quote='865347022, zed_090, /thread/805920?answerId=865347022#865347022, /profile/zed_090'] I fixed it by updating: [/quote] Weird. Just for grins I created a tiny test app that contains your first code snippet, and it passed through the App Store Connect submission process without any problems. So I’m not sure why this is failing for you or why that change helped. If you’re feeling enthusiastic about this, you could revert the change, see if it still reproduces the problem, and then file a bug about it, making sure to attach the .ipa that you fed into Transporter. If you do that, please post your bug number, just for the record. But no pressure. I understand if you just decide to stick with your workaround. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com