On occasion, Swift Charts draws a large pink rectangle over the entire chart area as shown in the screen shot below. I have never been able to reproduce this issue consistently, so I do not know if it is an issue with the data I input into the chart, or an Apple bug. It happens only rarely, for one redraw cycle, then the chart returns to the correct display. Has anyone experienced this issue, and if so, what was the source of the problem and how did you resolve it?

Hi, When I attempt to join a lounge, I get an issue in slack "There's been a glitch" and it won't connect me to the lounge channel. How do I resolve this?

In Xcode 12 Beta 1 using StoreKitTest, when an auto-renewable subscription would renew, a new transaction would be sent to the payment queue observer, and the local, on-device receipt would be updated to reflect the new transaction. Additionally, when you would call the SKTestSession expireSubscriptionWithProductIdentifier method, the local receipt would be updated to include a subscription cancellation date field. In Xcode 12 Beta 2, this doesn't appear to be working properly. Renewals do not generate new transaction, nor is the local receipt updated. Further, expireSubscriptionWithProductIdentifier does not update the local receipt with a subscription cancellation date field. Is there any configuration setting, or default setting that could be configured to get this to work properly again - without waiting for a new beta version of Xcode?

With the removal of deep or firm press accessible menus and buttons from WatchOS 7, I was wondering what the recommended approach is for creating a button that responds to a deep or firm press in as close to an identical fashion as the menu button deep press gestures on WatchOS 6 and earlier? Is a long press gesture equivalent to deep press, or is there some set of gesture settings I could configure on a long press gesture to approximate a deep press as closely as possible? I'm working on a suite of WatchOS applications where typical button presses (tap gestures) and screen swipes don't work reliably[1] (typically < 50% reliability, but often substantially less reliable than 50%) in the main application environment. [1] Reliability is the number of successfully registered gestures per physical gesture. For example, if it takes two physical button taps on the screen for the system to send the app a button tap action, that is 50% reliability.