Apple Seeds Third Beta of macOS Catalina to Developers

[bmansc]

Error installing here too
2019 MBP with TB i9 2.3 with 16 gig

 

[TrueBlou]

worked flawlessly on my MacBook Pro 2018 but in the music app there are still most of the album covers missing

Do you use Apple Music?

I had this problem with beta 2, finally got peeved with it, made a backup of the Music folder, deleted the original, rebooted and started Music up, lo and behold, everything was perfect.

 

[Mike Haas]

Installed on a 2017 13" MBP. Whew!

 

[rjjacobson]

Error installing here too
2019 MBP with TB i9 2.3 with 16 gig

Yes seems to be mostly (all) 2018 machines with TB? I also have same machine in late 2018 version of the 15 inch.

I saw a few 2018 machines worked but from errors I have seen on other sites sounds like it could be related to Touch Bar in some way???

 

[waquzy]

Installed on MBP 2017 13” nTB

The beauty of the non Touch Bar MacBook Pro strikes again! (No offence to anyone)

 

[rjjacobson]

On one site the discussions center on this as the possible error:

PrefPane: installDidFinishWithError - 041-81733: Error Domain=SUOSUErrorDomain Code=200 "An error occurred installing the update." UserInfo={NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing the update., NSUnderlyingError=0x600001726c10 {Error Domain=SUOSUErrorDomain Code=201 "An error occurred installing the update." UserInfo={NSUnderlyingError=0x600001727390 {Error Domain=SUErrorDomain Code=602 "An error occurred installing the update." UserInfo={NSUnderlyingError=0x6000017270c0 {Error Domain=BOSErrorDomain Code=110 "The bridgeOS update doesn't satisfy the given minimum version requirement." UserInfo=0x6000037d0080 (not displayed)}, NSLocalizedRecoverySuggestion=You can try again to complete the installation., SUErrorUpdateServerName=swscan.apple.com, NSLocalizedDescription=An error occurred installing the update.}}, NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing the update.}}}




Update bundle package component's bridge version (17.16.10466.5.18,0) doesn't satisfy minimum requirement (17.16.10496.5.4,0): 1

Comments are that this is related to Touch Bar in some way

 

[bmansc]

Yes seems to be mostly (all) 2018 machines with TB? I also have same machine in late 2018 version of the 15 inch.

I saw a few 2018 machines worked but from errors I have seen on other sites sounds like it could be related to Touch Bar in some way???

I was thinking it was TouchBar related as well.

 

[ludeboy12]

Doesn't work on my iMac Pro. No Touch Bar here obviously.

 

[rjjacobson]

It is like the file is downloaded and it goes back to checking it and failing with this error I mentioned...earlier.

Is there a place the file is installed so I can delete and start the full download over again?



PrefPane: installDidFinishWithError - 041-81733: Error Domain=SUOSUErrorDomain Code=200 "An error occurred installing the update." UserInfo={NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing the update., NSUnderlyingError=0x600001726c10 {Error Domain=SUOSUErrorDomain Code=201 "An error occurred installing the update." UserInfo={NSUnderlyingError=0x600001727390 {Error Domain=SUErrorDomain Code=602 "An error occurred installing the update." UserInfo={NSUnderlyingError=0x6000017270c0 {Error Domain=BOSErrorDomain Code=110 "The bridgeOS update doesn't satisfy the given minimum version requirement." UserInfo=0x6000037d0080 (not displayed)}, NSLocalizedRecoverySuggestion=You can try again to complete the installation., SUErrorUpdateServerName=swscan.apple.com, NSLocalizedDescription=An error occurred installing the update.}}, NSLocalizedRecoverySuggestion=You can try again to complete the installation., NSLocalizedDescription=An error occurred installing the update.}}}




Update bundle package component's bridge version (17.16.10466.5.18,0) doesn't satisfy minimum requirement (17.16.10496.5.4,0): 1
[doublepost=1562097957][/doublepost]

Doesn't work on my iMac Pro. No Touch Bar here obviously.

Maybe newer machines then?

 

[Ledurpabbi]

The TouchBar is still trying to make me miserable

 

[waquzy]

The TouchBar is still trying to make me miserable

The TouchBar is absolutely pointless and cumbersome imo. The only good thing about it is the Touch ID.

 

[Ejsup1]

It’s a problem with the T2 Chip Newer Drive OS is needed

 

[Mike Haas]

While I still had B2 running on the Mac, home sharing of movies and TV content in the Apple TV app worked running a newly updated iOS13 beta 3. It's broken again with both devices running B3. Home sharing of Music never worked running either beta. I'm betting it doesn't work on the Apple TV Public Beta 1 either. That's ok...I have hope it will all work out...

Build # if anyone wants it for B3 is 19A501i

 

[boccabella]

Still no GeoPort support?

 

[KibJ]

Same bridgeOS error here on Macbook Air 2018

 

[4389842]

If you are currently on Beta 2, 'softwareupdated' will install a bunch of packages to /Library/Updates/041-81733.

In this location there is 041-81733.en_GB.plist which has a line:

<bridge-version build-version="17.16.10496.5.4" build-group="0"/>

