They explain here a subtle behaviour (to say the least) of JSONEncoder. https://forums.swift.org/t/encoding-decoding-a-swift-dictionary-to-from-json/39989 A dictionary with Int or String key is encoded as dictionary. But with other type key, it is encoded as an array. That seems to be the case with the enum. I tested by catching error: do { let json = try JSONDecoder().decode(Json.self, from: jsonString.data(using: .utf8)!) print("JSON", json) } catch { print("Error", error) } and got the same error message: Error typeMismatch(Swift.Array<Any>, Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "variations", intValue: nil)], debugDescription: "Expected to decode Array<Any> but found a dictionary instead.", underlyingError: nil)) As you noted, if you replace the key type by String: struct Json: Codable { let variations: [String: String] } Then you get the expected result: JSON Json(variations: ["plural": "tests", "singular": "test"])

You do not show what books are. I suppose they are an array of some struct Book. Not sure I fully understand your question. But you can pass a books array to the Preview: #Preview { Library(books: [populate an array of Book]) }

I wonder if that's just possible. In 3D, a point on screen could be the visualisation point of several points on the graph, from frontmost to the last in the back. How would you discriminate between them ?

Hi Marc, if you want some advices on how to best use the forum, read this great post from @eskimo: https://developer.apple.com/forums/thread/706527 And don't forget to close the thread by marking the correct answer.

What was your question ? Please avoid duplicating posts.

The page shown on the first screenshot is version 1.0. I do not see where is version 1.1. You should: type the + blue button next to "MAcOS App" to declare a new version 1.1 Complete all the required meta data build for 1.1 will appear in the build section.

You can modify only in the first hour after posting. After, the post cannot be edited. In your case, you could: create a new post with the new title and maybe modified content.It would also be fine to point to the old post. in the old post, make a new answer where you link to the new post, explaining it is more general. IMHO, it is not worth bothering moderator for such a change.

Where did you get that windowNumber is UInt32 ? Doc states: var windowNumber: Int { get } On 32-bit platforms, Int is the same size as Int32, and on 64-bit platforms, Int is the same size as Int64. But never a UInt32. Why do you need converting from Int to UInt32 ?

You should contact support. It looks like those deletions and resubmissions have caused some mess. The other app has no issus, so there is no problem with your account.

That's a long known issue, when radius is between 1/3 and 1/2 of the side size. Detailed analysis here and, even more interesting, a solution with addArc(tangent1End: …): https://stackoverflow.com/questions/74623415/uibezierpath-bezierpathwithroundedrect-the-cornerradius-value-is-not-consistent

Removing the submission and resubmitting is not the best thing to do. I notice it may cause problems. You should contact support to clarify.

@iDepth from your screenshots, we can see that the new design frees space for the app's content. Isn't it a very good thing ?

Do you use a site generator to create your web site ? If so, they usually have tools or plugins to create contact forms. For instance, if you use WordPress: there are templates which include directly a contact form generator or you can add a plugin, such as contact-form 7 and there are detailed tutorials for using: such as: https://wpmarmite.com/en/contact-form-7/ Hope that helps.

Not sure you can do it on your own. Did you contact support for help ? To avoid such problem, I use a different scheme for build and version. version is the classical x.y.z and for build, I use the date 20250614. I find there is much less risk of confusion.

I had to refresh my mind on FFT. Found this interesting reference, may be of interest for those of us who need as well. https://www.analog.com/media/en/technical-documentation/dsp-book/dsp_book_Ch31.pdf