User Profile

Posts

Posts

Post not yet marked as solved
4 Replies
Replied In lost connection to the debugger on my mac
This is happening to me as well. A few additional details: Running Monterey with Xcode 12 and Xcode 13 beta 1 installed. Everything was working, I could do my normal work in Xcode 12, but still play around with new features in Xcode 13. Everything worked great. I installed Xcode 13 beta 2, which also included an install of the command line utilities. This is when the problem started, Xcode 12 could no longer use the debugger and I had to disable it in the scheme to at least test on the simulator. I tried reinstalling the command line tools for Xcode 12 thinking it would help, but it didn't. Debugger works fine on Xcode 13, but I can't do production work there since the app would not be approved on the App Store.
Post not yet marked as solved
8 Replies
Replied In PhysicsBody: Could not create physics body.
I struggled with this for awhile as well. Tried setting the mask in the scene editor or programitcally and both had the same issue. I then decided to add a 2x and 3x image to the project which was never required for SpriteKit textures in the past and everything started working.
Post not yet marked as solved
43 Replies
Replied In SwiftUI - NavigationLink inside NavigationBarItems, returns error on navigating from detail back to master view
My workaround is pretty horrible where the child basically forces the parent to repaint. This introduces other small issues if the navigation is triggered via a link. Since this issue happens with a brand new project with no modifications to the Master / Detail template I am hopeful it could get addressed quickly.
Post not yet marked as solved
43 Replies
Replied In SwiftUI - NavigationLink inside NavigationBarItems, returns error on navigating from detail back to master view
On 13.3 this no longer crashes and will return to the root view when back is tapped, but now I am not longer able to navigate back to the chold view. So no crash good, still a broken UI bad.I've also tried other suggestions with NavigationLink and displaying with the isActive property, but the same result happen where I end up on the root view and can never return to the child view.Quick update... The default Master / Detail Projedct Template from xCode suffers from this issue. I get this is a new technology, but when the default code prodived by the IDE has the issue it makes me wonder if there is any QA process. If there is only one row in the table the issue happens, but if you add two rows then the app behaves as you'd expect.