Hi , I got this quote with 5800 repetitions (5.8 MB / 1k) : `2023-05-25 01:02:59.021733+0200 LookAt[6404:302136] [general] *** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSNumber' (0x7ff84cfe02f8) [/System/Library/Frameworks/Foundation.framework]' for key 'NS.objects', even though it was not explicitly included in the client allowed classes set: '{( "'NSMutableDictionary' (0x7ff84cfb6b48) [/System/Library/Frameworks/CoreFoundation.framework]", "'NSArray' (0x7ff84cfb68a0) [/System/Library/Frameworks/CoreFoundation.framework]" )}'. This will be disallowed in the future ` -(IBAction)readFile:(id)sender { NSData * data; NSError * error = nil; data = [_vrReadWrite readData:kFileComponentA]; NSSet * set = [_vrReadWrite setOfClasses]; _vrRoot = [NSKeyedUnarchiver unarchivedObjectOfClasses:set fromData:data error:&error]; }``` I got the expected result, that's fine, but I'm not interested in this future. Uwe

Several years ago, I modified an [Apple Obj-c Time Zone] example (illustrated image below) to enrich my non-existent knowledge with Time Zones. The modified application illustrates the current [Time Zone Date and Time] for my current MDT location, and will illustrate another available [Time Zone Location] from a popup button. So, I decided to see whether I could convert the Obj-c code to Swift code. The converted Swift code built properly, but the application will repeatedly crash when I engage the Swift [clockAndCalendar binding]. The Swift code application generates the following error message: I understand the error message listed above to be: "EXC_BAD_ACCESS" error message (code=1, address=0x0) occurs when the application tries to access memory, which the application cannot access, or does not exist. Examining the error shows the MDT’s as the first encountered location: When I examine the additional [information] button, Xcode generates the following message, stating a [Foundation] incompatibility exists. Again, I wonder whether this issue can be resolved. So, for the moment, I believe I cannot produce an equivalent Swift file just yet without more knowledge, where I unwittingly, and most likely applied the Swift [clockAndCalendar binding] code incorrectly … ? I am curious about what I should do next, and how I might properly approach this error message ... ? NSTimeZone (Obj-c) and TimeZone (Swift) produce different [Time Zone] results, as noted in the associated [Print Statements]. Your possible suggestions for me to explore would be very welcome … :] Again, I must thank you for your time with this issue. Best regards, jim_k // The modified Obj-c View: // Obj-c [setupCityClock] code: - (void)setupCityClock:(NSView *)containerView timeZone:(NSTimeZone *)timeZone { NSDatePickerElementFlags flags = 0; flags |= NSDatePickerElementFlagHourMinute; flags |= NSDatePickerElementFlagHourMinuteSecond; flags |= NSDatePickerElementFlagTimeZone; flags |= NSDatePickerElementFlagYearMonth; flags |= NSDatePickerElementFlagYearMonthDay; flags |= NSDatePickerElementFlagEra; // Setup the city block and bind its value to a single NSDate property. NSDatePicker *theIdentifiedTimeZoneLocationCalendarAndClock = [[NSDatePicker alloc] initWithFrame:containerView.bounds]; // Draw the [Focus Ring] around the [Date Picker] theIdentifiedTimeZoneLocationCalendarAndClock.focusRingType = NO; // Draw the [datePicker Background colour] which makes the [background colour darker] theIdentifiedTimeZoneLocationCalendarAndClock.drawsBackground = YES; // Set the [datePicker Background Colour] to [TEXT BACKGROUND COLOUR] theIdentifiedTimeZoneLocationCalendarAndClock.backgroundColor = NSColor.blackColor; // Set the [datePicker Text Colour] to [WHITE] theIdentifiedTimeZoneLocationCalendarAndClock.textColor = NSColor.controlTextColor; // If the function is set to [YES] the [BORDER] is not [DRAWN] properly. // Setting the function to [NO] will not draw the [BORDER] theIdentifiedTimeZoneLocationCalendarAndClock.bordered = NO; // Set the [DATE PICKER STYLE] theIdentifiedTimeZoneLocationCalendarAndClock.datePickerStyle = NSDatePickerStyleClockAndCalendar; // Set the [DATE PICKER ELEMENTS] theIdentifiedTimeZoneLocationCalendarAndClock.datePickerElements = flags; // Set the [TIME ZONE] theIdentifiedTimeZoneLocationCalendarAndClock.timeZone = timeZone; // Check the results: NSLog(@"The [CURRENT TIME ZONE FOR (setupCityClock)] :: %@", timeZone); // Prints: - [America/Edmonton (MDT) offset -21600 (Daylight)] // Prints: - [Europe/London (GMT+1) offset 3600 (Daylight)] NSLog(@"The [CURRENT TIME ZONE FOR (setupCityClock) again] :: %@", theIdentifiedTimeZoneLocationCalendarAndClock.timeZone); // Prints: - [America/Edmonton (MDT) offset -21600 (Daylight)] // Prints: - [Europe/London (GMT+1) offset 3600 (Daylight)] // Bind the [TIME ZONES] to the [CURRENT TIME] [theIdentifiedTimeZoneLocationCalendarAndClock bind:NSValueBinding toObject:self withKeyPath:@"currentTime" options:nil]; // Add the [CITY CLOCK] to the [CONTAINER VIEW] [containerView addSubview:theIdentifiedTimeZoneLocationCalendarAndClock]; } // End of [- (void)setupCityClock:] // The modified Swift View [Without the [clockAndCalendar binding] engaged]: // NOTE: The clock’s static time differential is correct with each popup button selection. // Swift [setupCityClock] code: func setupCityClock(containerView: NSView, timeZone: TimeZone) { var flags = NSDatePicker.ElementFlags() flags.insert(.hourMinute) flags.insert(.hourMinuteSecond) flags.insert(.timeZone) flags.insert(.yearMonth) flags.insert(.yearMonthDay) flags.insert(.era) // Setup the city clock and bind its value to a single NSDate property. let theIdentifiedTimeZoneLocationCalendarAndClock = NSDatePicker(frame: containerView.bounds) // Draw the [Focus Ring] around the [Date Picker] theIdentifiedTimeZoneLocationCalendarAndClock.focusRingType = .none // Draw the [datePicker Background colour] which makes the [background colour darker] theIdentifiedTimeZoneLocationCalendarAndClock.drawsBackground = true // Set the [datePicker Background Colour] to [TEXT BACKGROUND COLOUR] theIdentifiedTimeZoneLocationCalendarAndClock.backgroundColor = NSColor.black // Set the [datePicker Text Colour] to [WHITE] theIdentifiedTimeZoneLocationCalendarAndClock.textColor = NSColor.controlTextColor // If the function is set to [YES] the [BORDER] is not [DRAWN] properly. // Setting the function to [NO] will [NOT] draw the [BORDER] theIdentifiedTimeZoneLocationCalendarAndClock.isBordered = false // Set the [DATE PICKER STYLE] theIdentifiedTimeZoneLocationCalendarAndClock.datePickerStyle = .clockAndCalendar // Set the [DATE PICKER ELEMENTS] theIdentifiedTimeZoneLocationCalendarAndClock.datePickerElements = flags // Set the [TIME ZONE] theIdentifiedTimeZoneLocationCalendarAndClock.timeZone = timeZone print("The [CURRENT TIME ZONE FOR (setupCityClock)] :: \(timeZone)") // Prints: - [America/Edmonton (fixed (equal to current))] // Prints: - [Europe/London (fixed)] // Bind the [TIME ZONES] to the [CURRENT TIME] <=== (The error occurs here) theIdentifiedTimeZoneLocationCalendarAndClock.bind(.value, to: self, withKeyPath: "currentTime", options: nil) // Add the [CITY CLOCK] to the [CONTAINER VIEW] containerView.addSubview(theIdentifiedTimeZoneLocationCalendarAndClock) } // End of [func setupCityClock(containerView: NSView, timeZone: TimeZone)]

I have a MacOS project with several targets and in which I have been refactoring Obj-C classes over to Swift 1 by 1. I have been doing this for months and all was fine and building well until the most recent class. But with that one the project simply refuses to build. I see the ProjectName-Swift.h file in the Project folder but the last build date was over a week ago and so it obviously does not include the new class, hence Xcode is complaining it can't find the new Swift Class. Understand the following before answering please: This is a very old and longstanding MacOS project with several targets, it is NOT a new MacOS project. I have previously added quite a few other Swift classes (using Swift 5) to this project and was able to build and run just fine. I have tried clean and build about 50 times and removing derived data. Nothing will force a rebuild of the ProjectName-Swift.h and the new class is definitely NOT in there. There are no other build issues with this project, just the one related to not being able to see the new class. The class was previously implemented in Obj-C and I was porting it over and that old class file is not referenced by the project at the moment. This Swift class ChartListTableCellView is NOT referenced in the obj.h file so it is not forward referenced there. The Bridge Header is imported in the .m that is complaining. Because Xcode is not seeing the Swift Class in the ProjectName-Swift.h it will not build and I am sort of in a chicken and egg circle jerk here. I even tried using the old Header at the top of the .m file where I need this class and it gets further but not far enough to build the Bridge Header. This is how the new class is declared so it should be visible. @objcMembers class ChartListTableCellView : NSView { private let grayBottomBorder = NSView() ... init() { super.init(frame: NSMakeRect(0, 0, 0, 0)) ... } ... } I am stumped and am out of ideas. Apple!! Seriously there needs to be a simple way to force a rebuild of the ProjectName-Swift.h file.

Hi, I want to know if we can detect whether Settings -> Mobile Data -> Wifi Calling option is enabled or not? I checked and could not find any API which can detect this. I am also interested to know if we can find a way to know if Wifi Calling is being used in a call.

Hi, Is there any API exposed to fetch network security type like "WPA", "WPA2", "WES" or None for iOS device?