Xcode 11 doesn&#39;t automatically add every possible simulator. But you can add an iPhone SE iOS 13 simulator.

In Xcode, click on the Window menu and select Devices and Simulators. Select the Simulators tab. Tap the + in the bottom-left corner. Give the new simulator a name. Select iPhone SE as the device type. Enter iOS 13 as the OS Version.

Now you have what you need.

**Edit:** This is still valid with XCode 12.3 and iOS 14.3 as of January 2020

Also can be useful. The problem may be in your project preferences. If downloading simulators didn&#39;t work, try this. Open you project in Xcode -&gt; Choose your project on the Navigator which is on the left side
[Navigator][1]


Then in the Deployment Info in target tab choose IOS version for your project (choose 10 or 11 for all simulator displaying)

[Deployment Info][2]


  [1]: https://i.stack.imgur.com/4iFfF.png
  [2]: https://i.stack.imgur.com/g77P9.png

I have following code in my AppDelegate.swift to setup root view controller for an iOS application. But it does not work. It follows Target structure (defined under General tab) and ignores this code.

(Xcode 11, Swift 5.1, iOS 13)

    class AppDelegate: UIResponder, UIApplicationDelegate {
        
        var window: UIWindow?
        
        func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {
            
            window = UIWindow(frame: UIScreen.main.bounds)
            guard let rootVC = UIViewController() else {
                print(&quot;Root VC not found&quot;)
                return true
            }
            let rootNC = UINavigationController(rootViewController: rootVC)
            window?.rootViewController = rootNC
            window?.makeKeyAndVisible()
      
            return true
        }
    }

Unable to understand where is the issue. 

I tried following references also but no luck:

   - [Swift ios set a new root view controller][1]
   - [Root View Controller Swift][2]
   - [iOS: Root Controller Navigation][3]


  [1]: https://stackoverflow.com/questions/33374272/swift-ios-set-a-new-root-view-controller
  [2]: https://stackoverflow.com/questions/31062108/root-view-controller-swift
  [3]: https://medium.com/@stasost/ios-root-controller-navigation-3625eedbbff

iOS 13: Swift - &#39;Set application root view controller programmatically&#39; does not work

I have been trying to make my project work with the new Xcode 11. Everything works smoothly, except on several occasions when I run my app on the simulator (iPhone 11 Pro Max), the app freezes after I click on EditTexts. This happens after a few times I have used the app. If I clear the simulator memory and restart everything works normally. 

I created a view controller with just the EditText and am able to replicate the simulator freezing. Sometimes it freezes before launching the soft keypad, sometimes after it has been displayed. I am still able to kill the app and rerun it through Xcode but it freezes every time unless I do hardware reset on simulator. 

I am just concerned if this would happen on the device too? Has anyone faced this? 

Edit: Just to add. When this happens, I try to use the messaging app and the same thing happens there. 

Keyboard gets stuck in ios 13 simulator

I&#39;m running Xcode 11.0 on macOS Mojave (10.14.6) and though the iPhone SE is [officially supported on iOS 13][1], it doesn&#39;t appear in the list of simulators.  

[![enter image description here][2]][2]

It can&#39;t be added nor downloaded, as far as I can see.  Any ideas?  


  [1]: https://support.apple.com/en-us/HT210327
  [2]: https://i.stack.imgur.com/rtlgE.png

Is there an iPhone SE simulator for Xcode 11, iOS 13?

I'm running Xcode 11.0 on macOS Mojave (10.14.6) and though the iPhone SE is <a href="https://support.apple.com/en-us/HT210327" target="_blank" rel="noopener noreferrer">officially supported on iOS 13</a>, it doesn't appear in the list of simulators.
<a href="https://i.stack.imgur.com/rtlgE.png" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/rtlgE.png" alt="enter image description here"></a>
It can't be added nor downloaded, as far as I can see. Any ideas?

I just downloaded iOS 13 for my iPhone and the new Xcode. I wanted to test my app for iOS 13, but when I try to run my app it will give me a error after a few seconds. Error: 

