Rivian software is (still) an embarrassment and needs to get better fast before R2

[rogersmj]

I've had my Rivian for less than 2 weeks, and I already almost can't take it anymore because of the software issues.

Disclaimer/context: I'm a big Rivian fan and have been rooting for them for years. I want them to succeed. I'm also a software architect, recovering developer, and CTO...I am fully aware of how hard it is to build and deliver complex software (not for embedded systems in a vehicle specifically, but I have some similar experience) for your current customers while also building for the future.

I just had to step back and take off the rose-colored glasses we sometimes have as fans of Rivian, because after experiencing the below I don't think I can look a normal person (non-early-adopter type) in the eye and recommend a Rivian.

All of the below issues have persisted after multiple resets of both vehicle and phone, and deletion/reinstallation of the Rivian iOS app.

1. About 70% of the time, the vehicle will not proximity unlock via phone key unless I pull out my phone (iPhone 17) and open the Rivian app. Yes, all the background permissions/Bluetooth settings etc are enabled. Insane that simply unlocking the car is still a problem in 2025. "UWB is supposed to make this better" -- yeah that would be great, if I could actually get the setup prompt. I can't. Besides, Tesla's been doing reliable unlocking via Bluetooth for years.
2. Apple Music stops after every 2-3 songs. It just stops playing until I tap Play again. Sometimes it just refuses to play that song and I have to keep skipping until one will start. Today, I got in the car and it just outright refused to start anything from Apple Music. Frustrating/annoying.
3. FM radio hasn't worked properly a single time. Oh it plays...but the UI is completely broken; we can't control it. It shows the radio as "off" when it's really on, or it stays locked on a single station regardless of what other buttons you push to change it, or sometimes it will change the station but the UI still shows that it's on a different station. Ridiculous.
4. Kneel when Parked only works about half of the time.
5. I can't get it to prefer my profile over my wife's when we both approach the car at the same time.
6. When I do select my profile, half the time it doesn't return my seat to my position. So then I have to re-setup my seat position.
7. Gear Guard setup just...won't. I have what is supposedly a proven compatible storage device, but when it tells me to plug it in, I do, and then nothing happens. No error message, no feedback, no additional information. The setup screen just closes.

There are yet more serious bugs that I (thankfully) have not experienced, like the slow level 2 charging or -- worse -- the wildly inaccurate arrival SoC estimates people have been reporting with the most recent update (2025.46.0). But those bugs are still indirectly affecting me even though I haven't experienced them, because we're leaving on a roadtrip soon, and I'm worried that these bugs might hit me — I'm afraid I won't be able to trust the arrival SoC, for example. Not a relaxing way to start a trip.

And that's the crux of it -- trust. I don't trust that the software in this $100k vehicle is going to work at any given moment, even for basic stuff like unlocking the car. Conversely, in three years, I haven't had any of the above issues in our Tesla, except for one time it wouldn't unlock until I opened the app on my phone. One. Single. Time. Everything else has been absolutely flawless in that vehicle -- audio, driver profile selection, the dashcam system, charging management, all of it. Based on that contrasting experience, I probably won't use my day one R2 reservation to replace our Model Y, and we'll be keeping the Model Y primarily because it's just reliable, and the Rivian isn't.

"It'll get better in the next update" or "it's come so far!" isn't acceptable after five years when we're talking about basic functionality that has been working fine in cars for decades — proximity unlock and FM radio, for example. "It's buggy because it's better tech and still new," again, isn't acceptable after this much time and for how expensive this vehicle is.

I know it's hard. I know it's new. Not an excuse anymore.

As a Rivian investor, I'm honestly more worried about next year now that I own a Rivian. If the mass market R2 experiences these types and volume of bugs, the Rivian brand will be tarnished and the R2 launch will be compromised. (Ironically, studies have shown that people who buy mid-market cars tend to have even less patience for reliability issues than people who buy $100k+ cars, due to lifestyle factors and a few other things.)

I don't post this to sh!t on Rivian, quite the opposite...I'm still rooting for them. But being honest about where things stand is important. They probably know all this, I'm surely not revealing anything that's new to anyone, but just as a reality check of where the overall current customer experience stands (for some people)...it's not great.

Let's hope for a better 2026 with software!

Sponsored

 

[nyckkr]

