1400375 - dcard.tw: 307 Redirect to Intent URI not working

Status: RESOLVED DUPLICATE of bug 1399504

(Firefox for Android Graveyard :: General, defect, P2)

Description

[Mike Taylor [:miketaylr]]

Originally reported here: https://github.com/webcompat/web-bugs/issues/9708

STR:

Load https://www.dcart.tw
Click the Google Play icon at the top

Expected:

Play store opens

Actual:

Nothing

09-07 15:35:09.967 10835-10924/? E/GeckoConsole: [JavaScript Error: "Handler function threw an exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIIOService.newChannelFromURI2]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: resource://gre/modules/NetUtil.jsm :: NetUtil_newChannel :: line 360" data: no] Stack: NetUtil_newChannel@resource://gre/modules/NetUtil.jsm:360:16 this.requireRawId@resource://devtools/shared/loader-plugin-raw.jsm:26:16 requireHook@resource://devtools/shared/Loader.jsm:78:18 require@resource://devtools/shared/base-loader.js:438:14 Require/require.context/<@resource://devtools/shared/base-loader.js:547:14 getProperties@resource://devtools/shared/base-loader.js -> resource://devtools/shared/l10n.js:66:46 getStr@resource://devtools/shared/base-loader.js -> resource://devtools/shared/l10n.js:90:22 parseSecurityInfo@resource://devtools/shared/base-loader.js -> resource://devtools/shared/webconsole/network-helper.js:629:29 NetworkResponseListener.prototype._getSecur

Comment 1

[Mike Taylor [:miketaylr]]

Clicking the button, we do a GET to https://dcardtw.app.link/QZG8tzVIKA
then we get a 307 with Location: intent://open?link_click_id=407684685888881272#Intent;scheme=dcard;package=com.sparkslab.dcardreader;S.browser_fallback_url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.sparkslab.dcardreader&referrer=link_click_id%3D407684685888881272;S.market_referrer=link_click_id%3D407684685888881272;end

Comment 2

[James Willcox (:snorp) ([e-mail]) (he/him)]

-> esawin

Comment 3

[Eugen Sawin [:esawin]]

I can not reproduce this on Fennec 55 or 57.
Clicking on the "Get it on Google Play" button redirects to play.google.com which has a "Open in Play Store" button which works as expected.

Comment 4

[Eugen Sawin [:esawin]]

Looks like it does reproduce on my phone (not on the tablet).

Comment 5

[Bogdan Surd, QA [:bsurd, NI]]

Device:
 - Nexus 5 (Android 6.0.1).

Hello, here is that regression-window:
Last known good build: 2017-08-28
First known bad build: 2017-08-29
Pushlog - 28 > 29 
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d10c97627b51a226e19d0fa801201897fe1932f6&tochange=1b4c59eef820b46eb0037aca68f83a15088db45f

Notes:
 In the build from 2017-08-29 if the user taps on the Google Play button he is taken to https://dcardtw.app.link/QZG8tzVIKA and nothing else happens.
 In the build from 2017-08-30 the issue happens as described in Comment 0.

Pushlog - 28 > 30
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=d10c97627b51a226e19d0fa801201897fe1932f6&tochange=ab2d700fda2b4934d24227216972dce9fac19b74

Comment 6

[Julien Cristau [:jcristau]]

new regression in 57, tracking.

Comment 7

[Eugen Sawin [:esawin]]

(In reply to Bogdan Surd, QA [:BogdanS] from comment #5)
> Device:
>  - Nexus 5 (Android 6.0.1).
> 
> Hello, here is that regression-window:
> Last known good build: 2017-08-28
> First known bad build: 2017-08-29
> Pushlog - 28 > 29 
> https://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=d10c97627b51a226e19d0fa801201897fe1932f6&tochange=1b4c
> 59eef820b46eb0037aca68f83a15088db45f
> 
> Notes:
>  In the build from 2017-08-29 if the user taps on the Google Play button he
> is taken to https://dcardtw.app.link/QZG8tzVIKA and nothing else happens.
>  In the build from 2017-08-30 the issue happens as described in Comment 0.
> 
> Pushlog - 28 > 30
> https://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=d10c97627b51a226e19d0fa801201897fe1932f6&tochange=ab2d
> 700fda2b4934d24227216972dce9fac19b74

The second regression window can be explained with the fix in bug 1389303, that's the expected behavior for the erroneous case.

The first regression window seems wrong, I don't see a good build in that range.
My attempt at finding a regression window resulted in another wrong window.
I assume that there might be multiple regression-fix cycles which throw the bisection off.

Comment 8

[Jim Mathies [:jimm]]

Hey Eugen, can you confirm the regression range since you can repo? Also, what would you like to do with this bug for 57?

Comment 9

[Eugen Sawin [:esawin]]

This is no longer reproducing, it's a duplicate of bug 1399504.

Comment 10

[Ethan Tseng [:ethan]]

Mirror the status of bug 1399504.