Skip to main content

Hi,

the Strava authentication in my windows app CR4NKUP is not working anymore. The app was built in Unity and uses the Vuplex Webengine ( https://developer.vuplex.com/webview/overview ). When the user wants to connect his Strava account for uploading activities to Strava the InApp Webbrowser is opened with the Authentication url and according parameters and the user has to authorize. My app handles then the upload of the activities to Strava and takes care about token refresh, etc. Everything was working fine for more than one year. But since about two months the Authentication does not work anymore.

When the Strava page is opened in the InApp webbrowser and the user enters his credentials (email) the page shows an error instead of the next page to enter the password. The error is something like this (translation from German to English):

Unexpected Error. Please try again later.

If I use the url for authentication directly in the browser everything works fine.

Were there any changes on Strava side during the last months which causes this error?? There were no changes on my side or in the App, so why is this not working anymore? Is Strava blocking requests from Apps?

Upload from already connected users is still working fine btw.

This is really annoying for my users, because new users can’t connect their Strava accounts and don’t upload their activities.

Help is really appreciated!

Thanks,

Marco 

Maybe Strava sees InApp browsers as security risk because these could phish the Strava login and password. It’s possible that they changed their login procedures so that only white listed browsers are allowed. Just a guess, but an informed one because if I use an alternative browser (i.e. Arc) I get the same error.

Hey ​@Jan_Mantau, thanks for your answer. I have the same impression, that the browser is blocked by Strava, but it’s hard to tell without an official answer on this. Do you know if it’s possible to get an answer from a Strava developer about this, or any possibility wo whitelist the app?

In my opinion it was the best solution to implement the browser directly into the app so the user don’t need to change or login to another site for connection the account like in other apps and it did work great. Would be a lot of effort to setup another web based system outside the app and very unfriendly for the users. So let’s cross fingers that there is another solution!

Thanks and have a great day,

Marco

Same with me, in-app browser authentication stopped working

Never mind. It looks like it’s working now.

It also stopped working for my users

Terms & ConditionsCookie settings