Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,549
39,403


Apple today released a visionOS 1.0.3 update for the Vision Pro headset, marking the first update that Apple has provided since the device launched. The software comes two weeks after the release of the visionOS 1.0.2 update.

Apple-Vision-Pro-with-battery-Feature-Blue-Magenta.jpg

The new visionOS update can be installed by opening the settings app and going to the software update section.

With visionOS 1.0.3, Apple added an option to reset the Vision Pro headset if the passcode set on the device has been forgotten. It also includes unspecified bug fixes. Apple's release notes:
This update provides important bug fixes and adds an option to reset your device if you’ve forgotten your passcode.
The Vision Pro launched without a way to reset the device without first unlocking it with a passcode, so those who did end up forgetting their passcodes had to go to an Apple retail store to reset it. With the update, if a passcode is rejected a certain number of times, users will get an option to erase the Vision Pro.

Note that erasing the Vision Pro does not remove Activation Lock, so a person who stole the headset and used this feature to wipe it would still not be able to log in with their Apple ID.

Article Link: Apple Releases visionOS 1.0.3 With Reset Option for Forgotten Passcode
 
Last edited:
I previously remarked that it was stupid for Apple to require you to take your AVP to an Apple Store if you somehow forgot your passcode, and people tried to mock me for saying that. "How can you forget your passcode?" Stuff like that.

Guess Apple agrees with me that it was stupid.

I think some people mentioned the passcode just not working and they were certain it was correct. Either way, this is a good fix.
 
*Runs to headset to update* It’s been absolutely fantastic and game-changing for my workflow but it has some obvious weird little bugs that are all remedied by restarts, been hoping for some fixes!
Yes. At least for starters, we need either keys on the virtual keyboard to Undo/Redo, or hand gestures. Mmmm… I wonder if in the meantime we could create a custom gesture using the accessibility options currently available.
 
My favorite part of the iPhone OS 1.x and 2.x days was the rapid updates that fixed and added tons of little things all over the place.
Yeah, I’m hoping Apple isn’t slow with adding features over time. Meta adds new features on a near-monthly basis. Quest 2 has had multiple performance upgrades via software updates over the year and is leagues better than it was on its release date. Let’s hope that Apple doesn’t make us wait a year for significant updates, at least initially.

I don’t want to wait until vOS 2 to have some sort of window manager and other basic features.
 
Yes. At least for starters, we need either keys on the virtual keyboard to Undo/Redo, or hand gestures. Mmmm… I wonder if in the meantime we could create a custom gesture using the accessibility options currently available.

My favorite part of the iPhone OS 1.x and 2.x days was the rapid updates that fixed and added tons of little things all over the place.
same we are reliving those classic OG iPhone days again!!
 
I previously remarked that it was stupid for Apple to require you to take your AVP to an Apple Store if you somehow forgot your passcode, and people tried to mock me for saying that. "How can you forget your passcode?" Stuff like that.

Guess Apple agrees with me that it was stupid.
Make a foolproof system, and the world invents better fools. Spending $3,500+ on a device doesn't improve the user's ability to remember a 4- or 6-digit number.
 
Make a foolproof system, and the world invents better fools. Spending $3,500+ on a device doesn't improve the user's ability to remember a 4- or 6-digit number.
But it wasn't just about remembering. Suppose you THOUGHT you had created a certain passcode, but you entered the wrong number twice?

The point is, making someone physically travel to an Apple Store to reset it was just plain dumb. Now Apple have fixed that issue.
 
But it wasn't just about remembering. Suppose you THOUGHT you had created a certain passcode, but you entered the wrong number twice?
Just continue entering the wrong number, what’s the problem? ;)

The point is, making someone physically travel to an Apple Store to reset it was just plain dumb. Now Apple have fixed that issue.
The thing is, you can reset the AVP using the $299 developer band. This is probably why the issue never came up during development.
 
  • Like
Reactions: AsarTheGod
But it wasn't just about remembering. Suppose you THOUGHT you had created a certain passcode, but you entered the wrong number twice?

The point is, making someone physically travel to an Apple Store to reset it was just plain dumb. Now Apple have fixed that issue.

Two things can be true at once. It was dumb for Apple not to have it and forgetting a short pin is also dumb.
 
If I previously downloaded the update as part of the Beta, how do I update to the release candidate?
 
I’ve always been confused as to how people can lose passwords. The reality is that you’re not expected to memorize all your passwords. I’ve always had a book into which I have passwords, serial numbers, etc. Yes, I know, someone can steal it. Sure, people can break into your home and steal anything. With this, they would have to know I have that, figure out what it looks like and then try to find it. That would be about as hard as figuring out my passwords to begin with, which would be difficult. I can pretty much guarantee that someone breaking into your home does not have a password book in mind when they go looking for small high value items to carry out.
 
Two things can be true at once. It was dumb for Apple not to have it and forgetting a short pin is also dumb.
Don't forget the power of dumb things at scale. If 1% of people can't remember their 6-digit number or even misplace where they wrote it down, and 300,000 people (a guess) have an AVP, that's 3000 people who are stuck and making Apple Store appointments. This software fix was a good idea.
 
Last edited:
I’ve always been confused as to how people can lose passwords. The reality is that you’re not expected to memorize all your passwords. I’ve always had a book into which I have passwords, serial numbers, etc. Yes, I know, someone can steal it. Sure, people can break into your home and steal anything. With this, they would have to know I have that, figure out what it looks like and then try to find it. That would be about as hard as figuring out my passwords to begin with, which would be difficult. I can pretty much guarantee that someone breaking into your home does not have a password book in mind when they go looking for small high value items to carry out.
What do you do when you need a password, serial number, bank account number, or any one of many other similar items when you're not at home? I can't imagine life without a password manager, which in my case stores hundreds of pieces of information.
 
The thing is, you can reset the AVP using the $299 developer band. This is probably why the issue never came up during development.
This reminds me of an issue we ran into at Microsoft when I was the Office product lead for PSS Charlotte back in 1999. We had a small percentage of users who simply couldn't install Office 2000 from the CDs -- the error code they'd get was 2351 or 2355. In some rare cases, this error would then lead to Windows becoming corrupt (very bad!). The weird thing was, this error NEVER came up during the Beta for Office 2000. We tried all kinds of troubleshooting -- sometimes it worked, sometimes it didn't.

Anyway, long story short, the problem was ultimately determined to be caused by a problem in one of the duplication lines, where they made the CDs. (The manager of the duplication process asked me to collect CDs from customers, which I did, and then forward them to him for analysis. That's how they discovered the source of the problem.) It never came up during the Beta because people didn't install from CDs, or they used burned CDs that worked OK -- and it only affected a small percentage of users because only a small percentage of users received Office 2000 CDs that came from that ONE line. Once they figured that out, they fixed the issue in the line and the 2351/2355 error went away for good.

Point being, when you're testing something, you need to test using the actual stuff that a customer would have. All of the testers using optional $299 developer bands is a mistake on Apple's part.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.