In my case I was listening for keyboards notifications and making it part of the environment. For some reason this caused consternation with textfields in general nested deeply in views. This includes searchable(). I took it out of the environment and all was well. Quite obvious swiftui is still riddled with bugs.

Yah, same here on a new release of my app. I did add a new screen that has a list but waits for the user's location before adding another list that sorts based on location. I can't reproduce the issue. No reports about it. This stack trace tells me zilch. Crashed: com.apple.main-thread 0 SwiftUI 0xc6116c OUTLINED_FUNCTION_4 + 7004 1 SwiftUI 0xc5fb4c OUTLINED_FUNCTION_4 + 1340 2 SwiftUI 0x1a3254 OUTLINED_FUNCTION_1 + 8876 3 SwiftUI 0x72e1f8 OUTLINED_FUNCTION_4 + 15576 4 SwiftUI 0x72c1cc OUTLINED_FUNCTION_4 + 7340 5 SwiftUI 0x72c31c OUTLINED_FUNCTION_4 + 7676 6 SwiftUI 0x1a1d24 OUTLINED_FUNCTION_1 + 3452 7 SwiftUI 0x1a1aac OUTLINED_FUNCTION_1 + 2820 8 SwiftUI 0x1a2d1c OUTLINED_FUNCTION_1 + 7540 9 SwiftUI 0xde5554 OUTLINED_FUNCTION_31 + 4520 10 SwiftUI 0x8562a8 OUTLINED_FUNCTION_0 + 9204 11 SwiftUI 0x8559b4 OUTLINED_FUNCTION_0 + 6912 12 SwiftUI 0x191fbe8 OUTLINED_FUNCTION_0 + 13676 13 SwiftUI 0x191fc28 OUTLINED_FUNCTION_0 + 13740 14 libswiftCore.dylib 0x4c100 withUnsafeMutablePointer<A, B>(to:_:) + 28 15 SwiftUI 0x191fa7c OUTLINED_FUNCTION_0 + 13312 16 SwiftUI 0x191f6a4 OUTLINED_FUNCTION_0 + 12328 17 SwiftUI 0x1327b0c __swift_allocate_boxed_opaque_existential_1Tm + 268 18 AttributeGraph 0xb854 AG::Graph::UpdateStack::update() + 512 19 AttributeGraph 0x2504 AG::Graph::update_attribute(AG::data::ptr<AG::Node>, unsigned int) + 424 20 AttributeGraph 0xcf58 AG::Subgraph::update(unsigned int) + 848 21 SwiftUI 0xe0627c OUTLINED_FUNCTION_15 + 26384 22 SwiftUI 0x187f3d8 OUTLINED_FUNCTION_2 + 20040 23 SwiftUI 0x187cd18 OUTLINED_FUNCTION_2 + 10120 24 SwiftUI 0x7a1900 OUTLINED_FUNCTION_101 + 17408 25 SwiftUI 0x18ea690 OUTLINED_FUNCTION_9 + 35076 26 libdispatch.dylib 0x26a8 _dispatch_call_block_and_release + 32 27 libdispatch.dylib 0x4300 _dispatch_client_callout + 20 28 libdispatch.dylib 0x12998 _dispatch_main_queue_drain + 984 29 libdispatch.dylib 0x125b0 _dispatch_main_queue_callback_4CF + 44 30 CoreFoundation 0x3720c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 31 CoreFoundation 0x33f18 __CFRunLoopRun + 1996 32 CoreFoundation 0x33668 CFRunLoopRunSpecific + 608 33 GraphicsServices 0x35ec GSEventRunModal + 164 34 UIKitCore 0x22c2b4 -[UIApplication _run] + 888 35 UIKitCore 0x22b8f0 UIApplicationMain + 340 36 SwiftUI 0x11620fc OUTLINED_FUNCTION_31 + 604 37 SwiftUI 0x1161f40 OUTLINED_FUNCTION_31 + 160 38 SwiftUI 0xdd3868 OUTLINED_FUNCTION_26 + 2196 39 Checklist 0x867d4 main + 4340606932 (ChecklistApp.swift:4340606932) 40 ??? 0x1b20fadcc (Missing)

@alex_jac Did you figure this out?

@anhdo Same problem. Any resolution?

I didn't save the token or secret as well cause I didn't know I needed them. Now apparently we need them. What are we to do? Log the user out and log them back in to get a new token? Apparently we have to call the endpoint to log them out. I have been doing some experimenting with that, and now saving the secret/token. I am calling the endpoint, and it returns a 200, but the credentialRevokedNotification notification is not fired. I believe I am doing it right based on the doc which is frustrating. I've called hundreds of endpoints so I know what I am doing. I think my problems maybe related to the client_secret though. There seems to be a process behind that which I am looking into. client_secret string (Required) A secret JSON Web Token (JWT) that uses the Sign in with Apple private key associated with your developer account. For more information about creating client secrets, see Generate and Validate Tokens. Note, not sure how this is possible via an app. Seems more like a process for a website using sign in. Apple should have given us a sign out button like they have in the phone settings and and on the appleid site. They didn't think about this and now a bunch of us are going to get screwed somehow.

@ben_singaccord Did you find away around this?

Same problem. Anyone?

This seems to happen with navigating in presented views. Legit bugs.

Take a look at https://github.com/tikhop/TPInAppReceipt

Yeah, the DTK bricked on 11.0.1B. Ready box it up and send it back. nah, I will try to restore it.