Just a heads up to others; I installed the 15.1 beta this morning on a perfectly functional HomePod and after restarting, it's been completely unable to connect to the Internet. Any Siri request is met by "I'm having trouble connecting to the Internet" and refers to me to the Home app. The Home app has no information, and the HomePod has presence on the WiFi network, and the network is functioning fine. I performed a full device reset, with the red light and all, and after setting it up again, it worked for about 15 minutes before losing Internet again. Something to do with the beta, clearly, as it was working up until the installation of 15.1. Reported via Feedback, but, wanted to mention here in case others have an issue.

I've not seen this one covered elsewhere, and whilst I've already tried the Feedback Assistant to get it to Apple, I'm not sure if it's being picked up or looked at there...The problem I've encountered is that whenever I use Disk Utility to create an APFS encrypted volume within a container, it works, but only until I reboot. When I reboot, after looking in I'm prompted for the password for the volume. I'm 100% certain of the passphase I used, but, after entering it the UI "shakes" to indicate the passphrase was wrong. If I try again, either with the same passphrase, or, trying something like my login password, the UI will go away, but, the volume does not mount.In Disk Utility I get the error:Could not mount “Data”. (com.apple.DiskManagement.disenter error 49218.)And that's that. I've now lost some data permanently, which is a bit frustrating. I excluded that volume from TimeMachine backups to ensure that there weren't unencrypted copies of the data floating about anywhere (even though my TM volume is encrypted (HFS+, not APFS)).Sadly, this is 100% repeatable, and I've had it happen a few times. Thankfully, not much data has been lost forever, but, it makes it tough to trust APFS Encryption.Steps that I took to do this:1) Had a new HD inserted in my MacPro (2019)2) Drive was formatted with GUID partition map3) Initial APFS container created (no encryption)4) Once Container existed, as well as initial whole-disk-sized APFS volume, I clicked on the Container and "+" to create a new container.5) Chose APFS Encryption as the FS, generated a passphrase with 1Password, and am certain it's accurate. 6) Volume mounted just fine, was able to read/write data to it no problem7) RebootedAnd that's where it went off the rails. Has anyone had better and more reliable experience with APFS Encrypted volumes?

Hi,I'm not sure when this may have changed, but, I was looking to modify the trust settings for some certificates that I have, and for some reason, Keychain Access doesn't seem to have this functionality any longer. I know about the command-line "security" application, and I will look to see if it can do it, but the GUI application used to permit adjustment of trust by simply double-clicking on a certificate and changing the Trust values.Now, selecting a certificate and double clicking, or trying Get Info, does nothing. I don't know if this is a bug to report, or, just a change in functionality...or, Just Me (tm).Can anyone find a way to adjust certificate trust in the Keychain Access application on High Sierra (latest beta, Dev 5, for example)?