What do you think we can do with this? You haven't bothered to say what you were doing, what automation you're trying to use or create. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Are you in the right place?

You're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. You could even go ahead and ask Ford if they're planning an update... Thanks.

Have you tried iOS 18.2? It was just released last week. Aside from that, you're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

Can you rephrase your questions, please? You're not really making much sense. Apple Intelligence is still in Beta. What message are you talking about? And what do you want to load?

I've extensivley tested this over the past two days. I tried timelines spanning one day, with: 72 entries, every 20 minutes 36 entries, every 40 minutes 24 entries, every hour 12 entries, every 2 hours 6 entries, every 4 hours 3 entries, every 8 hours 2 entries, every 12 hours In every case, the policy is .atEnd, and in every case the timeline is not refreshed when it's supposed to be, which causes the widget to display the wrong timer values. Due to the inflexibility of Text(date, style: .timer), I need to write code that calculates the correct timer value but shows less than a day. For example, if it's 11am today and the event date is tomorrow at noon, there are 25 hours between the two dates and the standard .timer would show 25:00:00, which is not what I want. So, I calculate the next occurrence of noon, and the widget shows "1 day" with a timer of "1:00:00". Every timeline with a refresh policy of .atEnd caues the countdown timer to show the wrong values. I've got it logging to a file, and I can see that the countdown dates are completely correct in every case. The widget is never refreshed at the right time, so the timers always show the wrong values. The only way I've managed to get this to work is to have a timeline with one entry, and a refresh policy of .after(), i.e. let date = Date() let refreshDate = Calendar.autoupdatingCurrent.date(byAdding: .minute, value: 30, to: date)! Timeline(entries: entries, policy: .after(refreshDate)) There is clearly something wrong with .atEnd.

You're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

Okay, firstly, you have a MacBook Pro 2021 with an M1 chip, not a "Mac M1 Pro 2021". Do you have to use Apple Configurator? Can't you restore it in any other way? What have you tried? Oh, also, you're in the wrong place. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

If you look at the Developer Documentation for Task it shows which versions it's available in. I see: iOS 13.0+ | iPadOS 13.0+ | Mac Catalyst 13.0+ | macOS 10.15+ | tvOS 13.0+ | visionOS 1.0+ | watchOS 6.0+ So yeah, macOS 15.0+. Is your app definitely only targeting iOS?

You're in the wrong place here. These are the Developer Forums, where developers of third-party apps ask for hints and tips on coding their own software. We're not Apple developers. Your link to that post from 2014 is the right place for you to ask this question. However, I'll give you a litle help. That post by Grant Bennet-Alder simply shows the Configuration.plist file being shown in Xcode. It is not necessary to have Xcode to edit that file. Also, when you say "root within xcode" you're misunderstanding what's being shown. Root is simply the root of the XML in that file, i.e. the base level of it. All data in an XML file - which is what a .plist file is, starts off in the root. You do not need to be in root mode to edit that file. Does this folder exist? /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/Resources/ If so, is there a Configuration.plist file in there? If so, edit it in any text editor you want, and change it as suggested. That folder exists on my macOS 15.1.1, but the Configuration.plist file is not there. It is possible that, over the years, this was renamed, as there are two other .plist files in my current folder: Info.plist and version.plist but they do not look like your example.

Veuillez visiter les forums d'assistance Apple où vous pourrez peut-être mieux répondre à votre problème.

Does your app do anything with photos or the photo library? Are you using a third-party library that uses them?

If you don't provide us any code to have a look at, you're just shouting into the void. Give us some code we can look at. We may notice what you're doing wrong, but right now we have no idea; you're basically just telling us you have an issue. What do you think we can do with that?!

Moving your own app to the Hidden folder would be okay. Moving someone else's app? Nope.

Look at your image and imagine there's a blue column immediately to the right of every red column. Now, the x-axis labels look like they're in the centre of the two columns. So, is your chart supposed to have two columns for each value? If not, in this line: AxisMarks(position: .automatic, values: shownXValues) { val in can position: .automatic be changed to something else? Also, is .useAppFont() a SwiftUI thing, or something you've written yourself? I've never seen it before.

Is it your app? If so, you must know why you removed it? Is it someone else's app? If so, ask them. We're just random people who develop software for Apple's platforms, and can't help you on this.