Posts

Post not yet marked as solved
5 Replies
What is the real technical reason(s) why non-macOS platforms don't support nested frameworks? Being able to supported nested frameworks in iOS & tvOS would make my life as a framework developer a lot easier.
Post not yet marked as solved
2 Replies
I've just confirmed that this error does not occur in iOS 14.3 or 15.0 beta simulators; it seems to be isolated to iOS 14.5.
Post marked as solved
25 Replies
The previous two suggestions (removing an empty runtime environment variable) worked for me. This appears to be a variable that's generated by Xcode, not something that I accidentally added.
Post not yet marked as solved
13 Replies
Same thing happens to me when attempting to run an iOS app, written 100% in SwiftUI (if that makes a difference), with a target of "My Mac (Designed for iPad)." It worked fine for the first few days, but now I get the same error. I've restarted, deleted Derived Data, cleared the cache, and all the usual jazz. It will build and run without errors on a physical iPhone X. MBP M1 2020, Big Sur 11.1, Xcode 12.4.
Post marked as solved
2 Replies
It's amazing that these instructions aren't shown directly on Xcode's Devices and Simulators, and instead are buried deep in the Help system - https://help.apple.com/xcode/mac/11.4/index.html?localePath=en.lproj#/devbc48d1bad. There's not even a link to that documentation from the Devices and Simulators panel.
Post not yet marked as solved
2 Replies
I've found that I can safely ignore this error, and recognition will continue.
Post not yet marked as solved
3 Replies
Are you running the app in the background? I can successfully record continuous speech for at least 50 minutes (in 1-minute chunks), but only if there aren't any long periods where no speech is recognized, like long pauses in a lecture.
Post not yet marked as solved
2 Replies
I know that this is an old question, but in case anyone stumbles across it, note that this error doesn't happen only when the app is backgrounded. My speech recognition code works perfectly fine in an ordinary Swift app, but when I tried to use it in a new SwiftUI app, I get this 1700 error immediately at startup (in the simulator).
Post not yet marked as solved
5 Replies
I get the same error, but only when BuddyBuild tries to compile it. As far as I know, BuddyBuild uses the same schemes that I've checked into the project, and my schemes are not trying to build for Catalyst.