Apple Releases Second Beta of visionOS 1.1

[MacRumors]

Apple today released the second beta of an upcoming visionOS 1.1 update for developers, allowing them to test new features ahead of the software seeing a public launch. The second beta comes a week after the release of the first beta.

The visionOS beta can be downloaded by going to the Settings app on the device and toggling on developer betas. A registered developer account is required, and Apple recommends making a backup before installing new software.

visionOS 1.1 adds an option to reset the Vision Pro in case you forget your passcode, a feature that was also just released to the public with visionOS 1.0.3 yesterday. Previously, a forgotten passcode would require the Vision Pro to be brought to Apple to reset it.

The update brings support for iMessage Contact Key Verification and it adds Apple device management to the Vision Pro. With this functionality, IT departments at companies and educational institutions can manage Vision Pro headsets in the same way they manage iPhones, iPads, and Macs.

According to Apple's beta notes, users can now reposition volumetric scenes closer than before, enabling easier direct interaction with the volumetric scene content. That means objects can be placed closer to you.

Apple has also improved Personas in visionOS, making them look more natural and lifelike than before.

Article Link: Apple Releases Second Beta of visionOS 1.1

 

[coffeemilktea]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

 

[vertsix]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

I don't understand why people like you are so invested in what others do.

 

[nfl46]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

Mind your business. I paid my $4k for me to do as I please.

 

[Scott6666]

I’m wearing my headset right now and checking this on my phone

 

[jw77777]

Nice, they added the AVP to Find My devices.

 

[PTVMan]

Nice, they added the AVP to Find My devices.

That's a great improvement.

 

[G5isAlive]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

Imagine coming to an article of interest and having to not wade through the snark of those that will never buy the device.

Naaaa dream on LOL

BTW, who dictates what device people use beta software on. I think if Apple was really concerned they would keep the doors locked tighter.

 

[TallGuyGT]

I installed it after seeing how much it appeared to improve personas. But it was super buggy compared to the release version and I regret it. Hopefully beta 2 is more stable.

 

[Realityck]

Spoiler: visionOS 1.1 Beta 2 Release Notes

General​

Resolved Issues​

• Fixed: Apps built for visionOS changing scene types or upgrading from a compatible app will crash on launch if previously launched on a device. (121478050)

Accessibility​

Resolved Issues​

• Fixed: The AccessibilityShortcut preference is reset if VoiceOver is toggled via triple-click of the crown immediately after completing setup. (121466353)

App Placement​

New Features​

• Near-user boundary for volumetric scenes have been modified. Users will now be able to reposition volumetric scenes much closer than before, which will enable easier direct interaction with the volumetric scene content. (120926205)

App Store Submission​

Known Issues​

• Apps built for visionOS are unable to use the front-facing-camera UI Required Device Capability. (121465787)
  Workaround: Remove the front-facing-camera UIRDC for apps built for visionOS.

Control Center​

Resolved Issues​

• Fixed: Opening Control Center during tracking fail or while transitioning into Travel Mode will lead to the Control Center indicator disappearing. (119676121)

Known Issues​

• The Control Center indicator might be missing. (121071017)
  Workaround: Reboot your Apple Vision Pro.

Immersive Space​

Known Issues​

• Immersive apps might not resume automatically if Apple Vision Pro is removed outside of the safe area. (122561314)
  Workaround: Double-click the Digital Crown to hide app content. Click it once again to restore app content.

Lock Screen​

Known Issues​

• Passcodes containing a character which uses a diacritic can’t be used to unlock Apple Vision Pro. (122551154)
  Workaround: Use the Forgot Passcode flow to reset your Apple Vision Pro and then create a new passcode without diacritics.

Mac Virtual Display / AirPlay Wireless​

Known Issues​

• Mac Virtual Display and AirPlay are known to conflict when used concurrently. Concurrent usage might result in performance degradation including connection failure. (110475215)

Markup​

Resolved Issues​

• Fixed: Markup is not available for use in the visionOS Simulator. (122125666)

Passcode​

Resolved Issues​

• Fixed: Passcode UI not obscured in screen recording and sharing. (121482327)

Passkeys​

Known Issues​

• Registering passkeys might not work on certain websites. (122217903)

