İOS 26 beta battery %1

Same issue here. While waiting for a fix, does anyone know of an alternative way to transfer files to an iOS 26 RC simulator?

You might be running into a beta software bug. CarPlay often has issues on beta iOS versions. Try reverting to the latest stable iOS release and reconnecting your Rogue—this usually fixes the problem. If you want to stay on the beta, reporting the issue via Feedback Assistant is the best way to get Apple’s attention.

Hi, thanks for trying out the new API! I’m able to reproduce the bug, and it seems related to how WebView interacts with SwiftUI’s observation system. We will need to investigate this issue, as resolution may involve changes to Apple's software. I'd greatly appreciate it if you could open a bug report and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating your bug report. In the meantime, one possible workaround is to observe changes to some other property on WebPage, like .onChange(of: webPage.isLoading) { } for example, which will result in the back-forward list updating as expected.

Oh, one more thing: If you’re modifying Mach-O images, make that every different image has a different build UUID. See TN3178Checking for and resolving build UUID problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='800260021, danilabagroff, /thread/800260, /profile/danilabagroff'] I'm developing a macOS console application [/quote] “Console application” isn’t a term we use on Apple platforms. An application is, by definition, something the user double clicks in the Finder, shows up in the Dock, has a menu bar, and so on. I’m presuming that you’re building a command-line tool, something that the user runs from Terminal, or is run by the system as, say, a launchd daemon. Please let me know if that’s not the case. [quote='800260021, danilabagroff, /thread/800260, /profile/danilabagroff'] What is the recommended approach for debugging applications that need to load dynamic libraries? [/quote] There are a number of factors in play. I’ll come back to that later. But first I want to dig into your log message: [quote='800260021, danilabagroff, /thread/800260, /profile/danilabagroff'] Error Details When running the application through LLDB, I get this sandbox denial in the system log… logd_helper(587) [/quote] Look at th

Here's the code. It works on iOS/iPadOS but not macOS for the same .storekit file??? import SwiftUI import StoreKit public enum License: String, CaseIterable, Identifiable { public var id: String { self.rawValue } case subscriptionLifetimePremium = subscription.lifetime case subscriptionYearlyPremium = subscription.yearly case subscriptionMonthlyPremium = subscription.monthly } struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Button(StoreKit Test) { Task { @MainActor in // Request our offers from the app store let productIDs = License.allCases.map { $0.rawValue } print(productIDs: (productIDs)) let productsOffered = try await Product.products(for: Set(productIDs)) print(productsOffered: (productsOffered)) } } } .padding() } }```

[quote='800331021, packagesdev, /thread/800331, /profile/packagesdev'] Also why is there a tag for InstallerJS and not one for Installation in the Developer Forums? [/quote] Again with the why questions (-: Seriously though, I agree that there should be a tag for Mac installer packages. Although I’d probably call it Mac Installer rather than just Installation, because otherwise it’ll get flooded with iOS stuff. I can’t fix this immediately, but I’ve put it on my to-do list so that it doesn’t slip through the cracks. [quote='800331021, packagesdev, /thread/800331, /profile/packagesdev'] Has this element always worked correctly in the past? [/quote] Clearly no, in that you’re seeing it fail on 10.14. As to what you should do about this, it depends on whether you actually need to support 10.14 or earlier systems? [quote='800331021, packagesdev, /thread/800331, /profile/packagesdev'] Generally speaking, this documentation is missing examples for a lot of the elements. [/quote] It’s also in the D

This is is going to be tricky. An app’s icon is part of its bundle, and thus modify the icon will break the seal on the code signature. You don’t want to leave the user with an app with a broken code signature because sooner or later Gatekeeper look at the app, notice the broken signature, and kvetch. Now, what you could do is something like: Build, sign, and notarise all the variants of your app. From those variants, construct an installer that only contain one primary variant of your app and the diffs for all the other variants. Have that installer install the primary and then apply the relevants diffs. The end result is an app that’s correctly signed and notarised, and thus unlikely to hit notary problems. However, doing this is quite a bit of work. The key problems is that critical parts of the code signature are stored within the app’s main executable Mach-O image. If you store the diffs as a list of files, you’ll need N copies of the main executable, which presumably is quite large. There are w