User Profile

Posts

Posts

Post not yet marked as solved
9 Replies
Replied In Can't run/debug on iOS 14 using Xcode 12.0 or 12.2 using Big Sur Beta 7?
Just wanted to give an update to anyone still experience a similar problem. Updating to iOS 14.0.1 (iPadOS for me) fixed the problem for me. I'm also on Big Sur Beta 8, but before updating to iOS 14.0.1 it wasn't working.
Post not yet marked as solved
9 Replies
Replied In Can't run/debug on iOS 14 using Xcode 12.0 or 12.2 using Big Sur Beta 7?
Yes, that's exactly what I'm seeing. I didn't let it sit long enough to know that it would run after a while. It's nice to know that I'm not the only one experiencing this problem. I can't figure out a solution though 😔 I'm tempted to install iOS 14.2 to see if that will work like it used to.
Post marked as solved
1 Replies
Replied In iOS 13.1 Swift Playgrounds not saving?
Not sure what the problem was, but it seems to have been fixed with the Swift Playgrounds 3.1 release.
Post marked as solved
5 Replies
Replied In How do you pass SwiftUI Bindings to other objects in iOS 13 Beta 4?
After spending way too much time on this issue, I happend upon a stackoverflow post on twitter that showed the new syntax for beta 4.https://stackoverflow.com/questions/56973959/swiftui-how-to-implement-a-custom-init-with-binding-variablesWhen initializing a binding variable, the syntax has changed from a $ to an underscore.Using the example you gave in the original post, here's the corrected code for beta 4:public struct CoolListRow : View { @Binding var currentStep: Int public var body: some View { // ... } public init(currentStep: Binding<Int>) { self._currentStep = currentStep } } Hope this helps.
Post marked as solved
5 Replies
Replied In How do you pass SwiftUI Bindings to other objects in iOS 13 Beta 4?
I thought it was just me (and probably spent way too much time deciding if it was or not), but I'm wondering if you're still having issues. Your solution allows your problem to compile, but I don't believe it's correct?When using @Binding it's possible to use the variable as if it were a regular variable, such as: @Binding var isPlaying: Bool isPlaying.toggle()But if we change the type as suggested, we have to use the variable by first going through value:var isPlaying: Binding<Bool> isPlaying.value.toggle()Are you having any additionally issues like I mentioned after making the changes that you've suggested?