Persona Enrollment​

Resolved Issues​

• Fixed: Eye tracking may not be accurate after Persona capture until the next time you put on Apple Vision Pro. (121630768)

RealityKit​

Resolved Issues​

• Fixed: In multi-scene apps, custom Systems created for each scene are now released when the scene is dismissed. (116190653)

Known Issues​

• Assigning a new VideoPlayerComponent to an Entity that already has one will result in a black video screen. (117087641)
  Workaround: Reuse the existing VideoPlayerComponent or remove the existing one first before assigning the new one.
• RealityKit reports incorrect visualBounds for Attachments, which may impact entity placement. Larger attachments may be clipped due to the incorrect visualBounds values. (121887607)
• A scene associated with the RealityRenderer might be incorrectly registered to a non-RealityRenderer system resulting in a crash. (122392672)

Settings​

Resolved Issues​

• Fixed: Users might not be able to shut down Apple Vision Pro from Settings. (120555236)

Simulator​

Known Issues​

• Simulator might quit unexpectedly when using Apple Studio Display or other 4-channel systems for audio output. (122506938)
  Workaround: Before launching Simulator, switch the audio output of your Mac to a different device such as headphones.

Siri​

Known Issues​

• Unable to invoke Siri in simulator. (122514562)
  Workaround: Developers may validate on actual device hardware.

StoreKit​

New Features​

