Posts

Post not yet marked as solved
0 Replies
113 Views
My app has a view that appears from a NavigationLink. The view has a list and a search bar; when a user taps the search bar the keyboard appears correctly. BUT, the entire view, including the navigationBarTitle and the navigationBarBackButton, move upward. This causes the navigationBarTitle and the navigationBarBackButton to move under the notch, where the back button doesn't work. To use the back button the user has to dismiss the keyboard with the return key, which moves the navigationBarTitle and back button downward and then tap the back button. This cannot be an uncommon situation, but I've spent the morning trying to find a way to prevent the NavigationBarTitle and <back button from moving upward where the user can't use the <back button when the keyboard appears. Is there a way to too that?
Posted
by jzumsteg.
Last updated
.
Post not yet marked as solved
0 Replies
174 Views
My app uses the AVFoundation to pronounce some words. Running the app from Xcode, either to a simulator or device, I frequently get this crash at start-up: AXSpeech (13): EXC_BAD_ACCESS (code=EXC_I386_GPFLT). It seems to occur randomly, maybe 20%-30% of the time I launch the app. When it does not crash, using audio works as expected. When launched from the device, it never crashes (so far, at least). Here's the code that outputs speech: Declared at the top level of the View struct: @State var synth = AVSpeechSynthesizer() In the View, as part of a Button's action closure: let utterance = AVSpeechUtterance(string: answer) utterance.voice = AVSpeechSynthesisVoice(language: "en_US") synth.speak(utterance) Any idea on how to stop this? It's annoying having to launch the app multiple times to test on a simulator or device.
Posted
by jzumsteg.
Last updated
.
Post not yet marked as solved
0 Replies
157 Views
My app uses the AVFoundation to pronounce some words. Running the app from Xcode, either to a simulator or device, I frequently get this crash at start-up AXSpeech (13): EXC_BAD_ACCESS (code=EXC_I386_GPFLT). It seems to occur randomly, maybe 20%-30% of the time I launch the app. When it does not crash, audio works as expected. When launched from a device, it never crashes (at least, so far). Here's the code that outputs speech: Declared at the top level of the View struct @State var synth = AVSpeechSynthesizer() In the View, as part of a Button's closure: let utterance = AVSpeechUtterance(string: answer) utterance.voice = AVSpeechSynthesisVoice(language: "en-US") synth.speak(utterance) Any idea on how to stop this? It doesn't stop development, but sure slows it down, requiring multiple app starts often.
Posted
by jzumsteg.
Last updated
.
Post marked as solved
14 Replies
14k Views
I'm working on several apps that were developed on Xcode 12.5. Using Xcode 13.1, I set a breakpoint, which correctly appears as the blue marker in the left-hand column of the editor. When I run the apps (in a simulator), the breakpoint turns to an outline of a breakpoint marker, with a dotted blue outline and a white interior. The apps do not stop at the breakpoint. Breakpoints work as expected on an app started in Xcode 13.1. I've dug through the docs but find nothing that describes what the outline breakpoint means or how to make it work. I've done all the standard stuff: cleaned the build folder, deleted derived data. What does the outline breakpoint marker mean, and how do I get breakpoints working in Xcode 13.1 when debugging code developed originally on Xcode 12.5? Thanks in advance for any help. John
Posted
by jzumsteg.
Last updated
.
Post marked as solved
10 Replies
3.8k Views
I have an app that uses a local git repository. Until today I've had no trouble with git functionality. Today, trying to commit the project, Xcode hangs with the spinning beach ball as soon as the commit window appears. If I try to commit an individual file, it appears to start the commit (that is, it takes a comment), but hangs with a message "Committing..." in the lower-right hand corner.My git expertise is limited to using it within Xcode and some basics from the command line. I'd appreciate any insights and advice on how to get it working in Xcode again.Thanks,John
Posted
by jzumsteg.
Last updated
.
Post not yet marked as solved
3 Replies
1.2k Views
I have a small app written in Swift 4.2 that runs on iOS 11 and 12 (and the iOS 13 beta). Its iOS Deployment Target (in Build Settings) has been 11.0. Recently I decided to try to expand it back to run on iOS 9 and 10. I set the deployment target to iOS 9.3, made necessary code changes (using "if #available..."). The app compiles, but when I try to run it on a iOS 9.x or iOS 10.x simulator, it fails.Running it in any 9.x simulator gives me a dialog box saying, "The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died)". I do not have a iOS 9.3 device handy, so I can't say what the behavior would be on a real device.Running it in any 10.x simulator, the simulator starts, and then I get a "Thread 1: EXC_BAD_ACCESS" crash. I get the same message when running on a iOS 10.3.3 device.I don't expect anyone to debug these problems for me, but does anyone have any experience trying to expand an app's target back to earlier versions and have any insight into where I could start to track down these problems? Or am I in a futile mission? I've dug through every link I can find on the Mach error -308 but have found no fixes that work for me.Any and all help will be greatly appreciated!
Posted
by jzumsteg.
Last updated
.