Despite the annoyances listed, the R1 is in a class of its own - high ground clearance, fun to drive and a large vehicle to accommodate people and stuff. Tesla is not comparable (in the same way a Toyota or Honda or even a BMW/Mercedes sedan is not comparable to a Defender and Rover).

Until the Rovers/Defenders go electric, Rivian has the electric version of that market...

Of course we want the annoyances to go away, but those won't hold me back from buying another Rivian. The bigger problem maybe the complete random shutdown of Gen 2 vehicles despite changing the 12V battery - it may effect a small proportion of the vehicles, but given the safety and related impacts of a shutdown, that's likely to have a far bigger impact on buyers.

 

[SwaziCAR]

I don't doubt that you have these concerns and that your vehicle doesn't behave the way you'd like it to in these seven areas.

I can honestly say, however, that I have none of these seven concerns, in many cases because I don't use the "features" (Gear Guard, Apple Music, FM radio, kneel when park, proximity lock). I bought the vehicle to drive, and none of these things affects how it drives (for me).

With respect to trusting arrival SoC estimates, my experience is that the vehicle's estimates are conservative, and experience driving the vehicle goes a long way toward understanding (and building trust).

But, as with any consumer product, if it doesn't work for you, by all means get rid of it. For me, whether--or for how long--I keep it will be based on the apparent reliability of things that actually make the car drive.

 

[SteveInBend]

I've had my Rivian for less than 2 weeks, and I already almost can't take it anymore because of the software issues.

Disclaimer/context: I'm a big Rivian fan and have been rooting for them for years. I want them to succeed. I'm also a software architect, recovering developer, and CTO...I am fully aware of how hard it is to build and deliver complex software (not for embedded systems in a vehicle specifically, but I have some similar experience) for your current customers while also building for the future.

I just had to step back and take off the rose-colored glasses we sometimes have as fans of Rivian, because after experiencing the below I don't think I can look a normal person (non-early-adopter type) in the eye and recommend a Rivian.

All of the below issues have persisted after multiple resets of both vehicle and phone, and deletion/reinstallation of the Rivian iOS app.

1. About 70% of the time, the vehicle will not proximity unlock via phone key unless I pull out my phone (iPhone 17) and open the Rivian app. Yes, all the background permissions/Bluetooth settings etc are enabled. Insane that simply unlocking the car is still a problem in 2025. "UWB is supposed to make this better" -- yeah that would be great, if I could actually get the setup prompt. I can't. Besides, Tesla's been doing reliable unlocking via Bluetooth for years.
2. Apple Music stops after every 2-3 songs. It just stops playing until I tap Play again. Sometimes it just refuses to play that song and I have to keep skipping until one will start. Today, I got in the car and it just outright refused to start anything from Apple Music. Frustrating/annoying.
3. FM radio hasn't worked properly a single time. Oh it plays...but the UI is completely broken; we can't control it. It shows the radio as "off" when it's really on, or it stays locked on a single station regardless of what other buttons you push to change it, or sometimes it will change the station but the UI still shows that it's on a different station. Ridiculous.
4. Kneel when Parked only works about half of the time.
5. I can't get it to prefer my profile over my wife's when we both approach the car at the same time.
6. When I do select my profile, half the time it doesn't return my seat to my position. So then I have to re-setup my seat position.
7. Gear Guard setup just...won't. I have what is supposedly a proven compatible storage device, but when it tells me to plug it in, I do, and then nothing happens. No error message, no feedback, no additional information. The setup screen just closes.

Just my own personal experience here but:

1. Have not had to take my phone (Pixel 7 Pro, OnePlus before that) out of my pocket to unlock the truckfor at least a couple of years.
2. NA
3. Tell me more about these radio "buttons" you're pushing.
4. Patience, young Padawan. It usually takes time to start and complete kneel mode.
5. Someone needs to be preferred. Why not your wife? Maybe it's related to your phone needing to be taken out of your pocket, though.
6. When my wife's profile is selected and I get in the driver's seat, it always adjusts to my profile when I select it.
7. Never had any formatting issues with my M.2 SSD.

 

[lefkonj]

Sorry for your challenges but this isn't the common theme for owners. I owned a Gen1 for over 2 years and have had a Gen2 for 10 months. 90% of the time the software is great and does as it should. Proximity locking/unlocking, Spotify, Nav, Charging, Gear Guard, Kneel the lot all good.

 

[windblowlc]