&gt; Terminating app due to uncaught exception
&gt; &#39;NSInternalInconsistencyException&#39;, reason: &#39;Modifications to the
&gt; layout engine must not be performed from a background thread after it
&gt; has been accessed from the main thread.&#39;
&gt; *** First throw call stack: (0x191ea9c30 0x191bc40c8 0x192395434 0x19218eb94 0x19218eaa8 0x19218e718 0x1963e6ea8 0x191bbfaf0
&gt; 0x198984384 0x19634fe54 0x19898468c 0x198997bf4 0x1988dd3e4
&gt; 0x1989083a0 0x198909388 0x191bbc3c0 0x191bb4dbc 0x191bb6de8
&gt; 0x191bb6b30 0x191bbcc78) libc++abi.dylib: terminating with uncaught
&gt; exception of type NSException

In iOS 12 and lower everything seems to be working and I won&#39;t get this error. Does somebody knows how to fix this error and what this error means?

Download ID:

    func Download_ID() {
        let urlString = &quot;https://www.instagram.com/\(self.username_String)/?__a=1&quot;
        guard let url = URL(string: urlString) else { return }
        URLSession.shared.dataTask(with: url) { data, urlResponse, error in
            guard let data = data, error == nil, urlResponse != nil else {
                print(error)
                return
            }
            do
            {
                let decoder = JSONDecoder()
                let downloadedData_user = try decoder.decode(Website.self, from: data)
                DispatchQueue.main.async {
                    self.profile_img_String = downloadedData_user.graphql.user.profile_pic_url
                    let Veri = downloadedData_user.graphql.user.is_verified
                    if Veri == true {
                        self.Verified!.isHidden = false
                    }else{
                        self.Verified!.isHidden = true
                        
                    }
                    self.Name!.text = downloadedData_user.graphql.user.full_name
                    self.username!.text = self.username_String
                    let url = URL(string: &quot;\(self.profile_img_String)&quot;)
                    self.profileImage!.kf.indicatorType = .activity
                    self.profileImage!.kf.setImage(
                        with: url,
                        placeholder: UIImage(named: &quot;image-placeholder.png&quot;),
                        options: [
                            .scaleFactor(UIScreen.main.scale),
                            .transition(.fade(0.4)),
                            .cacheOriginalImage
                    ])
                }
            } catch {
                print(error)
            }
        }.resume()
    }

