iPhone Recognized/Connected but NOT as a Key After Update (Resolved: PSA not Complaint)

[Empirate]

Automatic Update last night for my iPhone 14 Pro Max (26.3.1), and when trying to leave work after a night of call, my 2026 R1S did not unlock on my approach. After opening the Rivian APP, it did unlock, but two things occurred:

1. I got a "no key" error and was instructed to put a key in the console to enable "start" (placing my phone there did not resolve the issue).
2. My phone repeatedly went to a grey screen with a number pad (which looked like the lock screen, except grey) and prompted me to enter my passcode to continue accessing the vehicle (I'm paraphrasing here, but it seemed to be related to my Rivian app and the vehicle's recognition). Entering my 6-digit code resolved the screen, but did not resolve the vehicle failing to recognize it as a "key".

This was a WTF moment as I was tired and stuck in my work's parking lot. Thankfully, I did have a physical card/key kept in the car that I located and used successfully.

Once home, I turned off my phone and restarted it. That seems to have resolved the issue.

Hope this is helpful to anyone who encounters the same situation.

- Franklin

Sponsored

 

[tate16t]

Sounds like your phone was the issue?

 

[UnsungZero_OldTimeAdMan]

Don't keep the backup keycard in the car. Keep it on you, in your wallet. Backups aren't any good if you can't get to them—i.e. if you're locked out of the car. Keeping a key in the car, if someone broke in they could just drive off.

 

[Empirate]

Yes, the phone was the issue.

Good advice about keeping the key in my wallet

 

[badger4149]

Automatic Update last night for my iPhone 14 Pro Max (26.3.1), and when trying to leave work after a night of call, my 2026 R1S did not unlock on my approach. After opening the Rivian APP, it did unlock, but two things occurred:

1. I got a "no key" error and was instructed to put a key in the console to enable "start" (placing my phone there did not resolve the issue).
2. My phone repeatedly went to a grey screen with a number pad (which looked like the lock screen, except grey) and prompted me to enter my passcode to continue accessing the vehicle (I'm paraphrasing here, but it seemed to be related to my Rivian app and the vehicle's recognition). Entering my 6-digit code resolved the screen, but did not resolve the vehicle failing to recognize it as a "key".

This was a WTF moment as I was tired and stuck in my work's parking lot. Thankfully, I did have a physical card/key kept in the car that I located and used successfully.

Once home, I turned off my phone and restarted it. That seems to have resolved the issue.

Hope this is helpful to anyone who encounters the same situation.

- Franklin

Since the last update I've been having a related issue. Proximity locking/unlocking is working, but when I get into the vehicle, about 30% of the time my phone is not recognized as a key. I have to remove it from my pocket and then it is recognized. I'm Samsung, Gen 2 R1S.

 

[Empirate]

Since the last update I've been having a related issue. Proximity locking/unlocking is working, but when I get into the vehicle, about 30% of the time my phone is not recognized as a key. I have to remove it from my pocket and then it is recognized. I'm Samsung, Gen 2 R1S.

Have you done a restart on your smartphone?

 

[badger4149]

Have you done a restart on your smartphone?

Thanks for the follow up. Yes, both phone and vehicle have been restarted.

Sponsored