App runs in a Browser and does not sign-in the app

[streetgrover]

When attempting to log in to the SAP Concur Mobile App, it forces a web-browser interface within the app for any username/password entering method. After signing in, using any sign-in method (username/password, SSO, etc.) it loads the web interface and does not allow the application to open. This is not usable at all and I am frustrated that I can't get the application to work outside of the browser sign-in window within the app. This is a huge hindrance to my workflow and I can no longer upload receipts, submit reports, or book work travel like I used to.

Please address this issue with an App update or help me find a workaround.

Thanks,

Screenshots of the issue are provided below:

[johnsol5 · Accepted solution]

This morning I was able to get in, I am on IOS 18 BETA, but my users were not, so I went and checked if Concur had an app update on my device and it did. So I updated to version 10.15.1 and now I too cannot get in to Concur via mobile app.

10/01/2024 - to update readers:  I have verified with multiple iPhone users with various phones and system versions, IOS all versions work up through Concur mobile app version 10.14.0.2409031209 Even IOS Beta 18.1 (22B5054e), but as soon as you update the Concur Mobile app to any version after that it does not work.

So far with my ticket in with Concur has stated the following (i.e. major change with NO communications to Admins that I can find). I have asked for documentation of this and we are looking at our SSO now too. Will come back and update if we fix on our side. 

Concur has incorporated a relaystate parameter in the authentication request. It is crucial to collaborate with your IT team to ensure that the relaystate query string parameter is permitted/enabled. They should be able to identify where relaystate is not being passed along and determine where it is being dropped.

Depending on the IdP configuration, certain customers may be set up to use the IdP-initiated endpoint (such as Ping), which may not be configured to accept relayState. As a result, a more extensive reconfiguration of their IdP is required.

Additionally, in the same scenario, clients have the option and are encouraged to transition to SAML2, which follows a proper SP-initiated SSO flow. The effort required to reconfigure the IdP and transition to SAML2 is comparable.

[KevinD]

@streetgrover what browser is your default browser on your mobile device and is your device provided by your company or a personal device?

[streetgrover]

Hey Kevin,

Unfortunately, this seems to be an iOS 18 bug as the browser that opens within the concur app is not tied to the default browser. I confirmed with another iPhone not running iOS 18 beta that as soon as credentials are entered, the browser interface WITHIN the app (which happens to be Safari) closes and the app interface is automatically loaded. I have not been able to get the app to load as it refuses to accept the login credentials and return to the app interface. It instead stays in a web browser-like interface.

[KevinD]

@streetgrover I cannot speak about our Development team's timeline for app updates, but at the time you attempted to sign in, iOS 18 hadn't been officially released, so my guess is our app hadn't been updated yet to be compatible with iOS 18. To me this is completely understandable as we are more likely to push an app update closer to the actual release of a new iOS and not when the beta of that iOS is launched for testing. 🙂

[ally_c]

I have just got a new company iPhone 13 running iOS18 and have this exact problem. Any news regarding a solution?

[streetgrover]

Hey @KevinD ,

Thank you for sharing your insight, however, now we are several days after the full release of iOS 18. It should be considered that the Developer Team should at least be testing on future iOS versions to ensure compatibility ahead of full launch. It is unacceptable that many users are now experiencing these issues despite the app now listing "full support for iOS 18" which it doesn't.

[KevinD]

@streetgrover I wish I could disagree with you. Someone from our mobile support team said that if your device is using MDM (mobile device management), then you should reach out to your IT department. MDM is if you have a company issued phone where your company controls what can be installed or if you have a personal device, but your company wants to control any apps that are related to doing business. For example, accessing Outlook for work email, SAP Concur for expense reporting.

If you are not using MDM, then we were told to have you create a .HAR file and submit a help ticket to SAP Concur. Your IT department should be able to help with creating the .HAR file.

[LolueM]

Is no one having this problem at Concur? I don't see how you guys are not able to replicate this same problem when everyone else here seems to have the exact same problem as soon as updating to iOS 18. Multiple users in my org has confirmed this problem as soon as they've upgraded their personal iOS devices.

[dougrader]

Concur Admins - you still have an issue and it needs to be fixed please.  Can your developers address this major issue?  I have contacted ny IT department at my company and they have reached out to you and were told that CONCUR has NO known issues??????  Excuse me???  All you have to do is read these many similar issues.  Why not address this?

