Post not yet marked as solved
Using 12.0.1 (21A558) (RC), Teams will not work if I receive an incoming video stream.
Audio based calls work fine, however, as soon as someone joins a Teams session and sends video, Teams will immediately crash. In earlier Monterey Betas it would crash maybe half of the time, but, a restart of Teams would likely let it work. However, with later betas, and with the RC, I am completely unable to run Teams on macOS with an incoming video.
Tried running from the command line to get useful information, nothing, but, the logs that Teams generates itself show the crashes and it's 100% repeatable.
At the moment, the only way I can use Teams is if I run it in a Linux or Windows virtual machine.
(2019 MacPro)
Post not yet marked as solved
Telnet was removed from macOS about 3 years ago. You won't find it in macOS Big Sur, Catalina, Mojave or macOS High Sierra. There are some alternatives in packaging systems such as "homebrew" but, the preference is to not use telnet due to the inherent security risks of doing so. If you think you need telnet, see if whatever you are accessing can use ssh instead. It's also possible to do some things using netcat (nc), which is installed by default.
Post not yet marked as solved
I found a much easier fix for this problem than unpairing and pairing.I merely went to the iCloud settings on my phone, went to Reminders, and turned them off. I then deleted them from my phone (as the server-side version was correct), turned Reminders back on, and after they appeared on my phone, they also appeared on my Watch.
Post not yet marked as solved
I was hoping this would do the trick for me - I did the force restart, as you did, but, only pressed the top button for about 30 seconds, and that did restart the iPad Pro 12.9 inch model, but, alas, even after the slowly crawling installation progress meter, it has not completed. Seems like a semi brick state. Hoping to poke at it more...Update: It all went horribly wrong. I was forced into only a DFU mode restore, which put things back to 13.1.2. No amount of trying to get the (now pulled) beta installed worked. Sadly, the last time I made a backup of my iPad was a month ago, which means I'm weeping over lost LumaFusion edits...that was the only thing local on the iPad that wasn't backed up. Doh.
I've had this happen for all of the iOS 13 betas; but it was always related to my running VPN software. Apple servers are blacklisting a variety of IP addresses that happen to be VPN endpoints. Not sure why, other than perhaps they had some dodgy traffic - but not being able to verify the download was always a symptom. In my case, I just moved to another VPN server or endpoint, and it would typically work.
Post not yet marked as solved
Unfortunately, I wasn't able to get the backup and restore to work.Old: XS Max, 13.1b4New: 11 Pro Max, 13.1b4I did a full backup and sync of Old before plugging New into computer running Catalina Beta (which may be the problem here).The Welcome to your New Phone screen comes up, and it lets me select the backup I just made of Old for a Restore, asks for the password, and then promptly stops and returns to the "welcome to your new phone page".Console says:error09:39:15.476526+1000AMPDevicesAgentno XPC UI connection after waiting 2.0 seconds!error09:39:15.476567+1000AMPDevicesAgentfailed to start device restore from backup (-128)error09:39:15.477464+1000com.apple.amp.devicesuierror restoring backup: Error Domain=NSOSStatusErrorDomain Code=-128Which doesn't bode well. I'll try a system restart, tried rebooting the 11 Pro Max, but, still can not restore.UPDATE:Got it to work. Had to disable FindMyiPhone first. There is no warning in Catalina about deactivating that ahead of a restore. There is in Mojave. Things are now progressing!
Post not yet marked as solved
A good point, and one that stung me a few years ago.I believe it was the iPhone X. The current iOS betas at the time were not available for the iPhone X at initial delivery or pickup time. As a result, I had to start with a "new device" - that is insanely time consuming, as the syncing of applicaitons and data is painfully slow over USB (and even slower over WiFi).Since a new Beta came out today, and there is no Restore image for the 11/Pro/Max range, I suspect that if you're getting your phone on Friday, you'll either have to set it up as new, or, hope that a new beta comes out in a couple of weeks that you can put 13.1 on. I've pretty much resigned myself to spending tomorrow (hooray for being Australian, living in the future!) doing a new-device-setup on my 11 Pro Max.
Post not yet marked as solved
Yep, same exact issue here. Retina 5K iMac, though -- but the symptoms were identical to what you describe. Reported with the Feedback Assistant though, as well.
Post not yet marked as solved
I had this problem with one of the earlier watchOS 6 betas as well - it turns out that it was syncing music playlists from my iPhone. I had never enabled that, but, one of the betas apparently did, which prevented a second beta from being able to be installed. Check on the watch under Settings -> General -> Usage to see if this is the same for you. You can disable playlist syncing in the Watch app on your iPhone.
Okay, fixed.1) Reset Apple TV 4K (did not do Reset and Update, just Reset)2) Get it working again (sign in to iCloud, sort out WiFi, etc - easiest done with tapping with nearby device)3) Run Apple Configurator 2 Beta (latest beta)4) Re-pair Apple TV 4K with computer5) Install profile with freshly paired Apple TV 4K6) Restart Apple TV7) Check for software updatesHad to re-install all my apps (annoying) but, it seemed to work this time. 2 minutes remaining on the download...
Hmm, this didn't quite work for me - I had Beta 1 installed just fine, but Beta 2 would not show up in a update check.Tried all the steps you mentioned, even tried a Reset of the Apple TV, but, Beta 2 does not show up. Still runing Beta 1.Did you do a Reset and Update, or just Reset?
Can't help but wonder if this is a 32bit issue - did you happen to check to see if any of those moved extentions are 32 bit?I ran through the System Report and got rid of anything that was 32bit, and am trying the installation on a machine that isn't crucial now. Fingers crossed.