Stack:
    

    Main Thread Checker: UI API called on a background thread: -[UIView setHidden:]
    PID: 4437, TID: 1560742, Thread name: (none), Queue name: NSOperationQueue 0x10440d330 (QOS: UNSPECIFIED), QoS: 0
    Backtrace:
    4   Instagram Profile                   0x00000001029c09bc $s17Instagram_Profile21History_TableViewCellC11Download_IDyyFyycfU_y10Foundation4DataVSg_So13NSURLResponseCSgs5Error_pSgtcfU_ + 1612
    5   Instagram Profile                   0x00000001029c10d4 $s10Foundation4DataVSgSo13NSURLResponseCSgs5Error_pSgIegggg_So6NSDataCSgAGSo7NSErrorCSgIeyByyy_TR + 284
    6   CFNetwork                           0x0000000195105ffc CFNetServiceBrowserSearchForServices + 95540
    7   CFNetwork                           0x00000001951168dc _CFHTTPMessageSetResponseProxyURL + 7680
    8   Foundation                          0x0000000192279c60 A99BF5C7-12EA-3700-8798-6522387A8A89 + 1170528
    9   Foundation                          0x000000019217b7e8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 129000
    10  Foundation                          0x000000019227bfbc A99BF5C7-12EA-3700-8798-6522387A8A89 + 1179580
    11  Foundation                          0x000000019217b464 A99BF5C7-12EA-3700-8798-6522387A8A89 + 128100
    12  Foundation                          0x000000019227c9e8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 1182184
    13  Foundation                          0x000000019227c4a8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 1180840
    14  libdispatch.dylib                   0x00000001042bda48 _dispatch_block_async_invoke2 + 144
    15  libdispatch.dylib                   0x00000001042af2a8 _dispatch_client_callout + 20
    16  libdispatch.dylib                   0x00000001042b2084 _dispatch_continuation_pop + 572
    17  libdispatch.dylib                   0x00000001042b1468 _dispatch_async_redirect_invoke + 628
    18  libdispatch.dylib                   0x00000001042c0aac _dispatch_root_queue_drain + 356
    19  libdispatch.dylib                   0x00000001042c1418 _dispatch_worker_thread2 + 144
    20  libsystem_pthread.dylib             0x0000000191bb6a60 _pthread_wqthread + 216
    21  libsystem_pthread.dylib             0x0000000191bbcc78 start_wqthread + 8
    2019-09-24 23:21:24.917645+0200 Instagram Profile[4437:1560742] [reports] Main Thread Checker: UI API called on a background thread: -[UIView setHidden:]
    PID: 4437, TID: 1560742, Thread name: (none), Queue name: NSOperationQueue 0x10440d330 (QOS: UNSPECIFIED), QoS: 0
    Backtrace:
    4   Instagram Profile                   0x00000001029c09bc $s17Instagram_Profile21History_TableViewCellC11Download_IDyyFyycfU_y10Foundation4DataVSg_So13NSURLResponseCSgs5Error_pSgtcfU_ + 1612
    5   Instagram Profile                   0x00000001029c10d4 $s10Foundation4DataVSgSo13NSURLResponseCSgs5Error_pSgIegggg_So6NSDataCSgAGSo7NSErrorCSgIeyByyy_TR + 284
    6   CFNetwork                           0x0000000195105ffc CFNetServiceBrowserSearchForServices + 95540
    7   CFNetwork                           0x00000001951168dc _CFHTTPMessageSetResponseProxyURL + 7680
    8   Foundation                          0x0000000192279c60 A99BF5C7-12EA-3700-8798-6522387A8A89 + 1170528
    9   Foundation                          0x000000019217b7e8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 129000
    10  Foundation                          0x000000019227bfbc A99BF5C7-12EA-3700-8798-6522387A8A89 + 1179580
    11  Foundation                          0x000000019217b464 A99BF5C7-12EA-3700-8798-6522387A8A89 + 128100
    12  Foundation                          0x000000019227c9e8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 1182184
    13  Foundation                          0x000000019227c4a8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 1180840
    14  libdispatch.dylib                   0x00000001042bda48 _dispatch_block_async_invoke2 + 144
    15  libdispatch.dylib                   0x00000001042af2a8 _dispatch_client_callout + 20
    16  libdispatch.dylib                   0x00000001042b2084 _dispatch_continuation_pop + 572
    17  libdispatch.dylib                   0x00000001042b1468 _dispatch_async_redirect_invoke + 628
    18  libdispatch.dylib                   0x00000001042c0aac _dispatch_root_queue_drain + 356
    19  libdispatch.dylib                   0x00000001042c1418 _dispatch_worker_thread2 + 144
    20  libsystem_pthread.dylib             0x0000000191bb6a60 _pthread_wqthread + 216
    21  libsystem_pthread.dylib             0x0000000191bbcc78 start_wqthread + 8
    2019-09-24 23:21:25.431565+0200 Instagram Profile[4437:1560883] WF: _userSettingsForUser mobile: {
        filterBlacklist =     (
        );
        filterWhitelist =     (
        );
        restrictWeb = 1;
        useContentFilter = 0;
        useContentFilterOverrides = 0;
        whitelistEnabled = 0;
    }
    2019-09-24 23:21:25.431612+0200 Instagram Profile[4437:1560883] WF: _WebFilterIsActive returning: NO
    2019-09-24 23:21:26.084697+0200 Instagram Profile[4437:1560883] WF: _userSettingsForUser mobile: {
        filterBlacklist =     (
        );
        filterWhitelist =     (
        );
        restrictWeb = 1;
        useContentFilter = 0;
        useContentFilterOverrides = 0;
        whitelistEnabled = 0;
    }
    2019-09-24 23:21:26.084745+0200 Instagram Profile[4437:1560883] WF: _WebFilterIsActive returning: NO
    2019-09-24 23:21:26.150637+0200 Instagram Profile[4437:1560979] NSURLConnection ordering violation: didFinishLoading to be scheduled before didReceiveResponse
    2019-09-24 23:21:30.905067+0200 Instagram Profile[4437:1560742] This application is modifying the autolayout engine from a background thread after the engine was accessed from the main thread. This can lead to engine corruption and weird crashes.
     Stack:(
        0   Foundation                          0x00000001923953a4 A99BF5C7-12EA-3700-8798-6522387A8A89 + 2331556
        1   Foundation                          0x000000019218eb94 A99BF5C7-12EA-3700-8798-6522387A8A89 + 207764
        2   Foundation                          0x000000019218eaa8 A99BF5C7-12EA-3700-8798-6522387A8A89 + 207528
        3   Foundation                          0x000000019218e718 A99BF5C7-12EA-3700-8798-6522387A8A89 + 206616
        4   UIKitCore                           0x00000001963e6ea8 EBED47E6-6BB2-3119-82CE-CC13EDCA02D6 + 15568552
        5   libobjc.A.dylib                     0x0000000191bbfaf0 10328337-A06E-370F-8958-6EDDA1F434DC + 6896
        6   QuartzCore                          0x0000000198984384 18D85F6F-635D-3A6F-BF7D-898A644FDCF5 + 1393540
        7   UIKitCore                           0x000000019634fe54 EBED47E6-6BB2-3119-82CE-CC13EDCA02D6 + 14949972
        8   QuartzCore                          0x000000019898468c 18D85F6F-635D-3A6F-BF7D-898A644FDCF5 + 1394316
        9   QuartzCore                          0x0000000198997bf4 18D85F6F-635D-3A6F-BF7D-898A644FDCF5 + 1473524
        10  QuartzCore                          0x00000001988dd3e4 18D85F6F-635D-3A6F-BF7D-898A644FDCF5 + 709604
        11  QuartzCore                          0x00000001989083a0 18D85F6F-635D-3A6F-BF7D-898A644FDCF5 + 885664
        12  QuartzCore                          0x0000000198909388 18D85F6F-635D-3A6F-BF7D-898A644FDCF5 + 889736
        13  libsystem_pthread.dylib             0x0000000191bbc3c0 FEB52688-4D65-3D38-AD50-01B128A74208 + 37824
        14  libsystem_pthread.dylib             0x0000000191bb4dbc FEB52688-4D65-3D38-AD50-01B128A74208 + 7612
        15  libsystem_pthread.dylib             0x0000000191bb6de8 FEB52688-4D65-3D38-AD50-01B128A74208 + 15848
        16  libsystem_pthread.dylib             0x0000000191bb6b30 _pthread_wqthread + 424
        17  libsystem_pthread.dylib             0x0000000191bbcc78 start_wqthread + 8
    )
    2019-09-24 23:21:30.927369+0200 Instagram Profile[4437:1560742] *** Terminating app due to uncaught exception &#39;NSInternalInconsistencyException&#39;, reason: &#39;Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread.&#39;
    *** First throw call stack:
    (0x191ea9c30 0x191bc40c8 0x192395434 0x19218eb94 0x19218eaa8 0x19218e718 0x1963e6ea8 0x191bbfaf0 0x198984384 0x19634fe54 0x19898468c 0x198997bf4 0x1988dd3e4 0x1989083a0 0x198909388 0x191bbc3c0 0x191bb4dbc 0x191bb6de8 0x191bb6b30 0x191bbcc78)
    libc++abi.dylib: terminating with uncaught exception of type NSException

