“Apple Maps Guides”

Hi, I want to recreate a chart from Apple Health and I have code like this. When I scroll - especially the week and month charts, there are performance issues. If I remove .chartScrollPosition(x: $scrollChartPosition), it runs smoothly, but I need to know which part of the chart is currently displayed. Can you help me? import Charts import SwiftUI struct MacroChartView: View { var selectedRange: ChartRange var binnedPoints: [MacroBinPoint] @State private var scrollChartPosition: Date = .now var body: some View { VStack { Text((selectedRange.rangeLabel(for: scrollChartPosition))) Chart(binnedPoints) { point in BarMark( x: .value(Date, point.date, unit: selectedRange.binComponent), y: .value(Calories, point.calories) ) } .frame(height: 324) .chartXVisibleDomain(length: selectedRange.visibleDomainLength()) .chartScrollableAxes(.horizontal) .chartScrollPosition(x: $scrollChartPosition) .chartScrollTargetBehavior(.valueAligned(matching: selectedRange.scrollAlignmentComponents)) .chartXAxis { switch select

As the title suggests, I've been waiting over a month for a review. Testing patience to say the least when the official word is less than 72 hours.. What is going on? The version in review is now out of date as I've developed features quicker than Apple has been able to review them, yet I daren't remove the app from review as I'll lose my place in the queue. So even when/if it gets approved, I'll immediately have to add a new version for review. What a farce. Submission ID 994fa30a-92a6-4923-8cc8-b94090986b39

I want to write a CryptoTokenKit plugin to be used to unlock FileVault. I understand macOS already provides such a plugin for a PIV smart card https://support.apple.com/en-mz/guide/deployment/dep806850525/web Perfect. I want to do the same for a non-PIV smart card. So I have to provide my own CryptoTokenKit plugin. I already implemented a smart card plugin TKSmartCardToken. I can use it so pair the user with the smart card and use the smart card to login (except for the 1st login when the disk is still encrypted). As far as I understand for preboot I need to provide a persistent token https://support.apple.com/en-mz/guide/deployment/dep4e2622249/web From Xcode I created an empty application, and added a Persistent Token Extension (instead of a Smart Card Token Extension). After built I can see my new token in the output of pluginkit -m -p com.apple.ctk-tokens. My questions: how and when is my plugin loaded? I added calls to os_log_error() in all the empty methods created by the Xcode templat

I have a very important voice memo that I have recorded on my iPad, as I was recording it, it seemed to have completely worked, but for some strange reason the voice memo will not play, download to my filess, I am unable to send it to anyone, and it basically just pops up blank every time I just try to share it. I cannot listen to it and have not been able to listen to it. This is the same on both my iPad and my phone, when I went to Apple, they said to come on here and ask for guidance, and that it might be because my regular iPhone is updated normally but on my iPad, which was the Voice Memo was recorded on is updated To beta. please give me some advice and if there’s any way, I could recover even the transcript of the voice message because it is truly so important to me. The sound waves are there and everything and I just don’t understand why it will not play on either device. I have also tried copying it. I have also tried trimming the beginning and it’s like the data is there, but it will not pl

We've noticed, that size of our ipa started to vary from time to time. We've found that all the difference was in the LC_CODE_SIGNATURE command under the _LINKEDIT segment of binary. The main reason of that change was the different number of hash slots due to different value of page size: 4096 on macOS SEQUOIA and 16384 on macOS TAHOE. So the size of the final binary was dependent on the machine, it was produced on. I didn't find out any information on why the default page size changed on TAHOE. Apple’s codesign supports a --pagesize argument. For regular builds that setting can be passed via OTHER_CODE_SIGN_FLAGS=--pagesize 16384. But it seems that xcodebuild export ...` completely ignores it: i've tried to pass invalid size (not the power of two), and the export still succeded. I've also managed to get xcodebuild logs via log stream --style compact --predicate 'process == xcodebuild OR process == codesign' --level trace They have no occurrences of --pagesize: 2026-03-24 13:43:27.236 Df xcodebuild[9