I have been dealing with this very issue for a week now and Apple hasn't fixed it yet. Anybody on the same boat?Norway, Australia, and Switzerland are each showing an empty drop down menu.

I have the same exact problem. Missing prices for Australia, Switzerland, and Norway. I contacted Apple 4 days ago and they still haven't resolved the issue and won't provide an ETA.

Same here. I've also tried signing the .pkg with a newly installed certificate to no avail. Any luck on your end?

The following worked for a developer apparently, but not for me: Code Signing a Package For the first issue, I originally thought it was questioning which certificate I used to sign the app. My code signing of the app was correct, it was code signing the package file which I forgot to do. I logged into the Apple Developer portal and created a new Mac Installer Distribution certificate which I could use to properly sign the pkg file. Once I had the new certificate, I then built and signed the package: productbuild --component ./Permanent\ Eraser.app/ /Applications/ PermanentEraser.pkg --sign "3rd Party Mac Developer Installer: John Doe (12AB34567C)" Source: edenwaith.com

I called supporting but they just pointed me to the documentation. Not very helpful.

support

Just out of curiosity, are you running MacOS Big Sur Beta 3?

Upgrading to MacOS Big Sur Beta 4 did not help unfortunately. I might revert back to Catalina..

I downgraded from MacOS Big Sur Beta to Catalina and the issue went away.

Can you clarify on why a CKSubscription is needed? [Scenario A] User A shares a list of tasks with user B through a CKShare. User B gets access to the CKShare record and any modification made by user B is done directly to the CKShare object which represents a reference to the list of tasks of user A. The same applies to modifications made by user A -- they would be directly reflected on the CKShare record. Why would I need a CKSubscription in this case? [Scenario B] The only scenario where a CKSubscription would be needed is if CKShare is copied over to user B's Core Data/CloudKit. Then I would implement a CKSubscription to notify the Core Data object on user B's end of any change to CKShare and vice versa. What does Apple recommend: Implementing A or B?

Hi @DTS Engineer thank you for your reply. I have already reviewed the sample code prior to asking my question and it's also worth mentioning that I have implemented various compositional layout configurations with section headers without any problem. However, when I attempted to implement this specific configuration (Kanban), I ran into issues with the headers. To clarify, I don't want the headers pinned, I want them to be on top of the content and scoll with the reste of the content when I scroll up and down, just like they would in a tableView. I would appreciate some insights. Thank you.