iOS 17 having issues with proximity unlock

[mkg3]

PAAK using iO S17.0.3 on iPhone 15 Pro works great.

Locks and unlocks sooner without having to take the phone out of my pocket.

Edit: Rivian app 2.3.0

Sponsored

 

[Beanejar]

PAAK using iO S17.0.3 on iPhone 15 Pro works great.

Locks and unlocks sooner without having to take the phone out of my pocket.

Edit: Rivian app 2.3.0

Yup - 2.3.0 and 17.0.3 seem to be the key <ahem> on the 15pro.

Startled me today when it actually unlocked when approaching from the rear about 10 feet away, yet. Phone was in a coat pocket. Worked again from the side later in the day.

Could hardly believe it. Hopefully keeps working. ? Wasn’t really enjoying waiting to unlock via the app watching the Gear Guard screen through the window…

 

[connoisseurr]

PAAK using iO S17.0.3 on iPhone 15 Pro works great.

Locks and unlocks sooner without having to take the phone out of my pocket.

Edit: Rivian app 2.3.0

Yup - 2.3.0 and 17.0.3 seem to be the key <ahem> on the 15pro.

Startled me today when it actually unlocked when approaching from the rear about 10 feet away, yet. Phone was in a coat pocket. Worked again from the side later in the day.

Could hardly believe it. Hopefully keeps working. ? Wasn’t really enjoying waiting to unlock via the app watching the Gear Guard screen through the window…

Are either of you saying you had issues before updating the Rivian app and/or iOS? If yes, were the issues worse on Rivian app <2.3.0 and iOS <17.0.3, and got better after updates?

 

[Beanejar]

Are either of you saying you had issues before updating the Rivian app and/or iOS? If yes, were the issues worse on Rivian app <2.3.0 and iOS <17.0.3, and got better after updates?

yes - much worse <2.3

15pro was much worse than the 14pro on IOS 17 and <2.3. Frequently, the 15pro would not unlock at all even if app open and standing next to a door. At least a much worse delay of 15-20 seconds instead of 1-2 seconds. Power cycled phone, quit app, soft restart of R1S, nothing made a difference. Until now.

 

[connoisseurr]

yes - much worse <2.3

15pro was much worse than the 14pro on IOS 17 and <2.3. Frequently, the 15pro would not unlock at all even if app open and standing next to a door. At least a much worse delay of 15-20 seconds instead of 1-2 seconds. Power cycled phone, quit app, soft restart of R1S, nothing made a difference. Until now.

Great feedback, thank you. I was experiencing similar issues. PaaK would not work until I took my phone out and woke it up. Then, 1-2 seconds later, the R1T would acknowledge that one of us is near.

Both the wife and I having issues with 15 Pro and 15 Pro Max. No issues prior, though. I couldn't chalk it up to Rivian app, iOS, or recent truck update. We went as far as deleting PaaK on both devices, deleting apps and reinstalling/setup. Will test the latest iOS updates.

 

[bd5400]

For you and most everybody else, yes. For me, never. Tesla service techs were able to reproduce the issue, but only with my (brand new) phone. I think there’s a config setting gone wrong, or I’m paired with to too many Bluetooth devices already. I’ve reset most settings to no avail. Maybe there’s a ghost in my neighborhood.

In the Tesla case it appeared that the early Model 3 antenna was weak, and if my phone was in my back pocket, my (obviously massive) body was enough to block the signal. Even in my front pocket it was iffy, though, depending on how I approached the car. Another wrinkle is that I walk faster than most people, so the car doesn’t have enough time to react.

I had similar experiences with a 2018 Model 3. Not always, but sometimes it would only unlock if you woke the screen.

 

[NashvilleR1S]

I was on 17.0.2 so maybe it's fixed with .3? Like I said, 14 pro and I've only had perfect experiences with PAAK so far. Hoping an update will fix it!

 

[connoisseurr]

Updated to iOS 17.0.3 and Rivian app 2.3.0. PaaK will only work as soon as I remove my phone from my pocket or bag; essentially once the iPhone screen turns on.

 

[mkg3]

Updated to iOS 17.0.3 and Rivian app 2.3.0. PaaK will only work as soon as I remove my phone from my pocket or bag; essentially once the iPhone screen turns on.

On my old iPhone (12Pro) it had this issue, It might work and it might not. If not, I had to wake the vehicle using the Rivian app before it would unlock.

With 15Pro, works every time. Maybe there is something in the HW implementation for RFID, or that the new phone just works better...

 

[connoisseurr]

On my old iPhone (12Pro) it had this issue, It might work and it might not. If not, I had to wake the vehicle using the Rivian app before it would unlock.

With 15Pro, works every time. Maybe there is something in the HW implementation for RFID, or that the new phone just works better...

Wife and I both got 15 Pros on launch day. Before that, we had 13 Pros. Zero issues then.

It’s either a Rivian app issue, iOS 17 issue, or iPhone 15 issue.

 

[dholt]

Anyone else still having issues? I just had to take the phone out, open the app, hit the button, wait… tried again a few minutes later and had to completely force quit the Rivian app to lock the car at home. iPhone 15 pro, iOS 17.0.3, Rivian app 2.3.0. iPhone 14 pro on 17.0.3 and 2.0.3 had zero problems.

 

[Pacblue22]

Mine is now way worse, but between iOS and Rivian updates its hard for me to pinpoint, but with current iOS version and current Rivian version I am on, 2023.34.0, worst it has been for me...

Hey! So I updated my iphone to iOS 17 two days ago, I've always had perfect experiences with proximity unlock via phone, but now I have to unlock my phone, sometimes even open the app before it unlocks. Anyone else have a similar experience?

 

[fr4c]

Same issue here, will often need to unlock phone and open Rivian app for proximity unlock to work.

 

[mkg3]

Wife and I both got 15 Pros on launch day. Before that, we had 13 Pros. Zero issues then.

It’s either a Rivian app issue, iOS 17 issue, or iPhone 15 issue.

Interesting.

The fact that some 15s work and some do not, implies that it's not the phone but is Rivian. If it was 15 issue, then it should be consistent with all 15s on iOS17.

Proximity sensor is located in Rivian. So its has to do with the range and when the vehicle is allowed to sense it. In other words, when the vehicle is asleep, it probably does not send any electricity to the sensor. It requires it to be waken; hence need to open the app.

So why has it worked for me? Maybe I need to go away longer and let the vehicle go into a sleep mode before coming back to the car. I have it unlocked in the garage so that's not an issue and I precondition the cabin temperature before going back to the vehicle to open in a parking lot so the vehicle is awake already.

Need to experiment with and without cabin temperature being set after parking...

 

[kozak79]

My wife iPhone 12 and mine iPhone 14 Pro both upgraded to latest iOS 17 and no issues with PAAK

Sponsored