Appreciate the quick response! I think what's really confusing is that the comment in the code for (as an example) lowTemperateTime says "The time at which the low temperature occurs on this day." But the answer returned isn't a date on that day. I can add some code around this now that I know it's expected. Thank you!

I'm still experiencing it also. Just tried a test to see if it was fixed in iOS 18.2 but it's not.

I decided to not use .simultaneousGesture and keep gesture support disabled for the moment. The problem is that with Swift Charts you can long press and reveal a RuleMark. The problem is that while I RuleMark is revealed the user can drag to reveal the RuleMark values for other entries in the chart. That is triggering my drag logic. As with scrolling, this was not a problem with iOS 17.

Same behavior in the RC. I'm going to have to disable gesture support in my app until I can find a way around this problem.

Thank you for responding. I actually was already using .accessibilityAddTraits(.isToggle). You can see it in the code I included. The issue was that with iPadOS 18 VoiceOver was always saying that my toggle was off when iPadOS 17 was not doing that. I filed FB15045849 about the documentation as requested.

Thanks for responding! That doesn't work for me in tinted mode. This results in an all white symbol. Image(systemName: "sun.horizon.fill") .symbolRenderingMode(.multicolor) This results in an all tinted symbol. Image(systemName: "sun.horizon.fill") .symbolRenderingMode(.multicolor) .widgetAccentable() This also results in an all tinted symbol. Image(systemName: "sun.horizon.fill") .symbolRenderingMode(.multicolor) .widgetAccentable() .foregroundStyle(.white, .tint)

Perfect. I'll just change my max of 100m away to 111m and I'll be done. Thank you for the answer!

Will do! No change with Version 16.0 beta 4 (16A5211f).

Thank you Kevin. I really appreciate you responding so quickly. I need to think about how I'm going to handle this.

Thanks for doing that! I had already included similar screenshots in my feedback.

No. I had another developer verify they are seeing this issue also, but I haven’t received any response to this inquiry. i’d recommend also opening feedback so they know another person is experiencing this.

Contact developer support. They reached out to the dept that handles subscription review and eventually mine were approved after that.

Filed FB11980600

I want to profusely thank you for sharing these tips AND for putting that section in bold. It's what finally made me realize that I only had it enabled in one of the tabs.

Thank you so much for sharing this. I opened a TSI and was told to open feedback for a bug. This fixed my widget that was working fine when I last built it for iOS 15.