Heads up with iOS 26 beta 3, breaks the app

JGard18

Active Member

Verified Owner
Joined
Sep 6, 2024
Messages
207
Reaction score
109
Location
Boston MA
Cars
24 Lucid Air Touring
Referral Code
BIN679WM
Apple released Dev beta 3 for iOS 26 today, and like a moran I installed it right away. Since then, the Lucid app does not work. It's completely unresponsive once it opens. I've rebooted, force closed, reinstalled, etc, nothing has gotten it to work. Just a heads up for the rest of you, leave it on Beta 2 for now if you want to continue using your app.
 
Don't use a developer beta on your personal phone, they're for developers to use on their development phones or emulators...
 
Apple released Dev beta 3 for iOS 26 today, and like a moran I installed it right away. Since then, the Lucid app does not work. It's completely unresponsive once it opens. I've rebooted, force closed, reinstalled, etc, nothing has gotten it to work. Just a heads up for the rest of you, leave it on Beta 2 for now if you want to continue using your app.
I noticed that also, but it still works as the key.
 
Apple released Dev beta 3 for iOS 26 today, and like a moran I installed it right away. Since then, the Lucid app does not work. It's completely unresponsive once it opens. I've rebooted, force closed, reinstalled, etc, nothing has gotten it to work. Just a heads up for the rest of you, leave it on Beta 2 for now if you want to continue using your app.
I have the same problem. I tried to uninstall and reinstall the app with fresh login and it freezes.
 
Don't use a developer beta on your personal phone, they're for developers to use on their development phones or emulators...
I would hope that any tech enthusiast that’s installing dev betas knows fully well the intention and risks they take. I’ve been installing dev betas for years on my devices. Still nice to know when things break. He wasn’t blaming lucid as it’s clearly not their fault, it was more of a heads up which was useful for me as I just ran into this issue.
 
I would hope that any tech enthusiast that’s installing dev betas knows fully well the intention and risks they take. I’ve been installing dev betas for years on my devices. Still nice to know when things break. He wasn’t blaming lucid as it’s clearly not their fault, it was more of a heads up which was useful for me as I just ran into this issue.
Understood and apologies for coming off harsh there. I’ve just seen a lot of posts around (not here) recently of people who think betas are like hot backstage passes to show off, complaining that things break. I mistook this for that. Carry on.
 
I'm in the same boat (and, yes, I fully realized the risks in using the developer beta releases). I will note that the Apple Watch app does still work even though the main app doesn't. My watch also has the latest developer beta.

Jeff
 
Glad to know I’m not the only one with this issue. Seems like only the app Home Screen is frozen; the widget remains connected to the car (shows when it’s charging and the accurate state of charge) and the mobile key still works

I reported it to Apple feedback. I’m sure it’ll get fixed in Beta 4
 
Glad to know I’m not the only one with this issue. Seems like only the app Home Screen is frozen; the widget remains connected to the car (shows when it’s charging and the accurate state of charge) and the mobile key still works

I reported it to Apple feedback. I’m sure it’ll get fixed in Beta 4
Yeah, this kind of thing happens every beta cycle. It’s always one app or another reacting poorly to a change or bug.

I don’t expect Lucid to address it directly unless it doesn’t go away by the next three or four betas. Ideally, a new OS would never break an existing app.

My guess is Apple will have this sorted soon. Though it’s not like they are looking at the Lucid app specifically. (Though Craig Federighi drives an Air, so who knows?)
 
You can also use the Home Assistant App on iOS for remote functionality until the issue is resolved.
 
Ideally, a new OS would never break an existing app.
I agree with you. But Apple routinely violates this idea. They care very little about backwards compatibility, force apps to support their newest features, and then make it so older devices cannot run the newest stuff.
 
I agree with you. But Apple routinely violates this idea. They care very little about backwards compatibility, force apps to support their newest features, and then make it so older devices cannot run the newest stuff.
Not really.

IOS 26 can run on devices as old as iPhone 11, which was released in 2019. Which means that phone will be capable of running “the newest stuff” for at least 7 years. I’d say that’s fairly remarkable by modern tech standards.

Apple goes pretty far out of its way to make their phones last longer than most people give them credit for.

My point about apps not breaking was simply to say when we all upgrade in September, the existing apps on our phone that are working now should continue to launch and run as if we were still on iOS 18. That’s the goal.

