.42.?

[tcole]

I had the .4242 update (second iteration) installed on my R1T. Today I took it in to service to have a set of 20” AT wheels/tires I acquired put on and the software update to reflect the change in tire size. Interestingly they had to roll back my software to .38 to get the tire change done. In talking to the service tech, .42 has been pulled completely and I won’t get updated back to .42. I’ll just get whatever the next update is.

I’m good with it, but found it interesting that .42 was pulled completely.

So sounds like they might be doing what @240vPlug suggested above. Just moving into December release.

Sponsored

 

[CaptRat]

With lots of traveling the last couple of months, I wasn't able to install 38 until this last weekend. I was wondering why I wasn't getting a notice for any version of 42. If they pulled all the iterations, I guess that explains it.

Every OTA update I've installed since I got the vehicle (May, '23,) has had a glitch that required either an infotainment reset, a total reset, re-pairing the phone or resetting app logins. So far I haven't found anything not working with 38.....yet. I'm not complaining, though, as the fix for each of the glitches was pretty easy and fast and nothing required a SC visit or CS help. OTOH, don't get me started on the cheap plastic pins on the manual tonneau.

 

[Jblaze121]

My only complaints on 38 is slow loading of some screens like it’s not caching anymore after first load. Also PAAK, on an iPhone 13 and it’s been slow as hell again to unlock Vs previously unlocking 5 steps before I got to the vehicle.

 

[mikehmb]

1. A confusing, disorganized situation often attributed to or marked by human error.
2. A convoluted issue that is contested by many parties.
3. A rodeo event in which competitors attempt to lasso a goat, usually for younger participants

You are obviously a "city slicker".

TIL Goat Rope and Goat Rodeo are similar, but not equal.

 

[electruck]

I just got another push for 42.1. I had been ignoring the update last week while traveling until I noticed that it had disappeared entirely at the end of last week. Just got the notification that it is available again.

 

[tcole]

I just got another push for 42.1. I had been ignoring the update last week while traveling until I noticed that it had disappeared entirely at the end of last week. Just got the notification that it is available again.

Yep, I just got the notification too. Risking it and doing the update.

 

[electruck]

Yep, I just got the notification too. Risking it and doing the update.

I haven't had any major issues but installing wiped my audio eq settings and home location for proximity locking (although proximity for garage door popup was not impacted).

 

[moosetags]

We got .42.1 again after it disappeared for several days. Still don't trust it. We will wait.

Brian

 

[VSG]

We got .42.1 again after it disappeared for several days. Still don't trust it. We will wait.

People always jump to the worst conclusions.
I installed 2023.42.1 TWO WEEKS ago, and it has been working just fine. Anecdotal claims from a small number of users happen for EVERY update - don't just jump to the conclusion that the update is flawed because of a few anecdotes. Aw, I had to re-login to TuneIn because of the bad certificates. BFD.

When there is a REAL flawed update like 2023.42.0, then EVERYONE has a problem and you get 68 page threads about it. And to be clear, Rivian fixed that flawed update within TWO DAYS before 97% of the users even got a chance to install the broken update.

So what do you think is more likely, that Rivian pulled 2023.42.1 over the Thanksgiving weekend because it is fatally flawed, OR, perhaps, just perhaps, given that it was the busiest travel weekend of the year, they just didn't want to be flooded with calls to customer service (which always happens for EVERY update), and they wanted to prevent anyone from installing the update right before a big roadtrip (which is ALWAYS a bad idea)?

I personally think it's that they didn't want people shooting themselves in the foot and that they wanted to be able to give their staff some time off like everyone else, instead of putting them on overtime over the holidays. I think it was a really smart and considerate move to pause the rollout of the update over the holiday and resume it when they were back to normal staffing levels.

Sponsored