Updating to Xcode Version 12.2 fixed this for me. I am also running BigSur, but not sure if that had any influence. Good luck with it.

Updating to Xcode Version 12.2 fixed this for me. I am also running BigSur, but not sure if that had any influence. Good luck with it.

Updating to Xcode Version 12.2 fixed this for me. I am also running BigSur, but not sure if that had any influence. Good luck with it.

It is so comforting to know we are not alone... I filed a feedback for this issue on 21 Sep and have been longing for the day to see the back of this issue.

iOS 14.2 updat installed and alert (as mentioned originally) has stopped. Everything is working normally now.

Xcode 12 beta 2 has also fixed the issue with the disappearing button. If the ToolbarItem wraps the button, they can be position in their expected positions and remain in place despite tapping either button. Now, all that remains to be fixed is the "normal" toolbar implementation. Both buttons can be placed within the #if block if desired without affecting functionality.             .toolbar {                 #if os(iOS)                 ToolbarItem(placement: ToolbarItemPlacement.navigationBarLeading) {                     EditButton()                 }                 #endif                 ToolbarItem(placement: ToolbarItemPlacement.navigationBarTrailing) {                     Button("Add", action: makeSandwich)                 }             }

Xcode 12 beta 2 now "acknowledges" the Edit button in the above code as a tool bar item (at the top of the view) but persists to render the Add button at the bottom of the view. Whether the two buttons are located within the #if block or note, matters not a jot. Furthermore, all buttons remain in view despite tapping on either one. This is progress in the correct direction.

It seems that the mis-alignment feature is fixed with Xcode 12 beta 2. 😌

@bfad I have also seen this message regarding similar iOS 14 features that run fine on the beta simulators (running iOS 14). The corresponding macOS features, intuitively, will be designed for BigSur. You rightly point out 10.16 < 11 and I am guessing that for this reason, there is an incompatibility and hence the reason the macOS cannot find the member onOpenURL. I hope that helps.

What does “Debug with your extension’s scheme directly to Simulator” mean?

Thank you very much for your reply.

Commenting the widgetURL modifier does indeed "fix" the issue. Looking forward to see this working.

Ok, this issue was resolve by as follows. First a getCaffeineAmount method is created in the CaffeineAmountView:     func getCaffeineAmount(_ mass: Measurement&lt;UnitMass&gt;) -> String {         let measurementFormatter = MeasurementFormatter() &#9;&#9;&#9;&#9;measurementFormatter.unitOptions = .providedUnit         return measurementFormatter.string(from: mass)     } Then from the main VStack in the same struct, instead of the Text view, Text(measurementFormatter.string(from: data.caffeineAmount)) the following method call is made from a Text view: Text(getCaffeineAmount(data.caffeineAmount)) Any suggestions are welcome, regarding a different approach as I am certain there are many.

Thank you for your reply. The videos did appear at the time of broadcast, but for planning purposes it wasn't possible to set a schedule to watch a particular track of events as WWDC was unfolding. I am thinking that would have been possible at an in person event, so that one could focus on a particular technology or set of technologies. Now, the exercise is straight forward as the content is available on demand.

I also verify that when tapping the Add button the Edit button disappears, regardless of whether the buttons are within the #if os(iOS) block or not. It does suggest a disparity between the demo and reality.