It is a bit difficult to understand what you want to achieve. But it seems you found a solution. Great. So please close now all the other threads you have opened on the same question (and to which you have not replied. Did you read the answers at least ?). Have a good continuation.

Xcode 12.4 proposes 9.0 or 9.2. Same for you ? I compared with Xcode 12.1 which proposed from 9.0, 9.1, 9.2, 9.3, … whilst 11.3 which proposed all versions from 8.0 to 9.0, 9.1, 9.2, 9.3, 10… So it seems they manage versions for reason, even if it"s surprising that some are skipped (9.1 and 9.3 in Xcode 12.4). Finally, I would just accept the 9.3. That's already very old iOS version, less than 1% use it now. There may be a technical reason why archiver forces it.

From the crashlog, problem could come from the collectionView, line 52, where you invalidate the whole collection. Doc for UICollectionViewLayout says: When designing your custom layouts, you can improve performance by invalidating only those parts of your layout that actually changed. When you change items, calling the invalidateLayout() method forces the collection view to recompute all of its layout information and reapply it. A better solution is to recompute only the layout information that changed, which is exactly what invalidation contexts allow you to do. An invalidation context lets you specify which parts of the layout changed. The layout object can then use that information to minimize the amount of data it recomputes. So, could you either: remove this invalidate completely (what happens to your app then ?) use a more focused invalidate: func invalidateLayout(with: UICollectionViewLayoutInvalidationContext) Invalidates the current layout using the information in the provided context object. instead of func invalidateLayout() Invalidates the current layout and triggers a layout update. relocate the call to configurePhotosCollectionViewAfterResize() in another func override func viewDidLayoutSubviews() { super.viewDidLayoutSubviews() configurePhotosCollectionViewAfterResize() } following an idea found here: https://stackoverflow.com/questions/36884376/swift-how-to-refresh-uicollectionview-layout-after-rotation-of-the-device Note: could you testFlight your app, or download yourself to test it ? TestFlight would be more appropriate here.

If that may help… I once had a segmentation fault 11. Reason was: In a struct defined as: struct L { var u1: UInt64 var u2: UInt64 var u3: UInt64 var u4: UInt64 } I defined a subscript extension L {     subscript (j: Int, h: Int) - Bool? { } As far as I remember, the fault occurred if I called var lib  : [L]? if lib[j,h] { } instead of unwrapping: if lib![j,h] { } Hope that may help.

The app's entitlements does NOT have "com.apple.security.files.user-selected.read-write" Note that you could also add manually this entry in the entitlements plist (auto completion works there as well as you type com.apple.security.files.user). So that was the root cause. Don't forget to close the thread.

Are you sure you have not set a direct breakpoint there ? It occurred to others: https://developer.apple.com/forums/thread/39283 or https ://forums.raywenderlich. com/t/thread-1-breakpoint-1-1-2-1/41631 Or have you defined a breakpoint elsewhere ? Can you resume execution after breakpoint ? You should also try an option- clean build folder, in case. In anycase, look at the breakpoint panel at the left of Xcode window to see all the breakpoints you have set, and remove all.

It's not specific to Xcode 12.5. There was a long discussion about this error: 'Abort trap: 6 (in target )' https://developer.apple.com/forums/thread/107097

Don't use min and max for this. For instance, create a func to test validity: func isValidNumberOfPlayers(_ nb: Int) -> Bool { &#9;return nb > 0 && nb <= 10 } Then, when you create or read the list of players, for instance in an array with their names: var players: [String] = [] // You populate the array somewhere In the func where you declare the players, check the value, call if !isValidNumberOfPlayers(players.count) { print("number of players is not correct") // And do whatever you need to do } If you want to give a more precise test result, you could do this: enum PlayersCheckState { &#9;&#9; case ok &#9;&#9; case null &#9;&#9; case tooMany } func isValidNumberOfPlayers(_ nb: Int) -> PlayersCheckState { &#9;&#9;switch nb { &#9;&#9;case ...0&#9;: return .null &#9;&#9;case 1...10: return .ok &#9;&#9;default&#9;&#9;: return .tooMany &#9;&#9;} } Then call &#9;&#9;switch isValidNumberOfPlayers(playersCount) { &#9;&#9;case .null : print("No player") &#9;&#9;case .tooMany: print("too many players") &#9;&#9;case .ok: break&#9;&#9;//&#9;do whatever you need to do here &#9;&#9;}

@SemJelle When you mark the correct answer, it should be the correct answer, not your own acknowledge. In this case, correct answer is eskimo's.

@abhi.tomar That may depend on how space is organised (contiguous or not ?) Try with more room, as 50 GB.

Have you tried removing @escaping for RCTPromiseRejectBlock ? @objc func updateStepsCount(_ &#9;&#9;resolve: @escaping RCTPromiseResolveBlock, rejecter reject: RCTPromiseRejectBlock) { &#9;&#9;checkNotificationEnabled { enabled in &#9;&#9;&#9;&#9;resolve(enabled) &#9;&#9;} } // Or maybe in your case @objc func updateStepsCount(_ statisticsCollection: HKStatisticsCollection, _ resolve: @escaping RCTPromiseResolveBlock, rejecter reject: (RCTPromiseRejectBlock) -> Void) { See: https://stackoverflow.com/questions/59732722/swift-how-can-i-call-my-function-inside-completion-body This may be of interest as general discussion: https://forums.swift.org/t/implicit-escaping-of-closures-via-objective-c/12025

Try UNUserNotificationCenter.current().getNotificationSettings { (settings) in &#9;if settings.authorizationStatus == .authorized { &#9;&#9;// Notifications are allowed &#9;} &#9;else { &#9;&#9;// Either denied or notDetermined &#9;} } As defined here here: https://stackoverflow.com/questions/46664177/check-whether-user-notifications-are-enabled-after-uilocalnotification-deprecati

This tutorial should help you understand how: how to select a tool how to use it https ://medium. com/flawless-app-stories/getting-started-with-pencilkit-on-ios-13-a4bda3323fd8

@ZoneX It is very difficult to help if you don't do exactly what we propose. I proposed: override func prepare(for segue: UIStoryboardSegue, sender: Any?) { &#9;print("segue identifier", segue.identifier) &#9;if segue.identifier == "r" { &#9;&#9;let hockeyDetailVC: HockeyDetailVC = segue.destination as! HockeyDetailVC &#9;&#9;hockeyDetailVC.delegate = self &#9;} } and tell what you get. If you get something different from segue identifier r such as segue identifier R or segue identifier SomeString that means that "r" is not the identifier of this segue (or you don't call the right segue). Then change "r" by what you got here after "segue identifier" And what you did is very different for testing purpose &#9;override func prepare(for segue: UIStoryboardSegue, sender: Any?) { &#9;if segue.identifier == "r" { &#9;&#9;print("segue identifier", segue.identifier) // You put in the if that we know is not called ! It is key to check you call the RIGHT segue &#9;&#9;let hockeyDetailVC: HockeyDetailVC = segue.destination as! HockeyDetailVC &#9;&#9;hockeyDetailVC.delegate = self &#9;&#9;print("destination HockeyDetailVC is", hockeyDetailVC) &#9;} }

Is it Swift UIKit or SwiftUI ? Did you try calling func setNeedsDisplay(NSRect) on the frame of the label ?