8

(This may be specific to the Galaxy, which is what I'm using)

When I click a link to an SE site in the Android app, it gives me an "open with" pop-up that has three options:

  • Internet
  • Chrome
  • Stack Exchange

I can then choose to open SE posts like this "Just once" or "Always."

The problem is that when I set the SE app to "always," and I click "open in browser,"

  • I choose Chrome in the pop-up
  • The Chrome app opens the link
  • I am then redirected back to the SE app (???)

This must be because it's trying to handle the "Always open in SE app" part. But the problem is that now the "Open in browser" option is pointless!

Could this be fixed somehow?

|improve this question
  • I see this on my end too, I can hotfix it by forcing the link to open up in Chrome rather than showing the pop-up dialog but that isn't a viable solution for everyone, I'll look into it thanks! – Kasra Rahjerdi Jan 16 '14 at 17:09
  • @HodofHod I'm doing something similar to that. When I use that directly it includes "Stack Exchange" in the list of items to choose from, which is odd. But even if I use that directly it still redirects back to the app on my device (Nexus 5 running 4.4) when I choose Chrome instead of Stack Exchange. – Kasra Rahjerdi Jan 29 '14 at 18:27
  • @Kasra, Right, I just realized. :D New solution: This issue is probably due to the fact that the app uses the shortened url (i.e., q/216419/168660) instead of the full one (/questions/216419/open-in-browser-does-nothing-when-android-app-is-set-as-default). Then, when Chrome gets a 301 redirect, it checks for a default app for the new URL, finds StackExchange, and opens it there. Maybe using the full link, thereby avoiding the 301, will solve the problem? – HodofHod Jan 29 '14 at 18:29
  • @HodofHod That is very likely the case. The switching of intent doesn't change until a page redirect in Chrome, so that would be triggering it. Sadly I don't know how to manually make that URL without doing bad hacks on the Android side. – Kasra Rahjerdi Jan 29 '14 at 18:30
  • @KasraRahjerdi, Why can't you use the API? /questions returns a link item, with the full URL. (I assume you're already using the API for other things) – HodofHod Jan 29 '14 at 18:35
  • @HodofHod Because this would hopefully be using the "share" link found on the websites, which is the URL + a the person's account id. – Kasra Rahjerdi Jan 29 '14 at 18:36
  • @KasraRahjerdi I thought that the id link was only necessary for the "Share" function. At least, that's all I requested it for. It used to use the full URL, so I know you can get that; is it not possible to use a different URL for "Share" and "Open in browser" functions? (Sorry if I'm being dense.) – HodofHod Jan 29 '14 at 18:40
  • @HodofHod Yeah it's possible to use the full URL for open in browser instead of the one with the tag for each... I'll look into seeing if that fixes this issue. – Kasra Rahjerdi Jan 29 '14 at 18:49
  • @Kasra, Have you been able to look into this at all? (I'm really sorry to be pushy :) ) – HodofHod Feb 20 '14 at 19:43
  • @HodofHod I have looked into it. I'm still experimenting with different methods when creating the Intent to hope that I can do it without hacks. – Kasra Rahjerdi Feb 21 '14 at 1:25
  • I remember this bug, but is it still happening? I got different behaviour (app crash!) on SE app v1.0.82 (beta)... – Meta Andrew T. Jan 22 '16 at 9:51
  • @KasraRahjerdi did you find a fix? – Bebs Sep 4 '17 at 5:23

You must log in to answer this question.

Browse other questions tagged .