My Cupra app broken again

[DaveSmith]

Seems it is broken again. Refuses to start unless I perform an app update. When I select the update option it sends me to app store which prompty says that the app is not compatible with my device. Galaxy S10 plus Android 12. Checking the requirements it required android 10+. So why doesn't it run or allow the update?
I've sent an email to cupra support. I'll be miffed if I can't use it anymore as I've only just renewed my subscription.

 

[alanjs]

I've just had exactly the same problem. There was an update to the MyCupra app on 7 June that requires (I think) Android v13 or upwards for compatibility.
My phone has Android 11 so I'm stuffed as well as I haven't found any way round this problem. It seems to happen a lot with Android-based systems which don't let you upgrade the OS.

In my case, my wife gets a new phone and I get her old one which runs on Android 16.

 

[DaveSmith]

I've just had exactly the same problem. There was an update to the MyCupra app on 7 June that requires (I think) Android v13 or upwards for compatibility.
My phone has Android 11 so I'm stuffed as well as I haven't found any way round this problem. It seems to happen a lot with Android-based systems which don't let you upgrade the OS.

In my case, my wife gets a new phone and I get her old one which runs on Android 16.

Well that's odd as the app info says the requirements are Android 10+ and API 29+. I'm on Android 12 and API 35. So according to that it should work.
I've sent an email to the developers. However, given Cupra support history, I'm not holding out much hope.

 

[alanjs]

Well that's odd as the app info says the requirements are Android 10+ and API 29+. I'm on Android 12 and API 35. So according to that it should work.
I've sent an email to the developers. However, given Cupra support history, I'm not holding out much hope.

I got the info from this link. The last three updates - MyCupra v2.16, 2.17 and 2.18 (April, May and June) took a compatibility jump from Android 11 to 13.
I also opened a ticket with Cupra but I don't really expect an immediate reply.

 

[DaveSmith]

I got the info from this link. The last three updates - MyCupra v2.16, 2.17 and 2.18 (April, May and June) took a compatibility jump from Android 11 to 13.
I also opened a ticket with Cupra but I don't really expect an immediate reply.

Great. So my subscription is useless unless a buy a new phone. Thanks Cupra. Why can't I simply continue to use the older app? If you want me to upgrade, then give me a nag screen and a end of life support date. Don't just pull the rug from under my feet with zero warning.

 

[alanjs]

Great. So my subscription is useless unless a buy a new phone. Thanks Cupra. Why can't I simply continue to use the older app? If you want me to upgrade, then give me a nag screen and a end of life support date. Don't just pull the rug from under my feet with zero warning.

Agreed. It would have been nice to have had some warning. Fortunately I have an Android tablet that still runs the app.
However new models like the Raval have "Digital Keys" for access and starting. What happens if the app suddenly decides to stop working when you're away from home and you don't have an actual key with you? Too bad - go buy a new phone right now? Crazy!

 

[DaveSmith]

Got a reply. Kind of what I expected. Basically tough titties matey. Well it is the kick up the arse I needed to get a new phone as this is now 7 years old and no longer getting security updates.

 

[alanjs]

View attachment 54454
Got a reply. Kind of what I expected. Basically tough titties matey. Well it is the kick up the arse I needed to get a new phone as this is now 7 years old and no longer getting security updates.

I haven't had a response from Cupra yet but I expect it will be the same as yours.
Upgrading my wife's phone (so I could use her old one) was going to cost over £500 so I've opted for a cheaper £160 Samsung running Android 15 (with the ability to upgrade the OS) as I don't need any high-end features.
Oh well...

 

[DaveSmith]

I haven't had a response from Cupra yet but I expect it will be the same as yours.
Upgrading my wife's phone (so I could use her old one) was going to cost over £500 so I've opted for a cheaper £160 Samsung running Android 15 (with the ability to upgrade the OS) as I don't need any high-end features.
Oh well...

I don't see why we can't just continue to use the old version. Surely in most cases an update is optional? Ok if it is related to cyber security then they could legitimately insist that you update. I'm not going to waste my breath arguing with them as you know that this is what they are going to claim. It'd be like trying to argue with H&S, totally pointless as you can't win.

 

[alanjs]

I don't see why we can't just continue to use the old version. Surely in most cases an update is optional? Ok if it is related to cyber security then they could legitimately insist that you update. I'm not going to waste my breath arguing with them as you know that this is what they are going to claim. It'd be like trying to argue with H&S, totally pointless as you can't win.

With my previous knowledge of software development, I have to assume that some functionality in the app requires the use of an element of the Application Programming Interface (API) that is only available in the later versions of the OS. Developers are very reluctant to maintain backwards compatibility with older versions as it is expensive in terms of developer time. And it goes on and on. At some point they have to draw a line.
I had a response from them asking me to provide more detail and I have responded, more on the lines of "you need to give people more warning" and "what happens if you lose access when you are relying on a Digital Key" than on "why can't you fix this", because they ain't going to fix this.
At least this is a Heads Up that they might pay attention to.
Now waiting for new phone to be delivered. Bummer.

 

[DaveSmith]

With my previous knowledge of software development, I have to assume that some functionality in the app requires the use of an element of the Application Programming Interface (API) that is only available in the later versions of the OS. Developers are very reluctant to maintain backwards compatibility with older versions as it is expensive in terms of developer time. And it goes on and on. At some point they have to draw a line.
I had a response from them asking me to provide more detail and I have responded, more on the lines of "you need to give people more warning" and "what happens if you lose access when you are relying on a Digital Key" than on "why can't you fix this", because they ain't going to fix this.
At least this is a Heads Up that they might pay attention to.
Now waiting for new phone to be delivered. Bummer.

Yeah you're probably correct. I'm an engineer and we had exactly the same issue with windows apps we developed. Constantly trying to keep pace with Microsoft changing things was a bloody nightmare, and it continues to this day with the legacy systems we have out there. Some customers are still wanting support for 3.11 and XP as in their minds it was working fine and the upgrade is a costly and unnecessary exercise. Hence why the decision was made to stop all windows based in-house application solutions. We now use commercial HMI / Web based solutions, so the issue of Windows compatibility is someone else's problem.