@rogersmj , for a sw architect and a cto, you should have known that the issues you’re having are NOT sw issues. Get it checked out before you come here and post. I’m saying this because I have owned multiple Rivians for more than 3 1/2 years and have not experienced anything like what you’re describing. Yes, issues will surface but they usually go away after a soft/hard restart. If they don’t, put in a ticket and let sc diagnose.

One more thing, you’ve lost me with the following statement-

“ There are yet more serious bugs that I (thankfully) have not experienced, like the slow level 2 charging or -- worse -- the wildly inaccurate arrival SoC estimates people have been reporting with the most recent update (2025.46.0). But those bugs are still indirectly affecting me even though I haven't experienced them, because we're leaving on a roadtrip soon, and I'm worried that these bugs might hit me — I'm afraid I won't be able to trust the arrival SoC, for example. Not a relaxing way to start a trip.”

You can’t complain about something that hasn’t happened to you.

 

[Dark-Fx]

You know what the real embarrassment is? Melodramatic posts over minor issues masquerading as serious issues.

If only the rest of my life was so easy.

Rivian is all-hands-on-deck for R2, so they're likely only trying to quash the important bugs now. Entirely possible while doing this that they introduce new ones for their existing vehicles. They are trying to keep the User experience as hardware/platform agnostic as they can. I'm sure this is a big part of why they are suffering so many strange bugs.

I did have an issue with my vehicle not unlocking without pulling my phone out earlier. Seems like there's something causing the proximity system to crash out, because it didn't auto-lock after that either.

My SoC prediction at destination was within 5% on this last trip, so not sure what that "bug" is.

 

[jrmbadger]

Gear Guard setup just...won't. I have what is supposedly a proven compatible storage device, but when it tells me to plug it in, I do, and then nothing happens. No error message, no feedback, no additional information. The setup screen just closes.

I had the same issue with my used Gen 1. Turns out the USB connections weren't seated correctly in the console so I was getting charging but not data. Open a service ticket and they will fix it.

 

[Tarkus]

So sorry to here of the multiple issue & at 2 weeks old, Rivian should be taking this unit back and replacing it with another. Tarkus (My 2023 R1S) is 29 months old & with 103k miles, she has had none of your issues.

 

[jrmbadger]

About 70% of the time, the vehicle will not proximity unlock via phone key unless I pull out my phone (iPhone 17) and open the Rivian app. Yes, all the background permissions/Bluetooth settings etc are enabled. Insane that simply unlocking the car is still a problem in 2025. "UWB is supposed to make this better" -- yeah that would be great, if I could actually get the setup prompt. I can't. Besides, Tesla's been doing reliable unlocking via Bluetooth for years.

I cant really comment too much on UWB, other than you should make sure you updated BOTH the truck software AND the Rivian apple iphone app? Make sure the iphone app is updated otherwise it won't have you setup the UWB keys. I used to think Apple updated the iphone app automatically, but I've found several apps out of date for some reason.

I will also say that a quick internet search regarding PAAK shows a lot of complaints across brands. You mention Tesla, but I've also seen complaints on Tesla Motor Club forums about Tesla's PAAK as well. I personally have never had a problem with the Rivian or the Tesla but the PAAK experience seems highly dependent on phone, phone placement, specific car, and maybe just luck?

Finally, while I understand your need to vent about your frustrations, you should know that Rivian does NOT monitor these forums so you may get better results by providing your feedback directly to rivian here: contact us I would also add that you also might wanna open a service ticket for these items. Based upon the reactions from others, this doesn't seem normal for a Gen 2.

 

[Biturbowned]

Not minimizing your issues, but I only have the wrong memory seat/steering wheel position (right profile selected, but other profile settings) and only occasionally. The others I haven’t had in almost 3 years.

 

[higrob]

Seems like this could be yet another troll job or perhaps there could be some operator error as you learn your new vehicle.
I have 2 Gen 2 R1s's and any time I have experienced any issues that you list they were always due to my initial lack of reading the owners manual.
If you read it, you would know such things as if you open the door too quickly before the vehicle has a chance to kneel it will stop kneeling.
Such drama... posts like this are getting really old and way too frequent on this forum.

 

[VSG]

I've had my Rivian for less than 2 weeks, and I already almost can't take it anymore because of the software issues.

LOL.

