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 }

They're asking you to give the _ variable a name, and it's entirely up to you what you call it; it's just a variable name. The right-hand side was already given a name, numbers, and it represents the right-hand side of the information in the interestingNumbers array, i.e. the arrays of numbers. The underscore represents the left-hand side of the data, i.e. the three String values: Prime, Fibonacci, and Square. If you do this, you should see how it works: let interestingNumbers = [ "Prime": [2, 3, 5, 7, 11, 13], "Fibonacci": [1, 1, 2, 3, 5, 8], "Square": [1, 4, 9, 16, 25] ] var largest = 0 var largestSet = "" for (dataset, numbers) in interestingNumbers { for number in numbers { if number > largest { largest = number largestSet = dataset } } } print ("largestSet '\(largestSet)' with value: \(largest)")

I tried posting this a couple times now but it keeps getting taken down - I am not too sure why. I haven't received any explanation and I am pretty certain that I am posting in the correct place for TestFlight Apps. It gets taken down because this is absolutely and totally NOT the right place for posts like this. These are the Developer Forums where third-party developers of apps for Apple's platforms ask for hints and tips on coding issues, or the Apple Developer Programme. If you have an issue in your code, ask us and we may be able to help you. If you want us to test your apps, you must know that we have our own apps to develop and test, and don't have the time to test yours. Sorry, that's just the way it is. You can go on the various Mac-/iPhone-related news & rumours forums and ask for people to test your apps, because I can tell you right now, we don't have the time. Sorry.

Yeah, or some bot accounts asking about ASO. Perhaps complaints about review length or developer account issues should be syphoned off into a separate section? Maybe Apple could add a section above in the new post screen that says if they have an issue with their account to "click here" and go to some other place where actual Apple staff will have to respond? As a developer I don't really care about review length or someone else being unable to find a button in their Developer Account settings. I've helped people and never gotten a response from them, so I tend not to bother helping now. I've used these forums a lot in the past, and I enjoy them, but they have definitely recently gone downhill. Right now they're "just good enough". Apple should step in and make them better.

It looks like the Review team are logging in but aren't able to do much. What happens when you login with those credentials? You're in your prod environment, right? And if you want to go through using the app what do you have to do? You have to perform an actual transaction... in a prod environment... where actual money is used. The Review team are not going to do that. Do you have a test environment? If so, you should change the app so that when this particular test account logs in, it connects to the test environment instead of your prod environment so that the review team can go through the app properly. If you don't have a test environment, you should probably spin one up for the duration that the Review team need to use it.

Accept your own answer. That'll show others there's a solution to this, so they'll be more likely to view this thread and see it 😉

Don't you have to have created a new app in App Store Connect for Xcode to upload it? Otherwise, Xcode doesn't know where the app should go. Not sure how you achieve this, but before making any more attempts at uploading to App Store Connect, install your old app on the Simulator, then run the new app and install it to the Simulator. If you get two different apps, then you know that you haven't done it properly. Delete the new app from the Simulator, make some changes in Xcode and install to the Simulator again. Repeat until it actually just installs over the top of the original app.