DevSecOps
Well-Known Member
- First Name
- Todd
- Joined
- Sep 22, 2021
- Threads
- 69
- Messages
- 4,740
- Reaction score
- 11,500
- Location
- Sacramento, CA
- Vehicles
- '21 Audi SQ5 / '23 Rivian R1T / '23 M3P
- Occupation
- CISO
- Thread starter
- #1
NOTE 11/28/21: This version is no longer published and available. It has been replaced by 3.35.2 in the play store. This thread is being used for many topics so in order to get to relevant information please see the notes below.
It would appear that the FP 3.35.0 app breaks PaaK completely on Android 12, at least for some if not many people, by invalidating the security key used to authenticate/communicate with the car.
I am stranded at work because the backup password screen on the car won't appear either. So I'll be taking an uber home and back (50 miles) just to get a key. Pretty pissed off. So don't let this happen to you. Do not update!
Edit: Reviews are starting to hit the play store where other people are stranded with the same issue
Edit #2: I've revised the title because some people haven't had issue, while others have. I think the best course of action for anyone who uses PaaK without a FOB would be to ensure you have a FOB with you when updating the FP app. This still doesn't explain why the passcode wouldn't work.
Edit #3: See my follow up post here. https://www.macheforum.com/site/thr...-0-on-android-if-using-paak.11695/post-289050
Edit #4: Official response from FordPass Android Lead: https://www.macheforum.com/site/thr...if-using-paak-without-a-fob.11695/post-289727
Edit #5: The revised version of FP was released to address this issue. See here: https://www.macheforum.com/site/threads/fordpass-3-35-2-is-out-for-android.11769/
TLDR: READ THE BELOW IMPORTANT MESSAGE:
If you are on FP Android version 3.34.0 DO NOT UPDATE TO 3.35.0. Wait until you see 3.35.2 available in the play store, which has been pushed for deployment.
If you updated to 3.35.0 and HAVE issues you have 2 options, reset PaaK and it will work again or wait for 3.35.2 and then reset PaaK and it will work again. See the below if you reset PaaK with 3.35.0
If you updated to 3.35.0 and it works fine OR if you reset PaaK WHILE ON 3.35.0, do not update to 3.35.2 or it WILL break PaaK. Turn off auto updates for the FP app to prevent this from happening.
It would appear that the FP 3.35.0 app breaks PaaK completely on Android 12, at least for some if not many people, by invalidating the security key used to authenticate/communicate with the car.
I am stranded at work because the backup password screen on the car won't appear either. So I'll be taking an uber home and back (50 miles) just to get a key. Pretty pissed off. So don't let this happen to you. Do not update!
Edit: Reviews are starting to hit the play store where other people are stranded with the same issue
Edit #2: I've revised the title because some people haven't had issue, while others have. I think the best course of action for anyone who uses PaaK without a FOB would be to ensure you have a FOB with you when updating the FP app. This still doesn't explain why the passcode wouldn't work.
Edit #3: See my follow up post here. https://www.macheforum.com/site/thr...-0-on-android-if-using-paak.11695/post-289050
Edit #4: Official response from FordPass Android Lead: https://www.macheforum.com/site/thr...if-using-paak-without-a-fob.11695/post-289727
Edit #5: The revised version of FP was released to address this issue. See here: https://www.macheforum.com/site/threads/fordpass-3-35-2-is-out-for-android.11769/
TLDR: READ THE BELOW IMPORTANT MESSAGE:
If you are on FP Android version 3.34.0 DO NOT UPDATE TO 3.35.0. Wait until you see 3.35.2 available in the play store, which has been pushed for deployment.
If you updated to 3.35.0 and HAVE issues you have 2 options, reset PaaK and it will work again or wait for 3.35.2 and then reset PaaK and it will work again. See the below if you reset PaaK with 3.35.0
If you updated to 3.35.0 and it works fine OR if you reset PaaK WHILE ON 3.35.0, do not update to 3.35.2 or it WILL break PaaK. Turn off auto updates for the FP app to prevent this from happening.
Sponsored
Last edited: