On 19.04 do I keep waiting for bug fixes before updating?

[VSG]

How about 0 steps forward, 1 step backwards off the cliff?

There was an update less than a year ago that Rivian totally pooched the Security Certiicate which rendered vehicles hung during update, leaving them unstable and/or unusable, and the only way to fix it was to get Rivian support involved to manually push a reset AND in some cases, a physical service visit by Rivian. That's not better off than yesterday.

Except for the update Zoid mentioned that bricked a bunch of people's cars last year,

Oh please. Stop it with the fearmongering and misinformation. One mistake and you act like every OTA is potential malware. Sure it was the sort of thing that should not have happened, but you can bet that the same kind of mistake WON'T happen again because there are now checks in place and changes to the deployment process. The whole OTA system is a lot MORE robust as a result of this.

2023.42.0 was released on 13 November 2023. Problems with the release were detected by users immediately, and the rollout was stopped by Rivian within HOURS.

Note that a fix (2023.42.2) for those affected was rolled out within TWO DAYS (on 15 Nov 2023).

Fewer than 3% of owners had received the faulty release at that time. No one else was affected. The other 97% of us got the 2023.42.1 release which didn't have a problem and didn't need a fix.

And for that 3%, it absolutely did NOT "brick" the vehicles. Primarily the infotainment screen was affected and didn't display what is should, which prevented people from using the climate control and playing music and using the navigation among other things. The app continued to work, so for example you could still turn on the heater. The vehicles were still drive-able and usable, but perhaps some people were uncomfortable using their vehicle. But this didn't strand anybody. An inconvenience at most.

While it was not an ideal situation, the problem was extremely limited, not disabling, and fixed quickly. The error was not in the software, but the packaging of the software for distribution - the certificates used were for development and testing purposes only instead of the certificates meant for distribution. You can bet that process was examined and checks were put in place to prevent another a packaging error like that.


To the OP:
My rule for installing OTA updates (or cell phone OS updates, or laptop OS updates, etc.) is that you don't do it immediately if you have a critical need in the next day or so. This is just common sense. Like don't update your laptop the evening before your big presentation, because if the update has problems you're screwed. But don't put it off indefinitely either - you're just missing out on important fixes and new features and making the eventual upgrade harder.

The most recent OTA does have some bugs and quirks for *some* users. For example Apple Music doesn't work quite right. But you know what? Back in 2024.19 you didn't even *have* Apple Music. If you're reluctant to install an OTA right away, then don't. But holding off for four months now, like you've done, is a much worse strategy. The typical upgrade path is always going to be the best tested. If you skip three or four updates, then you're just opening yourself up to problems and edge cases, and making it harder for customer service to help you if you do run into problems.

Sponsored

 

[Donald Stanfield]

Oh please. Stop it with the fearmongering and misinformation. One mistake and you act like every OTA is potential malware. Sure it was the sort of thing that should not have happened, but you can bet that the same kind of mistake WON'T happen again because there are now checks in place and changes to the deployment process. The whole OTA system is a lot MORE robust as a result of this.

2023.42.0 was released on 13 November 2023. Problems with the release were detected by users immediately, and the rollout was stopped by Rivian within HOURS.

Note that a fix (2023.42.2) for those affected was rolled out within TWO DAYS (on 15 Nov 2023).

Fewer than 3% of owners had received the faulty release at that time. No one else was affected. The other 97% of us got the 2023.42.1 release which didn't have a problem and didn't need a fix.

And for that 3%, it absolutely did NOT "brick" the vehicles. Primarily the infotainment screen was affected and didn't display what is should, which prevented people from using the climate control and playing music and using the navigation among other things. The app continued to work, so for example you could still turn on the heater. The vehicles were still drive-able and usable, but perhaps some people were uncomfortable using their vehicle. But this didn't strand anybody. An inconvenience at most.

While it was not an ideal situation, the problem was extremely limited, not disabling, and fixed quickly. The error was not in the software, but the packaging of the software for distribution - the certificates used were for development and testing purposes only instead of the certificates meant for distribution. You can bet that process was examined and checks were put in place to prevent another a packaging error like that.


To the OP:
My rule for installing OTA updates (or cell phone OS updates, or laptop OS updates, etc.) is that you don't do it immediately if you have a critical need in the next day or so. This is just common sense. Like don't update your laptop the evening before your big presentation, because if the update has problems you're screwed. But don't put it off indefinitely either - you're just missing out on important fixes and new features and making the eventual upgrade harder.

The most recent OTA does have some bugs and quirks for *some* users. For example Apple Music doesn't work quite right. But you know what? Back in 2024.19 you didn't even *have* Apple Music. If you're reluctant to install an OTA right away, then don't. But holding off for four months now, like you've done, is a much worse strategy. The typical upgrade path is always going to be the best tested. If you skip three or four updates, then you're just opening yourself up to problems and edge cases, and making it harder for customer service to help you if you do run into problems.

