User being prompted with - ."..using an unsupported version of the SAP Concur mobile app"

[JDKing]

I have a user who is perpetually getting the message "Update Your App". "You are using an unsupported version of the SAP Concur mobile app." The version you are using will be decommissioned, preventing use of the app."  "Update Now".  They tap on "Update now" but nothing happens.

They are using iPadOS 26..1 and the version of the Concur app is V10.26.2.251.0171610,  based on my research both are the current versions.  I've cleared the cache, uninstalled the app, reinstalled the app, (via the instructions below...), hard reset the iPad multiple times but can't get the message to go away. 

Anyone else have or had and resolved this problem?

To clear the cache, uninstall, and download the mobile app again, please follow the steps below:
1. Open the SAP Concur mobile application,
2. Tap Done (iOS) or X (Android) in the upper left corner, (if there is no “Done” then click on the “X” in the upper left)
3. Double tap with two fingers on the SAP Concur Logo (in the center of the screen) to enter the settings menu,
4. Go to System > Clear Cache,
5. Delete the SAP Concur app from the iPad (By using the “long tap” method like you did prior, then “Remove App”
6. Restart the iPad,
7. After the restart, reinstall the SAP Concur app.

I've run through 

[KevinD · Accepted solution]

@JDKing this is a known issue and our R&D team is working on the fix. I don't have a date, as one wasn't mentioned. 

[JDKing]

Thanks so much for this information.  Is there a way I can be notified when a fix is released?

[USWsdymerski]

One of my users is having this issue on iPhone - he just emailed me about it a couple minutes ago. I am not sure from this post what the solution is other then "this is a known issue and our R&D team is working on the fix."

I told the user to try clearing the cache and uninstalling and reinstalling the app. Don't know if that was successful yet

[JDKing]

Hopefully that will be successful for you, if so please let me know.  It was not successful for my user.  He was not sure when the issue occurred, possibly after upgrading to  iPadOS 26. Right now it appears that the only option for me is to wait for a fix.