İOS 26 beta battery %1

I ended up updating my CI nodes to run macOS 26 Tahoe, and this error doesn't occur anymore.

Alas, my enthusiasm was a little bit premature. While my iPhone running iOS 26 proves that the problem has been fixed, somebody's iPad (though running at the moment iPadOS 18), despite getting the app being compiled and installed from Xcode 26, shows the bug being still there. How come that iOS 26 does have a fix, but iPadOS 26 does not (I checked on Simulater as well).

I get the same issue with my store kit configuration file. interestingly It still works on iOS in a simulation, but it does not work on macOS in a simulation. macOS always returns no products when I call the API. Here’s a post where I’m looking for an answer to that issue as well. https://www.reddit.com/r/SwiftUI/s/64xfCfbIPM

One can remove a language from the .xcstrings file through the .xcodeproj file, under Localization → (-) [Language]. The .xcstrings file seems to lack a minus (-) Button. However, in my project I could remove a language like this: I added the language (L) in the .xcstrings file to test it. After some time, the language L showed up in .xcodeproj file, under Localization. ❗️3. Here, there is a (+) and a (-) button, I selected the language L and removed it using the (-) button.❗️ After some time again, the language L did not appear in the .xcstrings file anymore. I assume it takes some time to synchronize between .xcstrings and .xcodeproj. Best, Tim :)

No idea if this pending authorization disposition is relevant or not, but I do not know what else I as a user can possibly authorize beyond flipping the switch in System Settings. #9: UUID: 0C6D2CA3-9BAF-45D8-819B-604F52203F56 Name: SMAppServiceSampleCode Developer Name: ABCDEFG Team Identifier: *****437 Type: app (0x2) Disposition: [disabled, allowed, visible, not notified] (2) Identifier: identifier com.example.apple-samplecode.SMAppServiceSampleCode8B59GX9437 and anchor apple generic and certificate leaf[subject.CN] = Apple Development: user@host.com (XXXXXXX) and certificate 1[field.1.2.840.113635.100.6.2.1] /* exists */ URL: file:///Applications/SMAppServiceSampleCode.app/ Generation: 0 Bundle Identifier: com.example.apple-samplecode.SMAppServiceSampleCode8B59GX9437 Embedded Item Identifiers: #1: com.xpc.example.agent #10: UUID: F8746E58-2ADA-4840-82E7-9DCC1F77FD72 Name: SampleLaunchAgent Developer Name: (null) Type: daemon (0x10) Disposition: [enabled, allowed, visible, notified] (pend

ASWebAuth + Universal link issue -In login iOS application we are launching the Login URL in the ASWebAuth to support the auto-saving of the username and password. -It enables the passkey options seamlessly. When user enters into the Native app using the passkey or saved credentials, we send an Auth-Return URL to Login system -login in response of successful authentication redirect user to the Auth-Return URL along with an authenticated Auth-Code value. -When the Auth-Return URL is evaluated, it is expected that we should redirect user back the Native application and proceed with the session of the user along with the Auth-Code received. Problem is ASWebAuth not dismissing and handover to app

OK, that’s definitely a sysex. Thanks for confirming. Given that, you should be able to export it for direct distribution with Developer ID signing. You’ll have to carefully work through the steps in Exporting a Developer ID Network Extension. Make sure that: The code is signed with the Developer ID variants of the com.apple.developer.networking.networkextension entitlement values. That entitlement claim is authorised by a Developer ID provisioning profile. Make sure to check both the container app and the embedded sysex. I also recommend that you add a ‘first light’ log point to your sysex so you can see whether it’s code runs at all. See Debugging a Network Extension Provider for more about that. And if you don’t get that log point, make sure to check for crash reports. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Again, I recommend that you use a .exp file so you have direct control over what gets exported. If you don’t want to do that, you’ll have to combine information about how the symbols are exported from the static library with information about how the framework is linked. For the former, see An Apple Library Primer and the Understanding Mach-O Symbols post it links to. For the latter, see Command [something] failed with a nonzero exit code for the commands passed to the linker, cross referencing that with the help in the ld man page. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='857868022, ski4funSonoma, /thread/799933?answerId=857868022#857868022, /profile/ski4funSonoma'] it seems to be the remedy to the helper/daemon crash. [/quote] That’s unlikely. Launch contraints typically cause things to fail rather than make things work. Hence the constraint. My advice here is that you remove anything you’ve done with regards launch constraints and then debug the original problem you were seeing. If that’s a crash and you post a crash report, I’d be happy to take a look. See Posting a Crash Report for advice on how to post a crash report. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The answer here is… well… fuzzy. I’m gonna recommend that you file a bug about the weird behaviour you’re seeing, so we can use that to investigate further. IMPORTANT Make sure to include information about why you’re accessing ARP, that is, what high-level goal you’re trying to achieve this way. 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