PSA: New iPhone/iOS 18.1, can no longer set up Rivian key

[ThirteenElectrics]

... this means the app. is pretty much useless. I was on the iOS 18.1 beta on my old phone; switching to the new phone (also on the iOS beta) I lost key access, which is expected, but, and am unable to re-create it. Rivian wants to set up the key using the old name of my phone (oddly), but the phone is never found on Bluetooth to complete the process. I've tried a half dozen times. The phone will join to the audio system no problem, just not as a key. Hopefully this will be fixed soon.

Sponsored

 

[Cycliste]

I didn’t have any problem setting up a new PAAK on an iPhone 16 Pro using the latest 18.1 beta.

 

[Kgomez777]

I have a 16pro max as well as IOS18 and had no issues with PAAK.

 

[Magicbus]

They call it Beta for a reason... bleeding edge.

 

[COdogman]

I had no trouble setting up a 16 Pro last week, but that was on iOS 18. I stopped doing the beta program when I picked up my Rivian last year just to be safe. I thought it was just daring Mr. Murphy to do something…

 

[Ohm Boy]

I had no trouble setting up a 16 Pro last week, but that was on iOS 18. I stopped doing the beta program when I picked up my Rivian last year just to be safe. I thought it was just daring Mr. Murphy to do something…

Love the “Mr. Murphy” reference!!

 

[josh0]

I also had no problem setting up PAAK on my new iPhone 16 Pro with iOS 18.1 beta. This would have been an earlier 18.1 beta release, when I first got my 16, so maybe something’s changed in a more recent release?

 

[Feetdry]

This latest update unpaired my Google 7 as a key phone. It will not pair and work as a key phone any longer. I haven't tried a reset on my R1T yet.

 

[Armeniandave]

Still on beta and still working for me also

 

[Mathme]

If you choose to run beta software, these are sometimes the inherent risks involved. Although I can participate in the beta program, I choose not to...especially now that I use PAAK.

 

[ThirteenElectrics]

I think the issue is migrating your phone to a new one while both are in 18.1. In that case Rivian sees two identical keys, and I don’t think it likes that. However, I did manage to delete the duplicate keys in the system, and after that the key worked. Hooray!

 

[iforbes]

Maybe stop using Beta software if you need it to work?

 

[Proxy]

Thank you for beta testing. It helps avoid problems for us non beta testers.

 

[mitchelmb]

... this means the app. is pretty much useless. I was on the iOS 18.1 beta on my old phone; switching to the new phone (also on the iOS beta) I lost key access, which is expected, but, and am unable to re-create it. Rivian wants to set up the key using the old name of my phone (oddly), but the phone is never found on Bluetooth to complete the process. I've tried a half dozen times. The phone will join to the audio system no problem, just not as a key. Hopefully this will be fixed soon.

I am in the same vote. When I got my the iPhone 16pro, I lost all ability to use my phone as a key. I worked with Rivian and went through soft and hard resets to no avail. We also deleted the key and deleted/reinstalled the rivian app. The phone seems to not see the bluetooth prompt to finish pairing as a key. The iPhone 16 pro is connected to audio and all the sensors via bluetooth. I should add that I am not running any beta iOS.

 

[SwampNut]

Rivian wants to set up the key using the old name of my phone (oddly), but the phone is never found on Bluetooth to complete the process.

Make sure you have wiped all traces of the phone out of the Rivian, and all traces of the Rivian from the phone. Note that there are multiple Rivian BT devices that the phone sees. Do all that, reboot both (master on the Rivian), then try again.

Sponsored