How to delete container in CloudKit Dashboard?

Lol really you cannot delete? Wooow man this is incredible and I just started with CloudKit to find out this basic functionality not working hahahah.

Registered the container name with lowercase. Am I permanently locked out of the correct case name for the App?

July 19, 3145 - Still unable to delete containers

2021, Still no change.

I think that Apple wants to prevent at any cost that a production container gets deleted due to a software bug. And if I must choose between being able to delete containers (not deployed in production, that must be the main criterium), or a very small chance that I loose one of my production containers due to a software bug (by Apple or any other party), I would always choose to not being able to delete containers, and continue living with all those unused (incorrectly named, test or temporary) containers.

Maybe Apple wants the deletion of containers to be as revolutionary as the calculator on the iPad...

Facing the same issue, cant delete the container

11/20/2021

How many of you would be satisfied with being able to hide the containers from your list, without actually having them deleted?

Asking because it looks like Apple's never going to allow us to delete them (this thread is at least 5 years old), but it might not be such a big deal to Apple to let us hide unneeded containers on the UI level.

If you think you'd be happy with that kind of solution, please upvote this answer and/or add a comment for it, because I am not quite sure we can see the upvote count :)

Should the upvotes show this concept would help a lot of you, I'll work up the UX details and a template for filing the Feedback, which we can all copy-paste-submit and be loud enough to get Apple's attention about this feature. We can all end up with cleaner lists of containers (yay) and all the containers can still be there, which I suspect Apple will have no qualm with.

This unexpected user experience has far reaching effects. It is bad enough that the Core Data / CloudKit frameworks are inherently fragile and need a total re-write, but it makes everyone scared to death to try anything they have none before in the XCODE IDE. I just ruined another project --- there are edge effects evidently to having more than one container -- it now destroyed my ability to properly query data from the other container. Went to uncheck the extra container (that caused the meltdown in what should have been unrelated areas of the project) and find that I can't. Worse, find that this problem has been documented here FOR FIVE YEARS. I tried to be loyal and tried to do an app that was going to be 100% Apple (CoreData, CloudKit) -- weaving through all the ridiculous code and coding and decoding between SwiftUI/CoreData/CloudKit just to sync a few measly data elements -- only to be kicked in the face by this amateurish (college professor theoretical data structures that don't work in the real world) joke for persistence management. (Which horrible architecture earlier today destroyed a slideshow in KeyNote I had to rebuild earlier today -- just because Finder and KeyNote cratered on an edge effect they had not architected to cover in a shared KeyNote file. Just showing that the Apple persistence/syncing architecture is not robust enough for serious commercial use.) I feel I have a bit of a right to rant about this -- as I have been programming since 1977!! What takes me a day to develop in this decrepit architecture took minutes to do back in the 1980's --- with 100's of concurrent users and absolutely no data loss in syncing and persistence. It is like somehow all the great knowledge we had back in the 1980's got flushed down the toilet and had to be relearned by another generation. Anyway -- I have about had it with ignoring bugs for FIVE YEARS. Sorry, once again, for this useless rant that won't go anywhere.

New Year Eve 2021 and still no change. Maybe 2022 will be better :(— i_Joe less than a minute ago 

January 3rd 2022, still not able to delete containers

jan 9, 22 ....

Jan 14, 2022. Is deleting containers supported now? At least, we need the ability to delete the containers that are not deployed to production.

still Fev 22 2022