dsym file

There have been some behavioral changes on N1 chip devices; especially in areas where the BT spec has not had a single way of interpreting things. We have been observing these changes and changing them back if appropriate and are considered regressions. So, the first thing you should do is to test all this in the latest iOS 26.3 and see if anything has changed from your earlier observations. Also, there would have been some changes on patterns of use that were never meant to work, but just happened to work, and those would have been corrected. For example, scanning without services is not supposed to work, and was never expected to work in the background. If you are scanning in the background without services, and whatever the Flutter library may have been doing to work around that limitation (if anything), and that has stopped working, you can consider that a bug that has been fixed. Similarly, advertising packets in the background have always been on a best effort basis. Also, it has always been possible th

Our SSH certificates are in OpenSSH format (RFC 4253), not X.509. These use a custom binary encoding that SecCertificate doesn't understand. Since kSecClassCertificate expects X.509 DER format: Should we store OpenSSH certificates as kSecClassGenericPassword with descriptive metadata? Is there any Keychain support for non-X.509 certificate formats? Or is the recommendation to keep them as files and only move X.509 TLS certs to Keychain? Example OpenSSH Certificate (text format): ssh-ed25519-cert-v01@openssh.com AAAAIHNzaC1lZDI1NTE5LWNlcnQt... Our current thinking is to store these as generic passwords: let query: [String: Any] = [ kSecClass: kSecClassGenericPassword, kSecAttrService: com.teleport.ssh.cert, kSecAttrAccount: (cluster).(user), kSecAttrLabel: Teleport SSH Certificate, kSecValueData: sshCertData, kSecAttrAccessible: kSecAttrAccessibleWhenUnlockedThisDeviceOnly ] Is this an acceptable approach for non-X.509 certificates?

Whether iOS provides any mechanism or API that allows iPhone apps to trigger or request parental re-approval after the application has already been installed PermissionKit has that for you: https://developer.apple.com/documentation/PermissionKit/SignificantAppUpdateTopic Also from which iOS version this capabilities will work & how to handle lower iOS version which is not supporting. The APIs seem to only be supported in iOS 26.2 and above. The laws say that A developer shall verify through the app store's data sharing methods.... Since Apple has not provided any data sharing method for users on iOS versions before 26.2, my interpretation is that we do not need to do any age verification for users on older versions of iOS, but I can not be sure at this time and this is not legal advice. I doubt Apple will provide any recommendation since doing that could be considered legal advice. The only way we will know for sure though is for the deadlines to pass, a law to come into effect, a relevant law suit filed

Hello @Reveloper Thank you for this enhancement request, If you'd like us to consider adding the necessary functionality, please file this request using Feedback Assistant. Once you file the request, please reply with the FB number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why? Thank you!  Travis Trotto - DTS Engineer

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.

@DTS Engineer Thanks again for replying and I have filed a bug requesting them to add support, through feedback assistant and here is the bug no. i guess FB21974462 .

[quote='876388022, mohalibou, /thread/812607?answerId=876388022#876388022, /profile/mohalibou'] It is possible to import a Swift package locally [/quote] Right. And that’s a great option for day-to-day development. My concern in this case is that the instructions say: Your submission must be an app playground (.swiftpm) in a ZIP file. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='876364022, Yashya, /thread/815698?answerId=876364022#876364022, /profile/Yashya'] Yes it's in Xcode playground [/quote] OK. This came up last year and the general consensus is that it’s fine to make this change in order to avoid all the availability ceremony. Note The reason I asked about whether you’re using Xcode is that Swift Playground still doesn’t support the iOS 26 SDK )-: See this post. I’d appreciate you filing a bug requesting that Xcode’s Swift playground support add a deployment target option. This limitation is an ongoing source of confusion for Swift Student Challenge participants )-: 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

Hi @DTS Engineer Travis, Thanks for the quick reply. As I mentioned in my original message, I haven't been able to recreate this condition in a sample project. I'd love to have a private conversation and show the issue in more detail, but we're ineligible to file a DTS ticket due to it. As you can see from the example above, the setup in the test window is all very simple so there must be something else causing this not to work properly. I understand what you're saying about the layer clipping, however there's no code associated with that window. No subclassed controls, no modified layers, no swizzling that I can see. We shouldn't need to do anything to get the truncation to work. One additional data point I can give you is that, before the issue occurs, we have this: p ((NSPopUpButton *)0x13426484d00).bounds (NSRect) (origin = (x = 0, y = 0), size = (width = 300, height = 24)) p (NSRect)[((NSPopUpButton *)0x13426484d00).cell titleRectForBounds:((NSPopUpButton *)0x13426484d00).bounds] (NSRect) (origi

[quote='815753021, AkshayKalucha, /thread/815753, /profile/AkshayKalucha'] We are currently observing NEVPNConfigurationChangeNotification [/quote] That is the canonical way to do this. [quote='815753021, AkshayKalucha, /thread/815753, /profile/AkshayKalucha'] it appears to have inconsistent behavior when … VPN configurations are installed programmatically via MDM systems [/quote] What do you mean by “inconsistent”? Your steps to reproduce indicate that this fails every time, which seems pretty consistent to me (-: Are you saying that this is inconsistent with the documented behaviour? Or are you seeing the problem intermittently? Either way, this sounds like a bug to me and I encourage you to file it as such. Make sure to include a sysdiagnose log taken shortly after reproducing the problem and, for bonus points, enable additional logging per the VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page. Please post your bug number, just for the record. On the workaround