This fails to install for reasons mentioned earlier in this thread.

HOWEVER, if you re-install the Developer Beta Profile, it will instead download a larger set of packages to /Library/Updates/041-81731.

041-81731.en_GB.plist has an internal reference to build number 19A501i which is more recent than Beta2 which is 19A487i

The download finished and I am greeted with a functional installer Window...

EDIT: it is now installing just fine. Moral of the story: re-install the profile

 

[zorinlynx]

I decided to take the risk and install Catalina on my main MBP (because I'm impatient and stupid), and unfortunately had to downgrade back to Mojave. There were enough little bugs in Catalina that made it frustrating to work on at times.

Specifically, for some reason, Audacity just wouldn't record properly. It would detect the mic (both built-in and a USB mic), and I could hit record, but then Audacity wouldn't actually record any audio. What's really bizarre, other apps worked just fine (i.e Audio Hijack). Furthermore, because of the change to how system files are stored on a read-only volume, Backblaze stopped functioning as it relies on a hidden folder on the root-level of the HD to keep track of your hard disk(s).

I know the Backblaze issue will be resolved before the official release, not sure about Audacity though...which would really suck if it doesn't work.

It's the same deal with iOS 13.

I started playing with the betas, remembering how smooth Mojave and iOS 12 betas were, but the 13/Catalina betas have a lot more issues than the 12/Mojave betas did.

I suspect Apple decided to do some deeper changes under the hood and it has manifested in bugs. I'm fairly sure they'll be fixed, but I'm going to be a lot more cautious upgrading to iOS 13 when the time comes than i was with 12. (At least with MacOS, if Catalina sucks it's trivial to go back to Mojave since there is no code signing for MacOS installs)

 

[Ledurpabbi]

You sir are a genius.

If you are currently on Beta 2, 'softwareupdated' will install a bunch of packages to /Library/Updates/041-81733.

In this location there is 041-81733.en_GB.plist which has a line:

<bridge-version build-version="17.16.10496.5.4" build-group="0"/>

This fails to install for reasons mentioned earlier in this thread.

HOWEVER, if you re-install the Developer Beta Profile, it will instead download a larger set of packages to /Library/Updates/041-81731.

041-81731.en_GB.plist has an internal reference to build number 19A501i which is more recent than Beta2 which is 19A487i

The download finished and I am greeted with a functional installer Window...

EDIT: it is now installing just fine. Moral of the story: re-install the profile

View attachment 846222

 

[urgs]

Three questions about Third Beta of macOS Catalina to Developers:

- Does it allow to make Time Machine backups into APFS disks?

I see no benefit in using APFS for time machine.
Some features as Copy-On-Write and Cloning are even disqualifying APFS as a file system for backups.

 

[bmansc]

If you are currently on Beta 2, 'softwareupdated' will install a bunch of packages to /Library/Updates/041-81733.

In this location there is 041-81733.en_GB.plist which has a line:

<bridge-version build-version="17.16.10496.5.4" build-group="0"/>

This fails to install for reasons mentioned earlier in this thread.

HOWEVER, if you re-install the Developer Beta Profile, it will instead download a larger set of packages to /Library/Updates/041-81731.

041-81731.en_GB.plist has an internal reference to build number 19A501i which is more recent than Beta2 which is 19A487i

The download finished and I am greeted with a functional installer Window...

EDIT: it is now installing just fine. Moral of the story: re-install the profile

View attachment 846222

You are awesome! Can you fix my streaming issue with TVOS? HAha. Mostly with YouTube and DirecTv.

 

[4389842]

You sir are a genius.

No dice... it fails again later on, specifically on my MBP2018, with the same bridges error as before but now from the process 'osinstallersetupd'. Disappointing.

 

[bmansc]

No dice... it fails again later on, specifically on my MBP2018. Still checking...

Well
Darn

 

[mikefla]

If you are currently on Beta 2, 'softwareupdated' will install a bunch of packages to /Library/Updates/041-81733.

In this location there is 041-81733.en_GB.plist which has a line:

<bridge-version build-version="17.16.10496.5.4" build-group="0"/>

This fails to install for reasons mentioned earlier in this thread.

HOWEVER, if you re-install the Developer Beta Profile, it will instead download a larger set of packages to /Library/Updates/041-81731.

041-81731.en_GB.plist has an internal reference to build number 19A501i which is more recent than Beta2 which is 19A487i

The download finished and I am greeted with a functional installer Window...

EDIT: it is now installing just fine. Moral of the story: re-install the profile

View attachment 846222

Yeah tried that too and it also failed!

Mike

 

[TheSkywalker77]

So, no iOS 13 beta 3 on my 7 plus.

And macOS seems to not want to install at all.

Time to wait another two weeks.

 

[vbctv]

2018 Mac mini, reinstalled profile, looked all good installing Beta 3 update, now crashing on boot. Now going to have to go back to Mojave, good thing I keep TM backs. Something major wrong with T2 chip and Beta 3. Doubtful for Apple fix this week with holiday... This is reason they should never release during holiday week... Caution to everyone else if you do get it to install, it still may crash...