apps.crashlytics.com - Unable to install crashlytics build

[leibovic]

URL: https://apps.crashlytics.com/register/sdQixtzMpdKvTYaR87KrehxW/download?utm_medium=email&utm_source=new_release
Browser / Version: Firefox Mobile 53.0
Operating System: Android 6.0.1
Problem type: Mobile site is not usable

Steps to Reproduce

1. Navigate to: https://apps.crashlytics.com/register/sdQixtzMpdKvTYaR87KrehxW/download?utm_medium=email&utm_source=new_release
2. …

Expected Behavior: able to install crashlytics build

Actual Behavior: looks like fabric chooses not to support fennec

From webcompat.com with ❤️

[adamopenweb]

Thanks for the report @leibovic. It looks like the website is doing server side user agent detection.

Testing on the command line with a Firefox Android user agent:

http -b GET "https://apps.crashlytics.com/register/sdQixtzMpdKvTYaR87KrehxW/download?utm_medium=email&utm_source=new_release" User-Agent:"Mozilla/5.0 (Android 6.0.1; Mobile; rv:53.0) Gecko/53.0 Firefox/53.0"

Shortened for readability:

<div class='note fade-in-when-ready'>
Open the invitation email on your device to begin registering for beta testing
</div>

Using a Chrome user agent:

http -b GET "https://apps.crashlytics.com/register/sdQixtzMpdKvTYaR87KrehxW/download?utm_medium=email&utm_source=new_release" User-Agent:"Mozilla/5.0 (Linux; Android 5.1.1; Nexus 4 Build/LMY48T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.89 Mobile Safari/537.36"

We get:

{
    "redirect_to": "/register/sdQixtzMpdKvTYaR87KrehxW/rsvp"
}

We should reach out to the site and ask if they will update their user agent detection to consider Firefox for Android.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent#Mobile_Tablet_or_Desktop

*edited

[adamopenweb]

Maybe @adamvduke or @MichaelDoyle can help us find a contact for this @crashlytics issue.

[MichaelDoyle]

Hello. :) Will bring this to the attention of the team. Stay tuned.

[adamopenweb]

Thanks! :)

[mikebonnell]

I'm a different Mike from the Fabric team :)

Right now, it's not on our immediate road map to add support for using Firefox Mobile with Beta. I have noted @leibovic down as wanting to see this added in. If the team pulls in the work to support Firefox Mobile, I'll update this thread.

[adamopenweb]

@mikebonnell: Thanks for taking the time to explain, I really appreciate it. :)

From what I understand, this is just a download page? If the website is accessed on Android, the user should be able to download the APK. It doesn't seem like there's anything to support, just the user agent detection used is allowing some browsers but not others (for example Opera works).

Thanks again. :)

[softvision-oana-arbuzov]

The issue is still reproducible on my side.

Tested with:
Browser / Version: Firefox Nightly 68.0a1 (2019-08-18), Fenix 1.2.0 (Build #12181645) 📦: 6.0.2 🦎: 69.0-20190729080047
Operating System: LG G5 (Android 8.0.0) - 1440 x 2560 pixels (~554 ppi pixel density), Samsung Galaxy S7 Edge (Android 8.0.0) - Resolution 1440 x 2560 pixels (~534 ppi pixel density)

[amyhoaustin]

I have the same issue on iPad. I fixed it by switching back to mobile site after switching to desktop version. https://www.igeeksblog.com/how-to-go-back-to-mobile-site-after-requesting-desktop-version-on-iphone-ipad/
The issue is solved.

[softvision-oana-arbuzov]

For me the issue still occurs even if I switch to desktop layout and back to mobile.

Tested with:
Browser / Version: Firefox Nightly 68.0a1 (2019-08-28), Fenix 1.3.1 (Build #12341950) 📦: 8.0.0, 78354bc12 🦎: 69.0-20190812090043
Operating System: LG G5 (Android 8.0.0) - 1440 x 2560 pixels (~554 ppi pixel density), Samsung Galaxy S7 Edge (Android 8.0.0) - Resolution 1440 x 2560 pixels (~534 ppi pixel density)

[ngdinhkhoa120691]

I have the same issue on iPad. I fixed it by switching back to mobile site after switching to desktop version. https://www.igeeksblog.com/how-to-go-back-to-mobile-site-after-requesting-desktop-version-on-iphone-ipad/
The issue is solved.

I love you.

[softvision-oana-arbuzov]

@ngdinhkhoa120691 that is a workaround, but glad it works that way for now.

This should work the same way it works on Chrome when accessing the provided URL.
So we keep this open for further investigation.

[haithngn]

I have solved this problem by deploying the App via FireBase after I tried many ways.