• New pricing properties price, currency, and currencyCode are now available on Transaction. If an offer was applied to the transaction, a new property offer is available to see information about it (id, type, payment mode), as well as convenience properties offerID, offerType, and offerPaymentMode. (106650768)
• productDescriptionHidden(_ API can be used to configure the visibility of product descriptions in ProductView, StoreView and SubscriptionStoreView instances within a view hierarchy. When building with Xcode 15.3, the view modifier can be used even if your app is running on iOS 17.0, iPadOS 17.0, macOS 14.0, tvOS 17.0, watchOS 10.0, visionOS 1.0, or later.
  When implementing a product view style, it can support this new view modifier by checking the descriptionVisibility property on the configuration value. (110414819) (FB12261973)
• You can use SubscriptionStoreView to present promotional offers by adding the subscriptionPromotionalOffer(offer:signature modifier.
  If you’re already using inAppPurchaseOptions(_ modifier to support promotional offers for StoreKit views, you should adopt the new API instead when your app is running on iOS 17.4, iPadOS 17.4, macOS 14.4, tvOS 17.4, watchOS 10.4, visionOS 1.1 or later. Do not use both APIs to apply a promotional offer for the same view. (115358806)

Resolved Issues​

• Fixed: The isEligibleForIntroOffer property and isEligibleForIntroOffer(formethod now reflect ineligibility in cases where a customer would otherwise be eligible for the offer if they weren’t actively subscribed. This means a customer which is not currently eligible for an introductory offer may become eligible in the future.
  Customers who redeem an introductory offer for a given subscription group will continue to never be eligible for another introductory offer in that subscription group. You can detect this case this by checking if any one transaction with a matching subscriptionGroupID has the type property on offer set to introductory. (103604770) (FB11889732)
• Fixed an issue causing the refund request “Done” button to not dismiss the sheet when using StoreKit Testing in Xcode. (117482750)
• Fixed: Apps which configure a SubscriptionStoreView to show terms of service & privacy policy links with automatic or URL destinations will now open the URLs in the default browser. (120985657) (FB13540404)

SwiftUI​

New Features​

• Immersive Space displacement value added to the Environment, indicating when the system has moved an Immersive Space from its default position for an active SharePlay session. (117694400)
• Introduced named SwiftUI coordinate space for Immersive Space. Allows cross-window coordinate conversions to an open immersive space. (118422388)

Resolved Issues​

• Fixed: Volumes using the defaultSize(_: Rect3D, in: UnitLength) modifier to specify size, will now be the specified physical size at all display zooms. (116579319) (FB13240946)
• Fixed: If the display zoom is changed in settings while a volume with a physical size is open, the content might be clipped. (120554484)

UI Frameworks​

Resolved Issues​

• Fixed: Navigation bar display title modes are now respected and result in a smaller or larger navigation bar title. (114283700)

UIKit​

Resolved Issues​

• Fixed: UIApplication. setAlternateIconName(_:completionHandler is not supported in native visionOS apps. This does not affect compatible apps running on visionOS. (120929653) (FB13535833)

Vibrancy​

Resolved Issues​

• Fixed: UILabel.preferredVibrancy only supported semantic label colors, but now it supports all colors.
  let label = UILabel()
  label.preferredVibrancy = .automatic // default value
  label.textColor = .red // label will be rendered as vibrant red.
  
  (115106359)

 

[mattopotamus]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

I've been running developer beta's on my Mac and iPhone for years now. Like to live dangerously.

 

[wilhoitm]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

I love running the Apple Vision Pro Betas, I am an early adopter! I am a leader, not a follower! Don't hate the player! Hate the game! Let's go!

 

[spaxxedout]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

It’s fine. The only problem I had with a beta was my HomePod logic board frying. That product doesn’t have a fan though.

 

[iLuddite]

My eyes!!!

 

[PTVMan]

Does the new beta require re-doing your persona?

 

[yabeweb]

All this betas and updates sound like a rushed release….
But hey , this is the new Apple.

 

[yabeweb]

It’s fine. The only problem I had with a beta was my HomePod logic board frying. That product doesn’t have a fan though.

Nice way to defend Apple!

 

[spaxxedout]

All this betas and updates sound like a rushed release….
But hey , this is the new Apple.

Imagine if Avie was in charge of this OS. He wouldn’t have shipped the home view app drawer that scrolls at 10fps.

 

[chrisn123]

Does the new beta require re-doing your persona?

No. It uses Beta 1 personas

 

[tevion5]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

lol if we're being honest here the Apple Vision Pro 1 is in some sense "beta hardware" so seems appropriate to me!

 

[victorvictoria]

Seems most software tech these days is released in what I'd characterize as Beta+ state of development. The companies' testers and engineers do everything they can to assure whatever SW is stable and functional, but there's no way they can anticipate all the ways endusers will use and misuse the product, and so there comes a cascade of "updates," to mitigate those unanticipated glitches.

 

[lkrupp]

Imagine buying an Apple Vision Pro for yourself, taking it home, and then running beta software on it.

You're technically not supposed to do it on a personal device, yet I wonder how many people on MacRumors are doing this right now.

Lots of them. And when they run into trouble they rant about it and demand to know how to back out of the beta, claiming their work flow has been destroyed and how evil Apple is. Happens all the time. No amount of warnings from MacRumors staff dissuades them.

 

[PTVMan]

No. It uses Beta 1 personas

Thanks!

 

[lkrupp]

Seems most software tech these days is released in what I'd characterize as Beta+ state of development. The companies' testers and engineers do everything they can to assure whatever SW is stable and functional, but there's no way they can anticipate all the ways endusers will use and misuse the product, and so there comes a cascade of "updates," to mitigate those unanticipated glitches.

When I worked for the world’s largest telecommunications company we would get patches to apply to the telephone switch almost on a daily basis. The engineers told us that no matter how hard they tried to ensure all the features worked (call waiting, call forwarding, three-way calling, caller ID, etc) when the public got hold of it there would always be some weird bug that would show up. So I always chuckle when some irate Apple user starts mouthing off about QA going down the tubes, “Doesn’t Apple test this stuff” and so on. And half the time it’s because the irate user is confused about how some feature works, or is trying make it work they way they think it should work.

 

[victorvictoria]

When I worked for the world’s largest telecommunications company we would get patches to apply to the telephone switch almost on a daily basis. The engineers told us that no matter how hard they tried to ensure all the features worked (call waiting, call forwarding, three-way calling, caller ID, etc) when the public got hold of it there would always be some weird bug that would show up. So I always chuckle when some irate Apple user starts mouthing off about QA going down the tubes, “Doesn’t Apple test this stuff” and so on. And half the time it’s because the irate user is confused about how some feature works, or is trying make it work they way they think it should work.

Agreed. Working for an Apple VAR, I asked our chief engineer what percentage of his team's on-site calls to fix network issues were caused by company technicians doing things wrong and taking down networks. He said, "About 95%."