[dougrader]

Concur Admins - you still have an issue and it needs to be fixed please.  Can your developers address this major issue?

[johnsol5 · Accepted solution]

This morning I was able to get in, I am on IOS 18 BETA, but my users were not, so I went and checked if Concur had an app update on my device and it did. So I updated to version 10.15.1 and now I too cannot get in to Concur via mobile app.

10/01/2024 - to update readers:  I have verified with multiple iPhone users with various phones and system versions, IOS all versions work up through Concur mobile app version 10.14.0.2409031209 Even IOS Beta 18.1 (22B5054e), but as soon as you update the Concur Mobile app to any version after that it does not work.

So far with my ticket in with Concur has stated the following (i.e. major change with NO communications to Admins that I can find). I have asked for documentation of this and we are looking at our SSO now too. Will come back and update if we fix on our side. 

Concur has incorporated a relaystate parameter in the authentication request. It is crucial to collaborate with your IT team to ensure that the relaystate query string parameter is permitted/enabled. They should be able to identify where relaystate is not being passed along and determine where it is being dropped.

Depending on the IdP configuration, certain customers may be set up to use the IdP-initiated endpoint (such as Ping), which may not be configured to accept relayState. As a result, a more extensive reconfiguration of their IdP is required.

Additionally, in the same scenario, clients have the option and are encouraged to transition to SAML2, which follows a proper SP-initiated SSO flow. The effort required to reconfigure the IdP and transition to SAML2 is comparable.

[tenders]

This issue continues several days after iOS18 was released. Occurs on both my iPhone and iPad. I’ve deleted the app and reinstalled several times, and rebooted the device several times.

[wuncarlitos]

The browser built into the app is what is popping up within the app, doesn't seem to be related in anyway to whatever browser you have installed, I noticed this started happening after getting iOS18.

I have been forced to use Concur on my computer as the desktop site is very inconvenient on the phone.

hopefullya fix is in the works 

[streetgrover]

I am running the iOS 18 beta and can confirm when I login to my account on another iPhone running iOS 17.x that this issue does not occur. This must be an iOS 18 bug that does not allow the app to sign in correctly. It prevents the browser window within the app to return the main interface of the app.

Seeing as iOS 18 is releasing next week, a fix needs to be provided soon!

[Andras]

Hi! @streetgrover . @ally_c , @tenders , @wuncarlitos  

I can see that issue has been fixed. Our R&D recommended to uninstall and reinstall the application.

Please let me know if it helps.

[streetgrover]

Hello @Andras,

Per your instructions, I removed (uninstalled) the app. Then, from the app store download the SAP Concur App. I went through the same login process as expected but it does NOT appear to have been fixed. Screenshots provided before are still relevant as they remain within a browser-like window within the app and never convert to the app interface. Any attempt to exit out of the browser in-app window brings me to the login screen. There is no exit button to enter the full app.

To provide more details, I am experiencing these issue the following:

• iPhone 15 Pro
• iOS 18.1 public beta 4 (22B5045g)
  • This occurs on 18.0 as well
• SAP Concur App 10.14.0

This has been an issue since iOS 18.0 and has not been fixed. Please advise that on the app store many other users are now reporting that the app is broken with iOS 18:

screenshot of recent app reviews for SAP Concur

[tenders]

Issue has not been fixed following (yet another) app delete and reinstall. iPhone 14 Plus, iOS 18.0 release copy.

[tenders]

Concur app was updated today to 10.15. No difference! Finding somebody at my company of 45,000 employees to change a backend setting is a joke. SAP should be pushing either a fix or instructions for what needs to be done from their end to their clients, not through users.

[Ev46f]

This has not been fixed. Unable to log in on iOS 18

[Ev46f]

In case it was still unclear, this is that it’s doing to basically everyone. 

Concur Sign in Loop Video 

[vperlutchi]

Hi @Andras ,

The issue is still there and in my company too is starting to affect more and more people that are updating to ios 18. I personally did try to uninstall, delete all the data and reinstall but the application is still not working. As I cannot attach a text file here, I'll show a screenshot of the log from my application as i tried to log-in experiencing the same behaviour that was already presented.

The issue is starting to get really problematic and i hope it will be solved soon.

Thank you.

Best regards.