During betas, we often see apps (as with the Lucid app now) that run into trouble. But that’s almost always cleared up by the public release.

They do this because they know it’s likely several of the apps on our phones have been abandoned by their developers and won’t get updated. Or they at least won’t be updated in time. So some apps may look a little outdated or have a bump or two in behavior. But they should continue to run.
 
IOS 26 can run on devices as old as iPhone 11, which was released in 2019. Which means that phone will be capable of running “the newest stuff” for at least 7 years. I’d say that’s fairly remarkable by modern tech standards.
I shipped a game, "Hover!", on the Windows 95 CD-ROM. It was shipped prior to Direct Draw--using the WinG library. It ran on every CPU level supported by Win95 (386sx through Pentium).

Last I checked it still ran on Windows 10, and I have no doubt it still runs on Windows 11, 30 years after release.

I have an iPad Air2--circa 2015. During that time Apple forced all apps to upgrade to 64 bits. 32-bit apps were deprecated. iOS refused to run them. It impacted my ability to use the device for the purpose for which I bought it--controlling a Mackie digital mixer and related app-controlled output processors. And they completely stopped supporting new iOS versions on it years ago.

Both Apple and Google have a cavalier attitude about breaking compatibility. It takes a significant investment in time, money, and culture of software development to maintain compatibility across 30+ years of an operating system.
 
I shipped a game, "Hover!", on the Windows 95 CD-ROM. It was shipped prior to Direct Draw--using the WinG library. It ran on every CPU level supported by Win95 (386sx through Pentium).

Last I checked it still ran on Windows 10, and I have no doubt it still runs on Windows 11, 30 years after release.

I have an iPad Air2--circa 2015. During that time Apple forced all apps to upgrade to 64 bits. 32-bit apps were deprecated. iOS refused to run them. It impacted my ability to use the device for the purpose for which I bought it--controlling a Mackie digital mixer and related app-controlled output processors. And they completely stopped supporting new iOS versions on it years ago.

Both Apple and Google have a cavalier attitude about breaking compatibility. It takes a significant investment in time, money, and culture of software development to maintain compatibility across 30+ years of an operating system.
Have you tried using IE7 to browse the internet lately? And what’s a CD-ROM? That the thing AOL kept sending me in the mail? :P jk

I used to ship games on 3.5” floppies back in the day, but we don’t do that anymore either.

Played a Macromedia Flash game in a while?

Yes, Apple has a penchant for leaving the past in the past. If they never did, we’d rarely move forward.

Some things are just not going to be backward compatible. You can’t put gasoline in an EV, either.
 
I shipped a game, "Hover!", on the Windows 95 CD-ROM. It was shipped prior to Direct Draw--using the WinG library. It ran on every CPU level supported by Win95 (386sx through Pentium).

Last I checked it still ran on Windows 10, and I have no doubt it still runs on Windows 11, 30 years after release.

I have an iPad Air2--circa 2015. During that time Apple forced all apps to upgrade to 64 bits. 32-bit apps were deprecated. iOS refused to run them. It impacted my ability to use the device for the purpose for which I bought it--controlling a Mackie digital mixer and related app-controlled output processors. And they completely stopped supporting new iOS versions on it years ago.

Both Apple and Google have a cavalier attitude about breaking compatibility. It takes a significant investment in time, money, and culture of software development to maintain compatibility across 30+ years of an operating system.
No one forced you to do anything. You were welcome to continue using your iPad running your 32-bit OS and apps indefinitely. That iPad would most definitely still be working 30 years from now. Probably much longer than that.

You seem to want companies to guarantee every one of literally millions of available apps will run on any hardware they release despite you consistently upgrading your operating system to whatever latest version comes out for the rest of time. That’s a little unrealistic, no?
 
Last I checked it still ran on Windows 10, and I have no doubt it still runs on Windows 11, 30 years after release.
And this is the reason why every Windows executable to this day is wrapped in a 16-bit DOS executable which, when run in DOS, says "This program cannot be run in DOS mode!"
There is a reasonable amount of backwards compatibility, then there is a hoarder house, and then there is Windows...
 
Anyone tried these AC enhancements ? Can you please report back (especially watching YT Vids via Airplay 🤣)?

 
Back
Top