We weren't fear-mongering, and nothing we said was untrue. You're barking up the wrong tree trying to accuse us of spreading fear or misinformation on Rivian here. We have quite a posting history here and have had our trucks for a substantial time. I took almost a year off from posting here and still have double your post history. You're barking up the wrong tree, especially when you reiterated what we said about updating at the end of your post.

Take a breath, settle down.

 

[s0ysauce]

Yeah for me it's just common sense not to be the first batch in OTA updates for a vehicle. For a phone, sure no problem. For a 7000lb vehicle, I'm ok waiting a few extra days to make sure there are no major issues.

 

[Zoidz]

Oh please. Stop it with the fearmongering and misinformation. One mistake and you act like every OTA is potential malware. Sure it was the sort of thing that should not have happened, but you can bet that the same kind of mistake WON'T happen again because there are now checks in place and changes to the deployment process. The whole OTA system is a lot MORE robust as a result of this.

2023.42.0 was released on 13 November 2023. Problems with the release were detected by users immediately, and the rollout was stopped by Rivian within HOURS.

Note that a fix (2023.42.2) for those affected was rolled out within TWO DAYS (on 15 Nov 2023).

Fewer than 3% of owners had received the faulty release at that time. No one else was affected. The other 97% of us got the 2023.42.1 release which didn't have a problem and didn't need a fix.

And for that 3%, it absolutely did NOT "brick" the vehicles. Primarily the infotainment screen was affected and didn't display what is should, which prevented people from using the climate control and playing music and using the navigation among other things. The app continued to work, so for example you could still turn on the heater. The vehicles were still drive-able and usable, but perhaps some people were uncomfortable using their vehicle. But this didn't strand anybody. An inconvenience at most.

While it was not an ideal situation, the problem was extremely limited, not disabling, and fixed quickly. The error was not in the software, but the packaging of the software for distribution - the certificates used were for development and testing purposes only instead of the certificates meant for distribution. You can bet that process was examined and checks were put in place to prevent another a packaging error like that.


To the OP:
My rule for installing OTA updates (or cell phone OS updates, or laptop OS updates, etc.) is that you don't do it immediately if you have a critical need in the next day or so. This is just common sense. Like don't update your laptop the evening before your big presentation, because if the update has problems you're screwed. But don't put it off indefinitely either - you're just missing out on important fixes and new features and making the eventual upgrade harder.

The most recent OTA does have some bugs and quirks for *some* users. For example Apple Music doesn't work quite right. But you know what? Back in 2024.19 you didn't even *have* Apple Music. If you're reluctant to install an OTA right away, then don't. But holding off for four months now, like you've done, is a much worse strategy. The typical upgrade path is always going to be the best tested. If you skip three or four updates, then you're just opening yourself up to problems and edge cases, and making it harder for customer service to help you if you do run into problems.

I'll just let others decide if it's fearmongering and misinformation, they can read excerpts of comments that were made here when this happen, including Rivian telling people to let the vehicle sit and not drive it. These are documented facts, not misinformation. Sorry if you think it is fearmongering, not intended that way, but it is intended to give validation to those who choose to wait a few days.

Claiming "this happened a year ago, it won't happen again" is sticking your head in the sand and being naive. How long has Windows 11 been out? The lastest Windows 11 KB5043145 patch dated Sept 26 is putting Windows 11 into boot loops and crashes. How about the Crowd Strike debacle?The stark reality is that it can and does happen and in my line of work I see failed updates that cause unintended serious issues 4 or 5 times a year. Perhaps the same kind of certificate mistake won't happen, are you CERTAIN that there are no other possible update failure modes?


"My update failed and truck wont boot. Just called service and got the “high call volume“ warning. Been on hold. If you have not updated yet, don’t! For those that got connected to service, what did they have you do? Can we fix ourselves?

Interesting enough the car does drive And the backup camera does come on in reverse. Just no ability to control anything.

Edit: just connected with a person. “It’s A known issue and our OTA team is working on it and should push out a new update.” No ETA"

"Same issue here. Just constant boot loop. Spoke with service and they mentioned deep sleep and wait for an overnight fix. New update push apparently. Very unfortunate!"

"Mine is in a reboot loop. Rivian support has been notified. They just said they are working on it.
it is what it is."

"Rivian support is asking people not to do any resets and not use the vehicle."

 

[ndmiller]

I know of no company with electronics or websites at this point that hasn't made mistake, been hacked and/or bricked some of their devices. It happens and how the company recovers is as important as how they communicate the mistake.

These days everyone whines for the next R1 update and they come after a couple weeks of testing and maybe a .1 or .2 update and more testing. Not what happened on that infamous Rivian update, as they were trying to get updates out as fast as possible based on consumer noise. Now they don't listen to the noise and just do their thing on their own schedule.

I had the update 3 days after it released knowing after 3 days and no noise, it was good to go for the most part.

Sponsored