Thank you for your response. I eventually found an alternative solution at  https://bitbucket.org/blog/deprecating-atlassian-account-password-for-bitbucket-api-and-git-activity. Essentially, all I needed to do was to create an app password and enter it into the Xcode account for the Bitbucket repository. This seems to be the least disruptive solution, but I was unable to find it during my first search into the Bitbucket literature.

We are in the same position. After several months of wrangling with App Store Review, we finally had our app (with IAPs) approved in January. We recently submitted an update (without any changes to StoreKit functionality), which was rejected for the same reason. Fortunately, we had some instrumentation which pointed explicitly to a failure to refresh the receipt. In retrospect, it seems that our initial success was a stroke of luck. (1) I agree with zixtix. There is no consistency in the reviewers' process. Furthermore, they offer no explanation on their specific actions (e.g., did they press the Cancel button on the sign-in dialog?). This type of information would be greatly helpful. (2) If I hadn't found this Forum thread, we would still be stuck. Apple needs to present these requirements more prominently in the overall Human Interface guidelines. (3) As an independent developer, my primary job should be to bring my client's vision to reality, not navigate the arcane details of the App Store. Over the past 2 years (yes, on this single project) I have read through scores of tutorials, documents and threads to piece together a basic understanding of StoreKit and how to use it. It would be tremendous if Apple would provide a single source for everything relating to the App Store. (4) Having to insert a considerable amount of code, simply to pass App Store Review, seems a waste of any developer's time (and client's money).

I've received the same error, but related to 'com.app.developer.icloud-container-identifiers', even though I haven't touched iCloud in over a year. So I think that the problem is more general than HealthKit.

I saw this identical problem on App Store Connect from my Macbook Pro (Catalina) and Safari. When I logged in from my Windows PC and Edge, everything was displayed correctly. I can't see the logic to this, since both browsers are presumably simply displaying an HTML page.