And I've had my Rivian more than 3 years, and haven't had one "software issue" that couldn't be fixed by a reboot. And very few of those, at that. Did you ever consider that the issues you list are due to your misunderstanding, wrong expectations, or even just problems with your specific vehicle, rather than a general indictment of all Rivians ever made?

Did you try a soft/hard reset? As a tech guy, isn't that the first thing you lean in school?

I'm not going to google things for you, but I know from reading this forum that most if not all of the issues you are reporting are not typical. And the ones that are seem to mostly stem from failure to read the manual. Take Kneel Mode for instance. You are aware that kneeling will stop if you open a door, right? Is that what is happening with you? Since you didn't explicitly mention that your doors remain closed the whole time, I think it's highly likely that you just didn't know this fact, and when kneeling stops you jump straight into blaming it on a software bug. Exercise for the student: List three reasons why it's a good idea for the vehicle to stop moving while you are entering/exiting the vehicle.

Likewise, if it chooses your wife when you both approach, that's consistent with your phone not being detected well. Again points to maybe your phone and to the fundamentals of microwave radio transmission (highly dependent upon antenna orientation, absorbed by your body so blocked when it's in your back pocket, dependent upon approach angle to the vehicle, etc.). Bluetooth was not designed for distance measurement, and it's bad at distance measurement. UWB on the other hand was specifically designed for distance measurement. So figure out how to set up your digital key.

Moving your seat doesn't work when your profile is selected? Did you calibrate the seat position? Please make an effort to learn about your new vehicle by reading the manual and the forums before you go straight to blaming Rivian. It seems your first instinct is to blame Rivian rather than to assume it's your own lack of knowledge about a new piece of tech.

For the SSD, you say you're a tech guy, so if you tried to plug that SSD into a computer and it wasn't recognized what would be your first thought(s)? Would you jump straight to concluding Apple software sucks? Or would you first test your SSD, test your cable, test your USB port, etc.? If all those work, it's likely your vehicle's USB port didn't get connected properly at assembly. A small number of people have reported this problem. Simple fix.

The only issue I can't speak to is the Apple Music thing. But I know there is lots of discussion on this forum about the Apple Music app, so perhaps you can read those threads? But you have a choice of either beating your head against the wall or trying to find something that works for you. I personally stream all my music from my own server, or from various services through my Alexa account, and that works well. I don't pay for services like Apple Music which charge me for playing music I already own.

There are yet more serious bugs that I (thankfully) have not experienced, like the slow level 2 charging or -- worse -- the wildly inaccurate arrival SoC estimates people have been reporting with the most recent update (2025.46.0). But those bugs are still indirectly affecting me even though I haven't experienced them, because we're leaving on a roadtrip soon, and I'm worried that these bugs might hit me — I'm afraid I won't be able to trust the arrival SoC, for example. Not a relaxing way to start a trip.

So you're afraid of issues you're not having?

Are these even real issues? There was a temporary L2 charging issue that hit a small number of vehicles in the previous update, that is fixed in the current update. So what? There is NO "wildly inaccurate arrival SoC" problem. I saw one complaint, with no details to corroborate it and no way to check other than my own vehicle, where I do not have that problem. Rivian arrival SoC numbers have been extremely accurate in my experience driving almost 40k miles now. I have tracked the predicted vs actual SoC over several very long trips (>4k miles) and I have complete confidence in this number.

This is a you problem - YOU'RE afraid. Irrationally afraid. Don't blame that on Rivian. You have trust issues. I do not, because of my experience taking my Rivian everywhere. This is something that you will have to overcome on your own.

 

[rogersmj]

A troll post, are you serious? More apologists here than I was expecting. You think the doors not unlocking are operator error? Or the radio displaying that it’s on one station but actually playing another is operator error? Or not setting my seat position when I select my profile?

I spent an hour on the phone with Rivian trying to get the UWB key to activate. That’s when we did all the resetting/reinstalling. App and vehicle are both up to date, obviously. No dice. They’re stumped too.

I think some of you are missing the real point, which is that if the R2 has these issues, it’s going to be a real problem with a mass market rollout, both in terms of brand perception and service load.

 

[rogersmj]

Did you try a soft/hard reset? As a tech guy, isn't that the first thing you lean in school?

Did you read the part in bold? Multiple resets, while troubleshooting on my own and with Rivian.

Wow guys. Didn’t think everyone here would get so defensive.

Sponsored