Post not yet marked as solved
This is still happening in Xcode 13.2.1. i have 2 intents generating a total of 80 warnings all of the "Multiple declarations found and ignored" variety.
Can someone else on this thread confirm?
Post not yet marked as solved
Thanks for the reply! That makes a lot of sense. After some testing i can confirm this is indeed the behavior:
Given an uninterrupted WiFi connection, the currentPath remains .unsatisfied after the App is launched until the first invocation of pathUpdateHandler (which happens right away); it then transitions to .satisfied. The first invocation seems more like the initial state vs. a changed state.
i.e. the first invocation it is not an indication that network availability has truly changed (which was my initial assumption).
Post not yet marked as solved
It is both bizarre and disappointing to see Apple make a splashy announcement in the Keynote (and the session on Wallet) on Home Keys without providing any documentation to developers.
InstantInteractive, it is easy to get around not being able to customize the return key type on a keyboard:
You simply create a UIViewRepresentable that wraps the good old UITextField we have come to know and love; it sucks to have to do it this way but at least there is a workaround. For some of the other issues i mentioned in my initial reply, there is no workaround.
Don't get me wrong, SwiftUI is here to stay and is indeed the future and when things work, it's magic. i can understand it having bugs when it was first released in iOS 13, but glaring issues and feature omissions remain in iOS 14 as well.
i would strongly caution against proceeding full-on with SwiftUI, it is just plain broken in a lot of places. The list of things that don't work in SwiftUI seem to grow the more you use it.
For instance, SwiftUI does not offer a pull to refresh feature (a deal breaker for me). SwiftUI provides no way of customizing the return key type on a keyboard. Keyboard support in general is just lacking, there is no way to set a first responder and no way to resign a first responder.
Using UIHostingController to bridge UIKit code to SwiftUI leads to other issues like Lists not behaving as they should (NavigationLinks will remain highlighted after you return from the Detail View). And the list goes on and on.
Mattes,
i have the exact same problem although my intents are implemented using in-App Intent Handling (new in iOS 14).
i learned that if i turn the Show When Run option OFF for the shortcut, Siri will no longer speak the custom success responses, it will only say things like "Done" or "OK". Turning the Show When Run option ON makes Siri speak the custom success responses.
This behavior is acceptable if the intents are performing an action and "Done" or "OK" will suffice to let the user know that the request was competed. However, it defeats the purpose if your intent is returning information that the user requested. e.g. "When will my package be delivered?"
Post not yet marked as solved
Using Xcode 12.2 and this still happens. Xcode crashes if i tick another language.
Post not yet marked as solved
AlertBridge is not a class of mine. Strangely, the stack trace reported by Crashlytics does not have any of my code. Here is the complete stack trace. Again, none of the classes seen in the stack trace are mine.
0	SwiftUI												0x1c9bf3ae8 AlertBridge.preferencesDidChange(_:) + 2604
1	SwiftUI												0x1c97eb474 _UIHostingView.preferencesDidChange() + 412
2	SwiftUI												0x1c98b92cc ViewGraph.updateOutputs(at:) + 180
3	SwiftUI												0x1c9b58e10 closure #1 in closure #1 in ViewRendererHost.render(interval:updateDisplayList:) + 816
4	SwiftUI												0x1c9b582b0 closure #1 in ViewRendererHost.render(interval:updateDisplayList:) + 524
5	SwiftUI												0x1c9b4f1b8 ViewRendererHost.render(interval:updateDisplayList:) + 316
6	SwiftUI												0x1c9c75748 _UIHostingView.layoutSubviews() + 160
7	SwiftUI												0x1c9c75774 @objc _UIHostingView.layoutSubviews() + 24
8	UIKitCore											0x195f657fc -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 2144
9	QuartzCore										 0x198509494 -[CALayer layoutSublayers] + 284
10 QuartzCore										 0x19850f5ec CA::Layer::layout_if_needed(CA::Transaction*) + 468
11 QuartzCore										 0x19851a128 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 140
12 QuartzCore										 0x198462b44 CA::Context::commit_transaction(CA::Transaction*, double) + 296
13 QuartzCore										 0x19848c4e4 CA::Transaction::commit() + 676
14 UIKitCore											0x195ada9d0 _afterCACommitHandler + 140
15 CoreFoundation								 0x19197af2c CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION + 32
16 CoreFoundation								 0x191975e20 __CFRunLoopDoObservers + 420
17 CoreFoundation								 0x19197629c __CFRunLoopRun + 968
18 CoreFoundation								 0x191975ba8 CFRunLoopRunSpecific + 424
19 GraphicsServices							 0x19baec344 GSEventRunModal + 160
20 UIKitCore											0x195ab13e4 UIApplicationMain + 1932
21 Kevo													 0x1029d1418 main + 17 (main.m:17)
22 libdyld.dylib									0x1917fd8f0 start + 4
