This is clearly an Apple bug. Have either of you raised a Feedback report? Perhaps if it's raised there someone might see it and fix it? Anyway, as a workaround, you could ask Apple for an address to post a physical form to. If they'll accept a physical form, download it from https://www.irs.gov/pub/irs-pdf/fw8ben.pdf, print and complete it, then post it to them. If you can afford tracking and/or signature on delivery (ask Apple if they'll sign when they receive mail that requires a signature; some companies won't), pay for it so you know they've received it. I think - can't remember as it was almost 20 years ago - when I set up my dev account for the App Store I had to post the form, so back in 2008 they accepted them.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for help, and 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.

I have never once been dissatisfied with the light on my MagSafe cables. I personally think you're over-engineering something here. Also, you're coming across as a little bit grumpy just because Apple hasn't already implemented your idea or told you definitively that they're going to implement it. You've been told about the unsolicited idea policy, so read it. You aren't going to be congratulated for anything, or rewarded for it. What are you going to do? Not mark the post as answered until Apple implement your idea? If you came across as less needy and followed the process you might be listened to a bit more.

Debug your code. Also, don't raise duplicate posts on the forums. Either edit your original post within an hour of posting it, or reply to the original. There's no reason to create multiple posts for the same thing.

What do you want us to do about it? Debug your code.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your post has nothing to do with developing for Apple's platforms. Please don't misuse these forums.

Good, now what have you actually tried? Show us some code. Is it the background of the data fields you want to get, i.e. the rounded rectangle boxes on top of the large AH background? It looks like some sort of simple gradient. What have you tried?

I hope that's test data and you haven't actually posted someone's private details on the internet...

These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. While a few of Apple's developers do sometimes visit these forums and mention that suggestions raised in here might be good ideas, they will always request that you raise each one of your suggestions separately at: https://feedbackassistant.apple.com/

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.

I had another think about this. How about using .position(x:, y:) to move the image? Just tried this code, and it looks good for AccessoryCircular, AccessoryInline, AccessoryRectangular, Smart Stack Circular and Smart Stack Rectangular, but is slightly off for AccessoryCorner, so again, you'll have to fiddle with the numbers for at least one of the types: GeometryReader { g in ZStack { // I added this circle to show where it is in the view Circle() .foregroundColor(Color.blue) Image(systemName: "circle.dashed") .resizable() .scaledToFit() .foregroundColor(.green) .position(x: g.size.width / 2 + 0.5, y: g.size.height / 2 + 0.5) // The 0.5 is the part that moves it to the right and down a little Text("9/9") .foregroundStyle(.primary) .font(.caption) .fontWeight(.semibold) } .widgetAccentable() }

Yeah, definitely wrong. I've just recreated this myself. You should raise this as a bug at https://feedbackassistant.apple.com/ then post the FB number here. I managed to get a normal dashed line to work, but the trade-off is that you have to get the right values for the circle size, or the dash where the line ends will be the wrong length when it hits the part where it started (if that makes sene?). // Looks correct for Accessory Circular: Circle() .stroke(.green, style: StrokeStyle(lineWidth: 10, dash: [12.5, 7.25])) // Looks correct for Accessory Corner: Circle() .stroke(.green, style: StrokeStyle(lineWidth: 7, dash: [11, 6.5])) // Neither of those two looks right for Accessory Rectangular You'll have to play around with the values for the different Accessory types if you decide to go with this option.

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 might also want to raise a Feedback report at https://feedbackassistant.apple.com/ When raising the report be sure to state what version of macOS you're using, and model of display as you seem to have omitted that here.

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 show the relevant code for the toolbars? Are you missing something like: ToolbarItemGroup(placement: .primaryAction) { // toolbar items }