New IOS Mobile App 2.0

[Bobby]

Anyone here having mobile key issues, post iOS upgrade? I have a 2025 GT that has been flawless up until the new app update, and now it frequently won’t open without quite a delay and a few door handle pushes, and also frequently asks me for my PIN (something it hasn’t done since the day I picked it up in September), once inside the car.

I had this issue my first two days -- when the App was crashing for me. Since then it has been flawless. I was asked twice to enter my PIN because "no key was present." The no key present message started coming up on the left screen once while I was in the middle of a drive. The solution was to restart my phone.

I am not entirely certain that this is all Lucid! Ever since updating to iOS 18.2, my phone has been a crashing, bug-ridden nightmare. Even the phone app itself has been crashing repeatedly!! Go Apple!! So, yes, we complain about Lucid's occasional flubs with software...what's Apple's damn excuse?!?

“No key present” has absolutely nothing to do with the app. The car is looking for a Bluetooth signal, which it momentarily thinks it lost. Just wait for the message to go away. No need to enter a PIN. It’s a bug.

My phone/app has literally never crashed. I’d recommend a full reset and iOS reinstall.

 

[thecodingart]

“No key present” has absolutely nothing to do with the app. The car is looking for a Bluetooth signal, which it momentarily thinks it lost. Just wait for the message to go away. No need to enter a PIN. It’s a bug.

My phone/app has literally never crashed. I’d recommend a full reset and iOS reinstall.

Well, no. This absolutely has to do with the app as the app is responsible for running the bluetooth manager and handshaking with the mobile key…

That is why you’ll see this message if you force kill the app.

 

[Bishop555]

Like others have already reported my app is now crashing constantly, worked great till this morning when i have it plugged in (the car) for charging, unsure if this matters

 

[joec]

Well, no. This absolutely has to do with the app as the app is responsible for running the bluetooth manager and handshaking with the mobile key…

That is why you’ll see this message if you force kill the app.

I get this message all the time, and I never force quit the app.

I do carry the fob and my mobile key is active, though. My theory has been there is some conflict over the handshake with the phone's mobile key and the fob. Both want to authorize, and neither is getting through.

I never get asked to put in my PIN, though. So it resolves itself somehow.

 

[LRSIII]

You can swipe and remove that mobile key question.

You can, but on my iPhone, once I turn the phone off and then on again, and then re-open the Lucid app, the mobile key question comes back. Removing the mobile key question doesn't seem to stick.

 

[SaaSManKS]

I just noticed today that when you’re driving, the app shows your moving AND the speed of the car which I thought was kinda cool

 

[ColonelBadger]

Had the app “crash” for the first time today. Had to restart the phone. Doesn’t look like a crash actually. Looks like the app is taking too long to start and iOS is killing it.

 

[thecodingart]

I get this message all the time, and I never force quit the app.

I do carry the fob and my mobile key is active, though. My theory has been there is some conflict over the handshake with the phone's mobile key and the fob. Both want to authorize, and neither is getting through.

I never get asked to put in my PIN, though. So it resolves itself somehow.

Force killing is just one way to bring the message up. Anything that basically kills the core bluetooth manager’s connection (example being the app crashing in the background) can cause this issue. The app, phone and car all have roles here. I can’t recall if the Air uses iBeacon or not, but there could be a precision calibration for the BLE accuracy that might not be calibrated well for certain devices..

 

[thecodingart]

You can, but on my iPhone, once I turn the phone off and then on again, and then re-open the Lucid app, the mobile key question comes back. Removing the mobile key question doesn't seem to stick.

I’d be very surprised if they weren’t storing the key in keychain.

It’s honestly a bit of a pet peeve when people say to uninstall and reinstall an application for a situation like this. On iOS, it’s rarely a resolve for the issue and would indicate a big problem in the app. The only and I mean only thing that deleting the App would do is delete on disk data that’s potentially putting it into a corrupt state. It will not delete persisted data inside of the keychain. On android situations like this are more common to try to clear out app specific data - mostly because of the way things work with storage.

Unsure how they go about syncing removing the key with a profile/vehicle though.

As a sidenote, while driving right now, I am seeing the app crash consistently in the background presenting me a no key detected message. Hopefully the Lucid engineers are getting those logs.

There might be something going on when Bluetooth wakes up the app in the background.

Another note is Apple just revised all of the Bluetooth interfaces fairly recently. If the issue is being seen on iOS, it would not surprise me if there were bugs around this. Unfortunately, I haven’t had much hands-on experience with the new APIs at this point.

 

[thecodingart]

After noticing the crashes I’m also seeing a spike and battery usage. The Lucid app is up to 8% which is pretty significant. It’s possible that it’s constantly trying to launch itself us re-launching things like Bluetooth and network snacks draining battery.

No key detected is probably appearing once every few minutes, which would make sense if the application is consistently trying to launch itself in the background after crashing.

Sometimes attempting to re-launch the app after a force kill causes it to crash again. When that ends up happening, there’s definitely a delayed launch screen. It seems the splash screen originally hangs on the Lucid logo, but then turns into a black screen without any splash logo and crashes.

I’m gonna see if I can check the console logs when I get home and see if I can find them

 

[thecodingart]

In case engineers are lurking,

iPhone 16 Pro Max
18.2

App v2.0.0

Follow up repro crashes happened just on the splash screen hang. I am driving in my car, reproducing the crashes with only the mobile key on deck.

 

[RM-S8]

Weird, i managed to simulate iPhone's app on my Android. Apple works perfectly (to make a phone call...)

 

[joec]

In case engineers are lurking,

iPhone 16 Pro Max
18.2

App v2.0.0

Follow up repro crashes happened just on the splash screen hang. I am driving in my car, reproducing the crashes with only the mobile key on deck.

Interesting. For me, the old app was sapping battery in the background excessively. And then whatever Apple changed in 18.1 stopped it from happening. The new app doesn't even show up on my list of battery usage at times, the drain is so low. This is on 18.2 and now 18.3 beta. Mostly it's under 1%. The highest I've seen it on a heavy usage day is 2%.

 

[thecodingart]

Interesting. For me, the old app was sapping battery in the background excessively. And then whatever Apple changed in 18.1 stopped it from happening. The new app doesn't even show up on my list of battery usage at times, the drain is so low. This is on 18.2 and now 18.3 beta. Mostly it's under 1%. The highest I've seen it on a heavy usage day is 2%.

My battery usage with the new app was perfectly fine until the background crashes started in vehicle.

I imagine relaunching is killing battery.

 

[borski]

My battery usage with the new app was perfectly fine until the background crashes started in vehicle.

I imagine relaunching is killing battery.

This is my guess too.

 

[thecodingart]

This is my guess too.

Rebooted my phone, crashes stopped. Today battery usage is down from 8-5% for the last 24 hours.

This issue is definitely the root cause of some major battery drain spikes.

 

[fadooly]

Between now and then the app will stop working

And I have to log out of my profile and log in and the app will work again

Has anyone face this issue with the new update

I get the below error message

 

[HC_79]

Between now and then the app will stop working

And I have to log out of my profile and log in and the app will work again

Has anyone face this issue with the new update

I get the below error message

Nope. The app is working fine for me.

 

[idiot900]

I too am newly seeing crashes on app start. Seems quite similar to what @thecodingart describes. After rebooting my iPhone, app starts successfully.

 

[TakeDuo]

2.0.1 in the App Store