eskimo

[quote='873882022, oddeyed, /thread/799110?answerId=873882022#873882022, /profile/oddeyed'] The contents nested in the application bundle are not world readable. [/quote] Yeah, don’t do that. macOS expects apps to be world readable so that all users can run them, and not following that convention takes you well off the beaten path. Honestly, I’m surprised that this is the first problem you hit O-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873874022, FT-cfoy, /thread/811791?answerId=873874022#873874022, /profile/FT-cfoy'] I wish I could ignore it [/quote] )-; [quote='873870022, FT-cfoy, /thread/811791?answerId=873870022#873870022, /profile/FT-cfoy'] I've submitted a bug report with this FB21768382 [/quote] Thanks. That’s definitely the right choice in this situation. Also, please add a sysdiagnose log to that bug, one taken on your device shortly after reproducing the issue. That helps with the triage. On the workaround front, you’re using MKMapView via UIViewRepresentable. If you switch to the shiny new Map SwiftUI view, does that avoid the problem? Another option is to filter these log entries out in Xcode: Locate the Filter box at the bottom of the Console debug area. Copy the string subsystem:com.apple.PerfPowerServices and paste it into the box. That’ll create a Subsystem filter. In the menu hanging off that filter, select “≠ is not”. For many other systems log hints and tips, see Your Friend the System Log. Share and Enjoy — Quinn

Thanks for the crash report. I was able to uncover an internal bug that AFAICT is tracking the same issue (r. 154431813) [1]. Sadly, that remains unfixed and doesn’t offer any ideas as to how you might avoid it. My advice is that you file your own bug about this, attaching all the information you have available. Please post your bug number, just for the record. Also, you mentioned that you’re in touch with some users that can reproduce this. If so, could you ask them to file their own report about it in Feedback Assistant. That should capture a sysdiagnose log, which might help with the investigation. If that happens, ask them to send you their bug number and then post those here as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Much to my own surprise. Radar is a very big haystack (-:

I can’t speak for a564033861, but from an Apple perspective it’s hard to track down whether we fixed this problem because they didn’t post their bug number )-: Given that, my advice to you is going to be the same as the original advice I gave them: Please file a bug. Ideally with a linker snapshot. Post the bug number here to make it easier on Future Quinn™. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873889022, dileepachandrasekara, /thread/813571?answerId=873889022#873889022, /profile/dileepachandrasekara'] Bug filed FB21757864 [/quote] Thanks. I’ve added my own comments to your bug. [quote='873907022, dileepachandrasekara, /thread/813571?answerId=873907022#873907022, /profile/dileepachandrasekara'] I want to understand whether this is a bug fix … [/quote] In my opinion this is a bug, but the resolution of your bug report will act as an official answer to that question (-: [quote='873889022, dileepachandrasekara, /thread/813571?answerId=873889022#873889022, /profile/dileepachandrasekara'] We need to extract the filename without extension for display purposes. [/quote] Ah, I’ve found myself in that very conundrum. It’s annoying that we never got a Swift equivalent of Objective-C’s -stringByDeletingPathExtension method. I think it’d be reasonable for you to file an enhancement request for that. And if you do, please post that bug number as well. [quote='873889022, dileepachandrasekara, /thread/8135

Thanks for those additional answers. [quote='873877022, Retouch, /thread/813562?answerId=873877022#873877022, /profile/Retouch'] I understand it refers to the scenario: “You have an existing flow object …” [/quote] OK. The error you’re getting is NEAppProxyFlowErrorDomain / 1. That’s a bit confusing because the error domain string doesn’t match the error domain identifier. In fact, the identifier is NEAppProxyErrorDomain: print(NEAppProxyErrorDomain) // -> NEAppProxyFlowErrorDomain So, code 1 corresponds to NEAppProxyFlowErrorNotConnected, which is documented to mean: The flow is not fully opened. However, you’re sure that the flow was fully open, so it’s not that simple. I did some digging and it seems that this error is caused by you attempting to write when the write side of the flow is closed. There’s a couple of ways that might happen: If you write to the flow before the open is complete. Or at least I think that’s the case. I wasn’t able to be 100% sure about that, and I declined to research further

