“show when run”

I also registered for a personal developer account for more than 5 days now, and I have a case opened with apple but account status still showing pending, and I see a place where its showing I need to complete purchase, as if to pay again! I heard nothing from Apple till now.

I also registered for a personal developer account for more than 5 days now, and I have a case opened with apple but account status still showing pending, and I see a place where its showing I need to complete purchase, as if to pay again! I heard nothing from Apple till now.

Running into this as well, 401s on Restriction None Mapkit JS tokens generated on https://developer.apple.com/account/resources/services/maps-tokens Failed to load resource: the server responded with a status of 401 (Unauthorized) There seems to be a mismatch some where because all of my tokens get a 401 even with Restriction None.

Works for me. It would most likely be related to the dump files bit though, as the script has finished running after the folder is created. Unless this is a part of something larger, in which case you would need to provide more information.

The remaining issue is isPagingEnabled. When paging is enabled, UICollectionView applies its own content offset snapping inside layoutSubviews(), which conflicts with your layout's contentOffsetAdjustment from invalidationContext(forBoundsChange:). During rotation the two corrections compound, leaving the offset between pages. This is why your layoutSubviews() workaround fixes it — it runs last and gets the final word. The fix is to disable isPagingEnabled and let the layout handle paging entirely. Your layout already corrects the offset during invalidation. The one piece you lose is scroll deceleration snapping, which you can replace with the velocity-aware variant: override func targetContentOffset( forProposedContentOffset proposedContentOffset: CGPoint, withScrollingVelocity velocity: CGPoint ) -> CGPoint { guard let collectionView, collectionView.bounds.width > 0 else { return proposedContentOffset } let pageWidth = collectionView.bounds.width let currentOffset = collectionView.contentOffs

Hi Ziqiao, thanks for looking into this. I'll answer your question about our share flow, then share some significant findings from today's debugging. We use a custom token-based invite flow rather than the standard system share URL tap → userDidAcceptCloudKitShareWith path. Here's the full flow: How we deliver the share URL Owner creates an invite token — stored as an InviteToken record in the public CloudKit database. The token record contains the CKShare.url string, the household ID, and a 7-day expiration. Owner sends a deep link — the invite UI generates a mesa://invite?token= URL and presents a share sheet (Messages, AirDrop, etc.). This is a custom URL scheme, not the CKShare.url directly. Participant opens the deep link — the mesa:// URL opens our app. The app extracts the token, queries the public database for the InviteToken record, and reads the shareURL field to get the CKShare.url. How we accept the share (programmatic path) Once we have the CKShare.url from the token lookup: // 1. Fetch share met