Redirection not working in IOS

[pranav2021]

Hi ,

I am developing application to fetch activity summary of a user using Fitbit APIs. The android version is working fine but its not working for IOS app. After user's authentication is done its just showing a blank page . 

[Gordon-C]

Hi @pranav2021 

When the user's authentication is complete, the user is redirected back to a specific location in your application that is defined by the redirect URL.   If the location doesn't exist, then it's likely you'll receive a blank page.   Have you checked the redirect URL to confirm its a valid location in your application?

Gordon

[pranav2021]

Hi GordonFitbit, 

Yes, the redirect url is correct. It's working find for android app, but doesn't work fir ios platform. After authentication where u select all scope and allow, it's not directing back to mentioned page. Instead it's just getting strucked. 

[Gordon-C]

Hi @pranav2021 

Would you please PM the URL that's generated after consent and that's displaying the blank page?

Gordon

[pranav2021]

Hi @Gordon-C,

Please find the generated url below

Redirect URL : https%3A%2F%2Fgssl-dev.outsystemsenterprise.com%2FGHL_UI%2FAuthenticated

Fitbit URL : https://www.fitbit.com/oauth2/authorize?response_type=code&client_id=23B53N&redirect_uri=https%3A%2F%2Fgssl-dev.outsystemsenterprise.com%2FGHL_UI%2FAuthenticated&scope=activity%20heartrate%20location%20nutrition%20profile%20settings%20sleep%20social%20weight&expires_in=604800

[Gordon-C]

Hi @pranav2021 ... I tested your authorize URL and I do not receive a blank page.   I'm taken to a page that tells me to get started.   Would you please try clearing your browser cache to see if that helps?   If not, have the user revoke consent to your application and try consenting again.

Gordon

[Gordon-C]

Hi @pranav2021 

Actually, I believe I am seeing the behavior you a reporting.   I do see we are correctly sending the user to your redirect URL which displays a white page.   After waiting a few moments, I'm taken to your "Get Started" page.   The delay is actually observed by your application receiving the authorization code and taking the user your Getting Started page.   This appears to be much slower using Safari than Chrome.   I can observe similar behavior with Safari on MacOS.   

Gordon

[pranav2021]

Hi @Gordon-C ,

For me, it's not getting delayed. When I call the URL from the app on iPhone it just shows me a blank screen and nothing is happening after that. I have checked it on IPhoneX and 12.

I can't debug as the page is not controlled by my app, it's on the Fitbit site. I am not sure of the cause.

Pranav

[pranav2021]

Hi @GordonFitbit,

I just found something, [I am getting disableThirdPartyLogin=True]

https://www.fitbit.com/login/transferpage?disableThirdPartyLogin=true&redirect=%2Foauth2%2Fauthorize...

I checked for this in the forum and google. This generally occurs if I m trying to log in using Google or Facebook on the login page but here I am login in with Fitbit profile credentials.

Also, the same logic is working for my android app but not for the iPhone app.

Any idea on what is causing this issue. I didn't get much help online as well.

[Gordon-C]

Hi @pranav2021 

Are you able to record a video of what is happening on your device?   I've tested your authorization on my iOS device and I do not see the problem you're observing.

Thanks!

Gordon