Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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. :p
I am, though I haven’t yet installed this second beta. But IMO, any 1.0 software is essentially a beta version, chock full of bugs and incomplete features. There isn’t much difference between an official beta and a release build this early in a product’s lifecycle. I have detected some differences between the first 1.1 beta and 1.0.2 release in terms of Safari’s partial instability, which oddly I haven’t seen again since the first day of 1.1. I’m guessing this second beta rolls 1.0.3 updates into the beta along with additional bug fixes for 1.1 features since you cannot install 1.0.3 once you’ve updated to the beta.

Note that 1.0.3 had a feature that came in 1.1 beta first, the ability to reset the Vision Pro if you forget your PIN code, which likely means that single feature is completed. It’s pretty common for developers to merge fixes and features between multiple code branches, so 1.0.3 has a bit of 1.1 beta and vice versa.
 
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.
There’s no such thing as bug free code and no such thing as code being shipped without known bugs. With the complicated software these days with millions of lines of code, it is humanly impossible to have no bugs. On my last major project before I went to contractor status, we had shipping versions with at least 2,000 known bugs, most of them minor but a few with quite high severity but low priority. The latter means that the bug is quite nasty, bug rarely shows up, or is impossible to reproduce. I wouldn’t be surprised if all of Apple’s OS software contains tens of thousands of known bugs, whether they are release versions or not.
 
Anyone else feels like visionOS leaks memory like a sieve? When it does not crash by itself, you'll end up rebooting it nevertheless at least once a day to keep it functional.
 
I wish Apple would make user accounts possible similar to the Mac. Guest mode is okay but a pain to start and use.
 
  • Like
Reactions: jw77777
visionOS 1.1 beta 3 (21O5197a) - February 20, 2024

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)

3rd Party Apps

Known Issues

  • Some third-party apps, including Microsoft Teams, might crash on launch or during use when Accessibility options are enabled. (122506670) (FB13595783)
    Workaround: Disable any Accessibility options before launching impacted apps.

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

Resolved Issues

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

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

Resolved Issues

  • Fixed: Immersive apps might not resume automatically if Apple Vision Pro is taken off and put back in a different location. (122561314)

Lock Screen

Resolved Issues

  • Fixed: Passcodes containing a character which uses a diacritic can’t be used to unlock Apple Vision Pro. (122551154)

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

Resolved Issues

  • Fixed: 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)
  • Fixed: RealityKit reports incorrect visualBounds for Attachments, which may impact entity placement. Larger attachments may be clipped due to the incorrect visualBounds values. (121887607)

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.
  • 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)

ShaderGraph Materials

Known Issues

  • ShaderGraph material node compositions might result in invalid visual output. (122723231)
    Workaround: Avoid using a common asset node for both a surface shader and a geometry modifier within a single material or duplicate the asset node if needed.

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

Resolved Issues

  • Fixed: Siri may be unusable. (122361345)
  • Fixed: Unable to invoke Siri in simulator. (122514562)

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(for:) method 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)
 
  • Like
Reactions: CodeSpyder
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.