[quote='873905022, pawanquantum, /thread/813746?answerId=873905022#873905022, /profile/pawanquantum'] What we want is to allow the user to manually disconnect the tunnel via a UI button [/quote] A button in your app? Or elsewhere in the system? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I read your post a bunch of times and it’s not clear whether you’re simply describing your experience or whether you have a question. Please clarify. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873863022, DTS Engineer, /thread/813853?answerId=873863022#873863022'] may I ask you to file a bug with that project? [/quote] Before you do that, I’d like to clarify what you mean by this: [quote='813853021, OC_s, /thread/813853, /profile/OC_s'] How do I determine the real values? [/quote] What specific information are you looking for here? And what do you plan to do with that information? This matters because Mac Catalyst is returning values that make sense in the iOS-ish environment that’s expected by such apps. It is possible to get ‘real’ values, but the best way to do that depends on your specific setup. For example, the systemName property is uninteresting in a Mac Catalyst app because the real system name is macOS. So you can do this [1]: let systemName: String #if targetEnvironment(macCatalyst) systemName = macOS #else systemName = device.systemName #endif However, that’s just one of these properties. The best path for the other properties varies based your the specific property and your ulti

AFAIK this information is available from Core WLAN. See the various properties on CWChannel. IMPORTANT Modern versions of macOS limit what Wi-Fi information you can access unless you have the Location privilege, as shown in System Settings > Privacy & Security. That restriction has been discussed on the forums many times. If you rummage through the posts with the Core WLAN tag, you’ll find a bunch of backstory. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='813858021, benwiggy, /thread/813858, /profile/benwiggy'] Why should a signed app be quarantined just because it's been downloaded? [/quote] Because that’s what quarantine is for. User-level downloaders, like Safari, quarantine stuff so that Gatekeeper runs when the user uses that stuff [1]. I talk more about this overall process in the first few sections of Resolving Trusted Execution Problems. Did you notarise your app? If not, that’s the first thing to fix. Notarisation Resources has links to documentation describing how to do this, and a lot more besides. Once your app is notarised, I recommend that you re-test using the process described in Testing a Notarised Product. If your app is notarised and still fails to pass Gatekeeper, run syspolicy_check against it. See the Run a System Policy Check section of Resolving Trusted Execution Problems If you continue to have problems, reply here with the details and I’ll see what I can do to help. Share and Enjoy — Quinn “The Eskimo!” @ Developer Te

I’m not sure what you’re referring to here. Please reply here with more details about the issue you’ve encountered. ps Quinn’s Top Ten DevForums Tips has lots of info on how to use the forums effectively. You should give it a read. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873516022, DTS Engineer, /thread/811382?answerId=873516022#873516022'] I’m going to research this further and get back to you. [/quote] I reached out to a colleague about this and they confirmed that my guess was correct. Better yet, they pointed me at App Store Connect Help > Transfer an app > Overview of app transfer > Apps using iCloud, which covers this topic specifically. It says this: If your app uses any of the following, it will be transferred to the transfer recipient after they accept the app transfer. … KVS identifiers associated with the app which confirms that iCloud key-value store preferences are expected to transfer, and this: If your app uses iCloud Key-Value Storage (KVS), the full KVS value will be embedded in any new provisioning profiles you create for the transferred app. Update your entitlements plist with the full KVS value in your provisioning profile. My interpretation of this is that you it’s telling you to do what we’ve done in this thread, that is, set the value i

Did you run the NWConnection diagnostic test I suggested in my previous post? What was the result? Again, this test is a important because it allows us to distinguish between two cases: Networking in your provider is blocked completely. Networking in your provider is fine in general but there’s an issue specific to URLSession. Knowing this is both useful as a diagnostic and, at least in the second case, raises the potential for a workaround. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='873554022, jamie_sq, /thread/805609?answerId=873554022#873554022, /profile/jamie_sq'] if any investigation has revealed whether there's anything that can be done to work around the problem [/quote] Nothing obvious popped out )-: I can say that we do fully understand the issue now and that makes the likelihood of a fix promising. However, I can’t offer a concrete timeline, other than to confirm that the fix didn’t catch the Xcode 26.2 bus. As always, I recommend that you re-test with future beta releases of Xcode as we seed them. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com