Today Apple released macOS Catalina 10.15 Beta 10 (19A578c) to Developers.
This article is meant to save you time going through the notes to find what is new and what is still leftover from the last beta. I went through both Beta 9 and the new Catalina 10.15 Beta 10 (19A578c) release notes to find all the changes. Like usual, I also have included the entire patch notes list as an archive. When Apple releases the next Beta patch notes, the previous patch notes are overwritten and taken down.
Summary of Beta 10 Patch Notes
Nothing! Apple has not documented any changes in the Public Developer Release Notes between Beta 9 and Beta 10.
Report your bugs NOW!
This may be the final beta left to test. The public Release of Catalina is only a few weeks away! You will want to get any bugs that you find into Apple now. If you get them in now, they could be fixed in the current beta cycle instead of waiting until after September’s release date. If you wait it could be months before the fix is put into a dot release combo update.
Keep in mind, I can only publish public data. If you are an AppleSeed for IT member you can access additional 10.15 Catalina Beta Patch Notes in the AppleSeed Portal. AppleSeed information is protected by Apple’s NDA.
Some fixes are not going to be listed. Many issues are from #MacAdmins who have filed FeedBack Requests and Enterprise Support tickets. Most of these issues are resolved but are never publicly noted.
Today Apple released macOS Mojave 10.14.6 Supplemental Update #3 and Security Updates 2019-005 for High Sierra 10.13 and Sierra 10.12. If Apple’s previous update release history is any guide, 2019-005 will be the final Security Update for Sierra. Once macOS 10.15 Catalina is released in October, Mojave will be security patched for two more years. High Sierra will be supported for one year and Sierra will be dropped.
10.14.6 Supplemental Update #3 ??? Wait.. What? Apple is calling it the 2nd Supplemental Update.
Not sure where Apple got out of order here, but this is the 10.14.6 Build Version release schedule.
Which version of the 10.14.6 update does my Mac need?
Software Update will always point you to the right update.
Any Build Version of 10.14.6 = Supplemental Update #3
10.14.0-10.14.4 = Combo Update
10.14.5 = Delta Update
10.8 – 10.14.6 Upgrade = Updated 10.14.6 (18G103) Full Installer.app
How do you keep track of all the macOS Build Versions?
I document all of all macOS versions along with most Apple Applications, XProtect, Gatekeeper and MRT updates in one database. You can check out the link below.
On Tuesday Apple released Xcode 11.1 GM Seed to Developers.
The Production version of Xcode 11 was released to the Mac App Store just 6 days ago. We now have the first beta version of Xcode 11.1 available for developers to test with. What’s new?
I have added links to my previous Xcode 11 Change Notes below. Also included is Xcode Requirements and “What’s New”
Summary of New Xcode 11. GM Seed Patch Notes
1 New Features
3 New Resolved issues
6 New Known Issues
0 New Deprecations
A Full List of changes is listed below, along with the full patch notes list.
Xcode 11.1 includes SDKs for iOS 13.1, macOS Catalina 10.15, watchOS 6, and tvOS 13. 2. Xcode 11.1 supports on-device debugging for iOS 8 and later, tvOS 9 and later, and watchOS 2 and later. 3. Xcode 11.1 requires a Mac running macOS Mojave 10.14.4 or later.
Asset Catalogs
Known Issues
Images in the asset catalog won’t be found at runtime when running on watchOS 4. (55395258)
Interface Builder
New Features
You can now preview your interface for the 7th generation iPad. (53957165)
Known Issues
There is an issue with UITabBarController where decoding an instance from a storyboard will create some extra views at the left end of the screen. Developers may remove these by applying a workaround. (55310448)Workaround: To remove the extraneous views from Storyboard, create a subclass of a UITabBarController and add the following snippet in the class’s init(coder:)method:class WorkaroundTabBarController: UITabBarController {
required init?(coder: NSCoder) {
super.init(coder: coder)
// This must be run immediately after the call to super.
if (tabBar.subviews.count > 1) {
tabBar.subviews[0].isHidden = true
}
}
}
Resolved Issues
Fixed a crash that sometimes occurred when compiling XIB files in iOS projects that backwards deploy to iOS versions earlier than 13.0. (55271752)
Localization
Known Issues
UITableViewCell labels in storyboards and XIB files do not use localized string values from the strings file at runtime. (52839404)
Simulator
Known Issues
On macOS Catalina, iCloud Drive will crash in a loop on simulated devices running older versions of iOS. (51392951, 54282967, 54818084)Workaround: Log out of iCloud in impacted simulators to halt the crash cycle.
Resolved Issues
CarPlay works on iOS 13.1 simulators. (54492162)
Swift
Known Issues
The NEHotspotConfigurationError enum from the NetworkExtension framework changed from NS_ENUM to NS_ERROR_ENUM, which can cause compiler errors in existing Swift code that uses the enum. For example, in code like this:let code = NEHotspotConfigurationError(rawValue: errorCode)
You will see the error message: “error: incorrect argument label in call (have ‘rawValue:’, expected ‘_nsError:’).” (54134493)Workaround: Replace references of NEHotspotConfigurationError with NEHotspotConfigurationError.Code. For the above example, change the code to:let code = NEHotspotConfigurationError.Code(rawValue: errorCode)
SwiftUI
Resolved Issues
Fixed an issue with Xcode Previews where debugging a preview would no longer pin the preview, and navigating would lose the debug session. (54758098)
Swift Packages
Known Issues
If an iOS, tvOS, or watchOS app uses a Swift Package that builds a dynamic library, it cannot be submitted to the App Store. (55564324)Workaround: Modify the Package manifest to build a static library.
Google Chrome Keystone Updater is removing the /var symlink causing account and boot issues.
UPDATE: 10/03/19
Google has posted an update that they found the issue in the Keystone Update and fixed it. They are are pushing the updated version now. The push started last night and the new version should be 1.2.13.79 or 1.2.13.80.
See Index #7 for theUpdated Fix from Google Support
#Varsectomy FAQ- Index
1.What is going on here?– #Varsectomy
2. Which macOS Versions are affected ?
3.Specific Mac Hardware ?
4.SIP – System Integrity Protection
5.AVID orGoogle Chrome Keystone Update causing this issue ?
6. How can I check my /var symlink?
7.How can I fix the issue = 2 ways to fix.
8. What about Hackintosh users? A fix for you!
9. Should I disable Chrome Auto Updates
10.Jamf Pro Extension Atribute
11. Links
12.Credit– Investigation by #MacAdmins& Apple
1. What is going on here ? – #Varsectomy
The purpose of this article is to gather all known information and data around the current issues some AVID and NON SIP protected Macs are experiencing. The issue first started on Monday 9/23/19.
Late Yesterday some #MacAdmins started to report that a few of their systems would not boot properly. They would have the following issues.
1. After rebooting the affected system it would Kernel Panic. The system will reboot only to KP again
2. User Logs out and the system shows the Setup Assistant.
3. The System Kernel Panics into a boot Loop.
AVID users were some of the first to report the issue. AVID.com says
Sometimes AVID Media Creators use 3rd Party Graphics cards connected to their Mac Pro. When the issue hit yesterday, it was thought that AVID was the main cause of the problems since all the users experiencing the issue had AVID software.
Only later after a MacAdmins deep dive investigation was it found that AVID was NOT the cause of the problem. It was Google Chrome Keystone Updater!
Join the #Varsectomy channel in MacAdmins Chat for the latest info!
2. Which macOS Versions are affected ?
MacOS 10.9 – 10.14 Mojave
NOTE: macOS 10.9 & 10.10 so not have SIP. System Integrity Protection was introduced in macOS 10.11 El Capitan.
3.Specific Mac Hardware ?
At first it was first reported that the 2013 Mac Pro was affected, this is not true.
Now it seems the issue affects all Macs that have SIP (System Integrity Protection) Disabled or turned OFF
Check if SIP is enabled by running csrutil status
System Integrity Protection status: enabled.
System Integrity Protection status: disabled
4. SIP – System Integrity Protection
All Reports so far look to be from Macs that have SIP Disabled!
Please do not disable SIP, it was created to protect macOS from this very issue.
5.AVID or Google Chrome Keystone Update causing this issue ?
At first the issue seemed to be caused by Avid Media Composer. After further investigation it was found that AVID was not the problem! Some AVID users may need to DISABLE SIP for 3rd party Video Card support.
After investigation from some of the top minds in the MacAmins Slack Chat #varsectomy channel it was found that the Google Keystone Updater was at the heart of the issue.
The Google Chrome Keystone updater lives here (if set to only update for the user who installed Chrome) – ~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/
If set to install for ALL users. (This also prompts for admin access for install) Thanks Jeff Johnson/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/
Thank you eholtam for the VM investigation and Screenshots!
Google Chrome Keystone Update Policy Running.
After kicking off the update you can see the problem below.
“Found and deleted symlink at path /var”
Found and deleted symlink at path /var
6. How do I check my /var symlink?
Check to see if your /var symlink was modified by running the following command.
ls -ldO /var
You should get one of the following outputs. The first one below means that your /var volder is SIP protected (notice the restricted flag) and the proper sym link /var -> private/var
The next one means that your symlink is broken and the folder is NOT SIP Protected.
drwxr-xr-x 5 503 wheel - 170 Sep 24 14:37 /var
If you find /var in this condition you are affected! If you LOGOUT, SHUTDOWN OR RESTART your Mac will NOT Boot! You will need to boot into recovery, repair the /var symlink and reset the restricted flags. Fix below.
First you have to fix the /var symlink so it shows /var -> private/var
Then you can remove the affected LaunchAgents
Boot to macOS Recovery by holding down Command R
Steps for 10.11 -10.14 SIP Supported Systems
1. Boot into Recovery 2. Launch Terminal (only if you're on 10.11+ with SIP) # chroot /Volumes/[affected install] # mv var vv # ln -s private/var var # chflags -h restricted /var # chflags -h hidden /var # xattr -sw com.apple.rootless "" /var
Steps for 10.9-10.10 NON SIP Systems
10.10 or older: only do symblink and the hidden chflag and remove launch agents from /Users/[affected user]/Library/LaunchAgents/ OR /Library/LaunchAgents/ - com.google.keystone.agent.plist - com.google.keystone.xpcservice.plist # exit (recommended) # csrutil enable (10.11+) 8. Reboot
NOTE: The information below is from Google. Link Below.
chroot /Volumes/Macintosh\ HD #(Macintosh HD is the default)
rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
mv var var_back #(Var may not exist, but this is fine)
ln -sh private/var /var
chflags -h restricted /var
chflags -h hidden /var
xattr -sw com.apple.rootless "" /var
NOTE: Commenter stockmind has noted that the GoogleSoftwareUpdate.Bundle could reside in the USERS folder. In that case you need to run this string instead. Change USERNAME to your Username. Thanks for the tip!
Youshouldn’t need to disable Chrome Auto updates at this time. From the Chromium bug report – bugs.chromium.org/p/chromium/issues/detail?id=1007358 Google has disabled Keystone updates for now until the issue is found and resolved.
Today Apple released macOS Catalina 10.15 (19A573a) Beta 9 to Developers.
This article is meant to save you time going through the notes to find what is new and what is still leftover from the last beta. I went through both Beta 8 and the new Catalina 10.15 Beta 9 (19A573a) release notes to find all the changes. Like usual, I also have included the entire patch notes list as an archive. When Apple releases the next Beta patch notes, the previous patch notes are overwritten and taken down.
Summary of Beta 9 Patch Notes
1 New Features
2 New Resolved issues
2 New Known Issues
0 New Deprecations
Report your bugs NOW!
This may be the final beta left to test. The public Release of Catalina is only a few weeks away! You will want to get any bugs that you find into Apple now. If you get them in now, they could be fixed in the current beta cycle instead of waiting until after September’s release date. If you wait it could be months before the fix is put into a dot release combo update.
Keep in mind, I can only publish public data. If you are an AppleSeed for IT member you can access additional 10.15 Catalina Beta Patch Notes in the AppleSeed Portal. AppleSeed information is protected by Apple’s NDA.
Some fixes are not going to be listed. Many issues are from #MacAdmins who have filed FeedBack Requests and Enterprise Support tickets. Most of these issues are resolved but are never publicly noted.
1. New Features in Beta 9
iCloud – Launch daemons and launch agents introduce new user privacy protections. Specifying privacy-sensitive files and folders in a launchd property list might not work as expected and prevent the service from running. Having Program or ProgramArguments pointing to an executable in a privacy sensitive location is currently allowed, but may be restricted in a future release. (49702405)To comply with the new privacy protections, resources for a launchd service must be stored in locations that aren’t privacy sensitive. If necessary, the app can set up resources during its execution rather than using launchd property list keys, making it possible to grant the app access using System Preferences > Security & Privacy > Privacy. The following launchd property list keys are affected: KeepAlive, PathState, QueueDirectories, Sockets, SockPathName, StandardErrorPath, StandardInPath, StandardOutPath, and WatchPaths.
2. New Resolved issues
Localization – Fixed an issue where certain languages might exhibit clipped or misaligned layout. (51068688, 50983852)
Localization – Fixed an issue where certain languages might display unlocalized text. (47765173, 51196633)
3. New Known Issues
Mac Catalyst – DOM keyboard events aren’t dispatched as expected in WKWebView when pressing or releasing keys. Web apps needing to track typed characters can instead listen for DOM input events. (54580414)
Remote Desktop – Turning on Curtain Mode prevents you from being able to control a remote Mac. (52900397)
Xcode 11 (11A420a) Is now available in the App Store
Today Apple released Xcode 11 to the Mac App Store.
The Production version of Xcode 11 was released to the Mac App Store today. The Build Number is the same as Xcode 11 Seed #2. I also double checked the release notes are they are the same.
I have added links to my previous Xcode 11 Change Notes below. Also included is Xcode Requirements and “What’s New”
Xcode 11 includes Swift 5.1 and SDKs for iOS 13, tvOS 13, watchOS 6, and macOS Catalina 10.15
SwiftUI
SwiftUI framework and design tools work together to enable a new way to build user intefaces
Declarative syntax defines your user interface using easy-to-read Swift code
Design tools make it as easy as drag-and-drop to construct and edit your views
Code you write is always in sync with the design and preview canvas
Library of controls and modifiers make it easy to build complex interfaces
Animations are built using simple commands that describe the action you want to see
Preview your real app running on multiple device types, orientations, and font sizes
Share common code across all Apple platforms, and add custom experiences for each OS
* NOTE: SwiftUI requires iOS 13, watchOS 6, tvOS 13, or macOS Catalina. To use the SwiftUI design canvas Xcode 11 must be running on macOS Catalina, coming this Fall.
Mac Catalyst brings iPad apps to the Mac
Click a single checkbox in your iPad project to add a native Mac app
One project and set of source code creates iPhone, iPad, and Mac versions of your app
Customize elements of your app for an experience unique to Mac
Add new SwiftUI code to your project along side existing UIKit code
Submit to the Mac App Store or notarize for outside distribution
Swift and Swift Packages
Swift packages are supported throughout, including build, debug, and SCM workflows
Use Swift packages from GitHub, Bitbucket, GitLab, or your own hosts
Download packages automatically based on dependency analysis
Create your own packages to share code among all your apps, or to publish for the community
iOS dark mode
Switch between light and dark mode instantly while developing and debugging
Asset catalog makes it easy to control images and colors for dark and light mode
Editor
Editor minimap gives a bird’s eye view of your code so you can quickly jump to any line
Each editor view has its own preview, assistant, or other complementary views
Split any editor pane to layout your workspace exactly as you want
Other improvements
Build stand-alone watchOS apps with a faster debugging experience
Simulator launches quickly and uses the GPU to accelerate Metal code
Test plans give you greater control of your test harness with sharable results bundles
Automatically generate localized screenshots using UI tests as part of your test plan
Source control adds support for stash and cherry-pick operations
Simulate device conditions such as a slow network or thermal warnings while debugging
Metrics tab in the Organizer shows how efficiently your app runs on customer devices
10.14.6 Update Causes a Kernel Panic When Using the Built-In FaceTime Camera.
NEW UPDATE: 4/08/20 – I am getting multiple reports that users are having issues applications that use Hardware Accelerated Video with the latest 10.14 and 10.13 2020-002 Security updates. The system will 100% freeze up during video conference, video or heavy app usage and you will have to hard power down. I posted all the new information about the freezing issue in a new article here – https://mrmacintosh.com/2020-002-update-causes-some-macs-to-freeze-up-while-using-vid-conf-apps/
FINAL UPDATE: 1/22/20 – Multiple users have contacted me to let me know that the latest macOS Mojave 10.14.6 Security Update 2019-002 (18G2022) has fixed the issue for them! The T2 BridgeOS version is 17.16.12551 or newer.
UPDATE: 10/03/19 – I am hearing from readers and commenters that Zoom has confirmed that this issue is fixed in macOS Catalina 10.15. This could very well mean that we will not get a fix for Mojave. 🙁
After Apple released the 10.14.6 Update, some users of 2019 & 2018 15″ MacBook Pros started to report Kernel Panics when using the Built-In FaceTime Camera.
I reported on a similar issue about a month ago when the 2019-004 Security Update for High Sierra and Sierra started causing a Kernel Panic after waking from sleep.
In this article, I will give you the lowdown of the issue. In the end, I will also give you a workaround until Apple releases a fix.
If you are interested in the 2018-004 Security Update Wake from Sleep issue you can read my report Below.
If you have the issue on a 2018-2019 13″ MacBook Pro/Air Please do not hesitate to Contact Me.
3. This issue does NOT affect most 10.14.6 users.
I tried time and time again to reproduce this issue. Having both a 2018 and 2019 15″MacBook Pro for testing, I figured that I would be able to reproduce the issue. Having FaceTime.app open for hours and using Zoom Conference call for 4 hours, produced zero crashes. This could be a clue as to an additional cause on the reported users computers, but I’m not sure.
4. Kernel Panic Reports
What do the Kernel Panic Reports look like? Looking over the report it looks like BridgeOS is crashing. Below is a sample report.
{“caused_by”:”unknown”,”macos_version”:”Mac OS X 10.14.6 (18G84)”,”os_version”:”Bridge OS 3.6 (16P6568)”,”macos_system_state”:”running”,”incident_id”:”6DCB8540-C363-4FC9-999E-9E38E276621A”,”timestamp”:”2019-07-25 15:44:33.33 +0000″,”bug_type”:”210″}
{
“build” : “Bridge OS 3.6 (16P6568)”,
“product” : “iBridge2,3”,
“kernel” : “Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010”,
“incident” : “6DCB8540-C363-4FC9-999E-9E38E276621A”,
“crashReporterKey” : “c0dec0dec0dec0dec0dec0dec0dec0dec0de0001”,
“date” : “2019-07-25 15:44:33.08 +0000”,
“panicString” : “panic(cpu 0 caller 0xfffffff01bca5bec): \”void AppleEmbeddedPCIeUpLinkMgmt::_linkInterruptAction(IOInterruptEventSource *, int): \” \”A link timeout has been seen after 100000 microseconds and 49999 iterations.\”@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/AppleEmbeddedPCIeUpLinkMgmt\/AppleEmbeddedPCIeUpLinkMgmt-76.260.2\/AppleEmbeddedPCIeUpLinkMgmt.cpp:3982\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P6568\nmacOS version: 18G84\nKernel version: Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010\nKernelCache UUID: DB4E28E6354462E8ADC412A804EB32E1\nKernel UUID: 9FC93C85-B7C5-3723-92B7-293273AB9C4F\niBoot version: iBoot-4513.270.14\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x40504000200\nPCIeUp link state: 0x94721611\nPaniclog version: 13\nKernel slide: 0x000000001559c000\nKernel text base: 0xfffffff01c5a0000\nmach_absolute_time: 0xa75d527f88\nEpoch Time: sec usec\n Boot : 0x5d37ad8f 0x000c3155\n Sleep : 0x5d39a45e 0x000defae\n Wake : 0x5d39ab5f 0x0006d1c2\n Calendar: 0x5d39ce41 0x000cb6eb\n\nPanicked task 0xffffffe000881680: 8160 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000c4b3e0, backtrace: 0xffffffe01633b590, tid: 280\n\t\t lr: 0xfffffff01c6ae2a4 fp: 0xffffffe01633b620\n\t\t lr: 0xfffffff01c79b5a4 fp: 0xffffffe01633b760\n\t\t lr: 0xfffffff01c679610 fp: 0xffffffe01633b770\n\t\t lr: 0xfffffff01c6ad848 fp: 0xffffffe01633bae0\n\t\t lr: 0xfffffff01c6adbc0 fp: 0xffffffe01633bb20\n\t\t lr: 0xfffffff01c6ada14 fp: 0xffffffe01633bb40\n\t\t lr: 0xfffffff01bca5bec fp: 0xffffffe01633bbd0\n\t\t lr: 0xfffffff01cb35fc4 fp: 0xffffffe01633bc10\n\t\t lr: 0xfffffff01cb34ad8 fp: 0xffffffe01633bc50\n\t\t lr: 0xfffffff01cb3434c fp: 0xffffffe01633bc90\n\t\t lr: 0xfffffff01c684614 fp: 0x0000000000000000\n\n”,
“panicFlags” : “0x2”,
“otherString” : “\n** Stackshot Succeeded ** Bytes Traced 112560 **\n”,
“macOSPanicFlags” : “0x0”,
“macOSPanicString” : “BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available”,
“memoryStatus” : {“compressorSize”:0,”compressions”:0,”decompressions”:0,”busyBufferCount”:0,”pageSize”:16384,”memoryPressure”:false,”memoryPages”:{“active”:8141,”throttled”:0,”fileBacked”:10933,”wired”:10886,”purgeable”:0,”inactive”:5798,”free”:3029,”speculative”:2344}},
5. Why rolling back will NOT work.
You might think, what if I roll back to a previous version of Mojave like 10.14.5? In the past, this might have worked! It will NOT work when the issue is caused by BridgeOS. Apple has made it impossible to roll back the version of your T2 BridgeOS.
After you updated to 10.14.6, your BridgeOS was also updated. If you try to reinstall 10.14.5, this version will still work but the newer BridgeOS will still be installed. This is also why if you got your MacBook Pro replaced at the Apple Store, the issue could STILL be happening to you.
The only way you could get this to work is if you got ahold of a 10.14.5 system on BridgeOS version 16.16.5601 or lower.
6. Built-In FaceTime Camera
The crash ONLY happens when you use the MacBook Pro Built-In FaceTime Camera. It does not matter what you do. From the many reports that I have looked through, the crash could happen the very second you activate the camera or 2 hours after. Most of the reports seem to be from 10min to 1 hour of use.
7. Camera Software that causes the KP’s
The following software can cause your Mac to Kernel Panic
FaceTime.app
WebEx
Zoom
Slack
Google Hangouts
Skype
Teams
gotomeeting
BlueJeans
You get the idea, basically ANY application that uses the Built-In FaceTime Camera.
8. Workarounds
Most issues like this have some type of workaround. Sometimes a workaround is found by accident or after hours of testing. This time around a few users on the Apple Discussion Forums found at least one workaround.
Plug in an additional Web Camera. This could be a USB Web Camera or even a monitor with a built-in camera like the Apple 27″ ThunderBolt Display.
You don’t even have to use the secondary camera. For some reason with the second camera plugged in reports say that you can use the built-in FaceTime Camera without crashes. Found by user edgonz305
Run a Windows Fusion VM with Skype in that VM. The problem does not occur using integrated camera. This is not a solution for everyone, but for me it works better than using an external camera. Additional workaround from OaSOakover
You can prevent the crashes by just disabling video on the meeting. (This one is pretty obvious if you don’t need to use the FaceTime Cam)
macOS Catalina Beta may fix the issue. Reported by Commenter Dave!
9. Will Apple fix this issue? 10.14.6 Supplemental Update #3 ?
With the end of support coming up fast for Mojave, will Apple fix this issue? I think the answer is YES. This is coming from reports that Apple DOES know about the issue and is still investigating. My guess is that Apple will release one final Supplemental Update to fix this.
If you or any of your users are having this issue, please contact Apple Support.
Zoom Response -“We found it not only influences ZOOM but also FaceTime, Skype and other Camera involving Apps, we are still working with Apple to fix it but currently as a workaround, please turn off your video when joining ZOOM meetings or use external camera by USB.”
If you have any information on the 10.14.6 FaceTime Kernel Panic issue that you would like added to this article, please Contact Me.
Today Apple released Xcode 11 GM Seed 2 to Developers.
The Xcode 11 GM Seed 2 was released today. Usually GM or Gold Master means that this Build Version is the final shipping version. In this case a 2nd GM Seed was released.
This article is meant to save you time going through the notes to find what is new and what is still leftover from the last beta. I went through both Xcode 11 GM (11A419c) and Xcode 11 GM Seed 2 (11A420a) release notes to find all the changes. I also included the entire patch notes list as an archive. When Apple releases new patch notes the previous patch notes are overwritten and taken down.
Summary of New Xcode 11 GM Seed 2 Patch Notes
0 New Features
2 New Resolved issues
2 New Known Issues
0 New Deprecations
A Full List of changes is listed below, along with the full patch notes list.
Asset Catalog – Fixed an Asset Catalog bug that prevented named colors from being found at runtime when running on iOS 11. (54325712)
Build System – By default, Xcode’s new build system doesn’t detect changes in directories declared as inputs to shell script build phases. Enabling the build setting USE_RECURSIVE_SCRIPT_INPUTS_IN_SCRIPT_PHASES causes it to do so. However, if any of the files inside such a directory are generated by a task that depends on the output of the script phase, then a dependency cycle error is emitted and must be resolved by restructuring the target. (41126633)
New Known Issues
Asset Catalog – When an asset is localized in the asset catalog, another localized resource must exist in the corresponding lproj directory for the app to use that language at runtime. An empty strings file can serve this purpose. (49565973)
Simulator – CarPlay does not work in iOS 13 simulators. (54492162)
Yesterday Apple released iOS 13.1 Beta 3 to Developers.
This article is meant to save you time going through the notes to find what is new and what is still leftover from the last beta. I went through both iOS 13.1 Beta 2 and the new iOS 13.1 Beta 3 (17A5837a) release notes to find all the changes. I also included the entire patch notes list as an archive. When Apple releases the next Beta patch notes the previous patch notes are overwritten and taken down.
Summary of New iOS 13.1 Beta 3 Patch Notes
1 New Features
1 New Resolved issues
2 New Known Issues
2 New Deprecations
A Full List of changes is listed below, along with the full patch notes list.
SwiftUI – (NOTE: this is a change of wording) BindableObject is replaced by the ObservableObject protocol from the Combine framework. (50800624)You can manually conform to ObservableObject by defining an objectWillChange publisher that emits before the object changes. However, by default, ObservableObject automatically synthesizes objectWillChange and emits before any @Published properties change.// RoomStore.swift import Foundation class RoomStore: ObservableObject { @Published var rooms: [Room] = [] } struct Room: Identifiable { var id: UUID var name: String var capacity: Int var hasVideo: Bool } // ContentView.swift import SwiftUI struct ContentView: View { @ObservedObject var store: RoomStore var body: some View { NavigationView { List(store.rooms) { room in RoomCell(room: room) } .navigationBarTitle(“Rooms”) } } } @ObjectBinding is replaced by @ObservedObject.
2. New Resolved Issues in iOS 13.1 Beta 3
Media Player – Fixed an issue where playback stopped if an app using MediaPlayerFramework to play catalog content was backgrounded. (54131440)
3. New Known Issues in iOS 13.1 Beta 3
Metal – In iOS 13, if you refer to a sparse texture in an argument buffer you must explicitly call use(:usage:stages:) on the texture rather than calling useHeap(🙂 on the heap. (54605833)
Sidecar – To use Sidecar with iPadOS 13.1 beta 2 or later, macOS Catalina Beta 8 or later is required. (54903543)
4. New Deprecations in iOS 13.1 Beta 3
Networking – Removed support for FTP and File URL schemes for Proxy Automatic Configuration (PAC). HTTP and HTTPS are the only supported URL schemes for PAC. This affects all PAC configurations including, but not limited to, configurations set using Settings, System Preferences, Profiles, and URLSession APIs such as connectionProxyDictionary and CFNetworkExecuteProxyAutoConfigurationURL(::::). (28578280)
SwiftUI – SwiftUI APIs deprecated in previous betas are now removed. (52587863, 53310683)
Today Apple released macOS Catalina 10.15 (19A558d) Beta 8 to Developers.
This article is meant to save you time going through the notes to find what is new and what is still leftover from the last beta. I went through both Beta 7 and the new Catalina 10.15 Beta 8 (19A558d) release notes to find all the changes. Like usual, I also have included the entire patch notes list as an archive. When Apple releases the next Beta patch notes, the previous patch notes are overwritten and taken down.
Summary of Beta 8 Patch Notes
3 New Features
3 New Resolved issues
2 New Known Issues
4 New Deprecations
A Full List of changes is listed below, along with the full patch notes list.
Report your bugs NOW!
This may be the final beta left to test. The public Release of Catalina is only about one month away. You will want to get any bugs that you find into Apple now. If you get them in now, they could be fixed in the current beta cycle instead of waiting until after September’s release date. If you wait it could be months before the fix is put into a dot release combo update.
Keep in mind, I can only publish public data. If you are an AppleSeed for IT member you can access additional 10.15 Catalina Beta Patch Notes in the AppleSeed Portal. AppleSeed information is protected by Apple’s NDA.
Some fixes are not going to be listed. Many issues are from #MacAdmins who have filed FeedBack Requests and Enterprise Support tickets. Most of these issues are resolved but are never publicly noted.
1. New Features in Beta 8
SwiftUI – NSManagedObject now conforms to ObservableObject. The new @FetchRequest property wrapper can drive views from the results of a fetch request, and managedObjectContext is now included in the environment. (50280673)
SwiftUI – BindableObject is replaced by the ObservableObject protocol from the Combine framework. (50800624)You can manually conform to ObservableObject by defining an objectWillChange publisher that emits before the object changes. However, by default, ObservableObject automatically synthesizes objectWillChange and emits before any @Published properties change.// RoomStore.swift import Foundation class RoomStore: ObservableObject { @Published var rooms: [Room] = [] } struct Room: Identifiable { var id: UUID var name: String var capacity: Int var hasVideo: Bool } // ContentView.swift import SwiftUI struct ContentView: View { @ObservedObject var store: RoomStore var body: some View { NavigationView { List(store.rooms) { room in RoomCell(room: room) } .navigationBarTitle(“Rooms”) } } } @ObjectBinding is replaced by @ObservedObject.
SwiftUI – The RangeReplaceableCollection protocol is extended to include a remove(atOffsets:) method and the MutableCollection protocol is extended to include a move(fromOffsets:toOffset:) method. Each new method takes IndexSet instances that you use with the onMove(perform:) and onDelete(perform:) modifiers on ForEach views. (51991601)
2. New Resolved Issues in Beta 8
Apple TV – Support for signing in with an account from a different country is now available. (51240948)
iWork – Attempting to open iWork documents in Finder will no longer unexpectedly create a .cpgz file if the corresponding iWork app isn’t installed. (40693892)
Mac Catalyst – Fixed an issue where event handling in extension contexts sometimes produced unexpected results, including failure to deliver trackpad pinch and zoom gestures. (50145462)
3. New Known Issues in Beta 8
Mac Catalyst – Catalyst apps using UIDocumentInteractionController might quit unexpectedly. You can work around this issue by excluding UIDocumentInteractionController functionality with target macros. (48878552)
SwiftUI – Apps containing SwiftUI inside a Swift package might not run on versions of iOS earlier than iOS 13. (53706729)Workaround: When back-deploying to an OS which doesn’t contain the SwiftUI framework, add the -weak_framework SwiftUI flag to the Other Linker Flags setting in the Build Settings tab. See Frameworks and Weak Linking for more information on weak linking a framework. This workaround doesn’t apply when using dynamically linked Swift packages which import SwiftUI.
4. New Deprecations in Beta 8
EndpointSecurity – (Left over from last time as it was incorrectly noted that this was removed) The kauth API has been deprecated. (50419013)
SwiftUI – Complex overloads for the background(:alignment:) and border(:width:) modifiers are deprecated. Use shapes in a background(:alignment:) or overlay(:alignment:) to draw these instead. (53067530)
SwiftUI – The identified(by:) method on the Collection protocol is deprecated in favor of dedicated init(:id:selection:rowContent:) and init(:id:content:) initializers. (52976883, 52029393)The retroactive conformance of Int to the Identifiable protocol is removed. Change any code that relies on this conformance to pass .self to the id parameter of the relevant initializer. Constant ranges of Int continue to be accepted:List(0..<5) { Text(“Rooms”) } However, you shouldn’t pass a range that changes at runtime. If you use a variable that changes at runtime to define the range, the list displays views according to the initial range and ignores any subsequent updates to the range.
SwiftUI – Several extensions to the Binding structure are removed. (51624798)If you have code such as the following:struct LandmarkList: View { var landmark: [Landmark] @Binding var favorites: Set var body: some View { List(landmarks) { landmark in Toggle(landmark.name, isOn: self.$favorites.contains(landmarkID)) } } } Define the following subscript on the Set structure:extension Set { subscript(member: Element) -> Bool { get { contains(member) } set { if newValue { insert(member) } else { remove(member) } } } } Then, change self.$favorites.contains(landmarkID) to self.$favorites[landmarkID].
