“file uri scheme”

I'm having some issues with SwiftUI's SignInWithAppleButton's signInWithAppleButtonStyle. I am trying to change the color of the button based on the user's current scheme or if it changes. This is iOS 14 and SwiftUI: @Environment(.colorScheme) var currentScheme @State var appleButtonWhite = false VStack{ SignInWithAppleButton( tttttttt.signUp, ttttttttonRequest: { request inttttttt ttttttttttrequest.requestedScopes = [.fullName, .email] tttttttt}, ttttttttonCompletion: { result in ttttttttttswitch result { ttttttttttcase .success (let authResults): ttttttttttttprint(Authorization successful.) ttt ttttttttttcase .failure (let error): ttttttttttttprint(Authorization failed: + error.localizedDescription) tttttttttt} tttttttt} tttttt) tttttt.frame(minWidth: 0, maxWidth: .infinity) tttttt.signInWithAppleButtonStyle(appleButtonWhite ? .white : .black) } .onChange(of: currentScheme, perform: { (scheme) in ttttif scheme == .light tttt{ ttttttappleButtonWhite = false tttt} ttttelse tttt{ tt

It seems that apps, which are generated with the latest version of Xcode, generate EXC_BAD_ACCESS when the iOS app is called by url-scheme. Do you have the same issues or any workaround?Steps to reproduce:1) Compile an app with an url-scheme2) call this app from e.g. Safari by using myapp://openThe app opens and then crashes with EXC_BAD_ACCESS

I have a project that builds 5 binaries from 5 different schemes. Building each one of them separately takes around 2 minutes, with a large part of time spent on linking (lto I guess). I have a dummy target that builds all of them in parallel - I never managed to successfully build it, it goes on for 40-50 minutes and I just lose patience. What happens is, all the compilation is done ok, but when linking starts, 10 linker processes are spawned (5 binaries x 2 architectures) and they seem to never finish. While they are running, top shows a kernel_task using a lot of cpu (>100%) and the instances of ld using around 20-30 each. This is all happening on m1 macbook air 8/256. My guess is that it is a combination of RAM pressure, thermal throttling and the OS aggressively shuffling the 10 processes over the 8 cores, leading to lots of cache misses and possibly swapping. Is there any workaround I can apply - possibly some xcode setting to limit parallel jobs to 4-6 or something like that.