Modifications to the &gt; layout engine must not be performed from a background thread after it has been accessed from the main thread

Since I updated to the latest Xcode version 11.0 (11A420a) the debugging is extremely slow and cumbersome. 

**EDIT:** After updating to 11.1 GM (11A1027) the problem is still the same.

Compiling a project and running it in simulator or on a device is no problem. However when reaching a breakpoint Xcode becomes more or less unusable:

 - Program execution stops immediately when the breakpoint is reached. However Xcode needs up to 30 seconds to show the position in the code window and another minute or so to load the content of the variable view (which shows the values and states of the variables available at the breakpoint).
 - If I use the *Step into* or *Step over* features it takes up to a minute to perform the next step and again another minute to load the variables.

I am running Xcode on a Mac mini 2018 with a 3.2 GHz i7 and 32 GB ram. I have used Xcode 10 on the same machine before without any problems.

---

Searching for &quot;Xcode slow&quot; brings up a ton of threads and possible solutions of course. From my years as iOS Developer I know that Xcode never was the fastest and stable program. However it was never as bad as now.

Unfortunately none of the know tricks (restarting Xcode or the Mac, cleaning the project, cleaning the Xcode library folders, etc. had any effect,

**So the big question is:**

**Is this a known problem in Xcode 11? Are there any known solutions?**  


Xcode 11 debugger is extremely slow - A known problem?

In imperative Swift, it is common to use computed properties to provide convenient access to data without duplicating state. 

Let&#39;s say I have this class made for imperative MVC use:

```swift
class ImperativeUserManager {
    private(set) var currentUser: User? {
        didSet {
            if oldValue != currentUser {
                NotificationCenter.default.post(name: NSNotification.Name(&quot;userStateDidChange&quot;), object: nil)
                // Observers that receive this notification might then check either currentUser or userIsLoggedIn for the latest state
            }
        }
    }
    
    var userIsLoggedIn: Bool {
        currentUser != nil
    }

    // ...
}
```

If I want to create a reactive equivalent with Combine, e.g. for use with SwiftUI, I can easily add `@Published` to stored properties to generate `Publisher`s, but not for computed properties. 

```swift
    @Published var userIsLoggedIn: Bool { // Error: Property wrapper cannot be applied to a computed property
        currentUser != nil
    }
```

There are various workarounds I could think of. I could make my computed property stored instead and keep it updated. 


Option 1: Using a property observer:

```swift
class ReactiveUserManager1: ObservableObject {
    @Published private(set) var currentUser: User? {
        didSet {
            userIsLoggedIn = currentUser != nil
        }
    }
    
    @Published private(set) var userIsLoggedIn: Bool = false

    // ...
}
```

Option 2: Using a `Subscriber` in my own class:

```swift
class ReactiveUserManager2: ObservableObject {
    @Published private(set) var currentUser: User?
    @Published private(set) var userIsLoggedIn: Bool = false
    
    private var subscribers = Set&lt;AnyCancellable&gt;()
    
    init() {
        $currentUser
            .map { $0 != nil }
            .assign(to: \.userIsLoggedIn, on: self)
            .store(in: &amp;subscribers)
    }
    
    // ...
}
```

However, these workarounds are not as elegant as computed properties. They duplicate state and they do not update both properties simultaneously. 

What would be a proper equivalent to adding a `Publisher` to a computed property in Combine?

An equivalent to computed properties using @Published in Swift Combine?

Since I installed the **iOS 13.2 beta**, I have been getting a debug console error message. It happens every time I load a ViewController with a WKWebView object in the storyboard.


Then the following message is shown continuously while the web view is visible
...

    2019-10-10 12:10:47.867830+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.908698+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.908814+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.934169+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.947668+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:47.964375+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.193556+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.193723+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.193941+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.194012+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.195679+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.200432+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.207225+0200 (...) [Process] kill() returned unexpected error 1  
    2019-10-10 12:10:48.207298+0200 (...) [Process] kill() returned unexpected error 1 

At the moment I close the view I get the following message: 

    2019-10-10 12:32:41.577505+0200 (...)[ProcessSuspension] 0x1051e50b0 - ProcessAssertion::processAssertionWasInvalidated() 

Sometimes I get the following message in the middle while the web view is loaded: (I can&#39;t say when it happens)
 
    2019-10-10 12:33:11.453528+0200 (...) Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
    2019-10-10 12:33:11.459713+0200 (...) Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service

And the if I touch the screen it starts again

        2019-10-10 12:10:48.200432+0200 (...) [Process] kill() returned unexpected error 1  
        2019-10-10 12:10:48.207225+0200 (...) [Process] kill() returned unexpected error 1  
        2019-10-10 12:10:48.207298+0200 (...) [Process] kill() returned unexpected error 1 
    ...




I have checked that this is happening in all of the view controllers with WKWebViews of my app, so it doesn&#39;t seem to be a code error. 

This **doesn&#39;t crash the app**, but I would like to know why this is happening, and if someone else is having the same issue. 



Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?

After upgrading to Xcode 11.3.1, I am having problems using Safari web inspector with the iOS 12.1 simulator. Every time that I run an app inside of an iOS 12.1 simulator device, it will show up in the Safari debug menu and allow me to connect to it, but the only tabs I will see are Sources, Console and Audit. 

Here is a screenshot of the inspector attached to an instance of the Safari browser inside of the simulator.

[![enter image description here][1]][1]


Is there any way to resolve this?


  [1]: https://i.stack.imgur.com/Lch96.png

Environment:

 - MacOS 10.14.6 (18G95)
 - Xcode 11.3.1
 - Safari 13.1 (14609.1.20.111.8)
 - Simulator Version 11.3.1 (SimulatorApp-912.5.1 SimulatorKit-570.3
   CoreSimulator-681.17.2)



Safari web inspector is only showing Sources, Console and Audit

Today I downloaded the release of Xcode 12.3, and I went running the iOS 14.3 simulators and it seems like there is a graphic glitch that all translucent views are yellow, dock included.

I redownloaded iOS 14.2 and those seem fine. It just seems really odd. I&#39;ve submitted feedback, but I was curious if anyone else has seen this?

I&#39;m on [macOS v10.15.7][1] (Catalina) and am curious of if it&#39;s just Catalina or also [macOS v11][2] (Big Sur).

[![Image 1][3]][3]

[![Image 2][4]][4]

  [1]: https://en.wikipedia.org/wiki/MacOS_Catalina
  [2]: https://en.wikipedia.org/wiki/MacOS_Big_Sur
  [3]: https://i.stack.imgur.com/wBBFN.jpg
  [4]: https://i.stack.imgur.com/cldiw.png




Xcode 12.3 iOS 14.3 simulators Yellow Dock / yellow translucent issues

Trying to update from Xcode 11 GM to 11.1 always fail.

I tried moving /Applications/Xcode.app first... nothing works

This is my commerce log:

&gt;2019-10-08 12:29:08+01 leviathan installd[556]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=501 &quot;The package is attempting to install content to the system volume.&quot; UserInfo={NSLocalizedDescription=The package is attempting to install content to the system volume.} {

Can&#39;t update Xcode 11

I used to use autolayout add new constraints to make simple constraints to superview / relative view like this (for loooong time): 

[![enter image description here][1]][1]

However, recently after updated to the latest xcode (11.3.3 or just 11.3/11C29), I have this weird issue: when I set the constant = 0, they always generate the constraints in an unwanted way like this: 

[![enter image description here][2]][2]

And it seems default value is somehow 20 and making my view look so wrong (0 compared to 20?)

If I fix that by edit the constraint like this:

[![enter image description here][3]][3]

Then it&#39;ll correct again (the image is after edited the constraints, before edited it display constant = `Standard`)

I don&#39;t even know how to describe the issue, but how do I fix this new `add new constraint` to use my desire point instead of standard / default?

Update:

It seems to only happened when constraint to superview. No clue how to fix tho.

Update Apr-01-2020:

Xcode11.4 fixed this.


  [1]: https://i.stack.imgur.com/H66p8.png
  [2]: https://i.stack.imgur.com/QGLh6.png
  [3]: https://i.stack.imgur.com/ajIsr.png

Xcode 11 add new constraints set zero: use set value instead of default / standard

When inspecting a crash with Firebase Crashlytics, I noticed the following line in the Keys section:

&gt; CoreUI: deallocating _CUIInternalLinkRendition 7113 /private/var/containers/Bundle/Application/1E06D0B4-30EA-41CA-998C-D8E86AA94100/&lt;appname&gt;.app/Assets.car

Is this related to the assets in my app? A memory issue in CoreUI?

Content Type	Original Author	Original Content on Stackoverflow
Question	Dylan	View Question on Stackoverflow
Solution 1 - Ios	rmaddy	View Answer on Stackoverflow
Solution 2 - Ios	prostiak	View Answer on Stackoverflow

Is there an iPhone SE simulator for Xcode 11, iOS 13?

Ios Problem Overview

Ios Solutions

Solution 1 - Ios

Solution 2 - Ios

Keyboard gets stuck in ios 13 simulator

iOS 13: Swift - 'Set application root view controller programmatically' does not work

Attributions