@jonalmeida is setting Focus as default browser, and without any beta or nightly release, he is seeing it unset.
@jonalmeida any other STRs than that?
Focus stays as default.
Focus is unset.
@jonalmeida is there any way some other app on your phone is unsetting Focus? Is something else becuase default app? Did you do any OS upgrades?
I'll try to re-run my regular usage and see if I can find out if another app is causing this.
Did you do any OS upgrades?
None.
I'll update this ticket when I have better STR.
We definitely need STR, if we can identify any. My browser default has been steady. Is this a dev build, nightly, beta, or production? I wonder if switching between nightly and beta is causing it somehow.
@colintheshots We were talking about this on Slack. I'm using Nightly, so we believe that might be the problem. It hasn't happened in a while (~1 week) so I haven't be able to see if there was something I did to trigger it.
@jonalmeida We're most likely going to be doing another release this week. Lets coordinate you checking before / after the release to see if that is the cause.
unable to repro either
I haven't seen this happen any more, so I'm not sure what changed, but I'm happy have this closed.
OK let's close for now, do keep an eye out if it happens again, thanks @jonalmeida
@Sdaswani I found an STR!
Interestingly, this isn't a Focus issue but maybe a custom tabs/regular browser issue that we may not be able to fix?
Your default browser should stay set as to what you originally placed it as.
The default browser is now unset to no default browser.
Android version: Android 9 (Pixel 2)
Focus version: (it shouldn't matter) 8.0.1 (Build #323241231 :lizard: 64.0.20181112164519)
With this in mind, I wonder if the nightly or nightly -> beta updates are registering as new browser installs and that's what is unsetting the default browser. 馃
Thanks @jonalmeida ! Does step 2 include _updates_, or only fresh installs? If only the latter it's a smaller problem than if it's the former!
I'm not sure yet. I can only test this during another update. From an in-channel conversation, this is expected behaviour on Android when installing a new browser app though.
Ah, I _guess_ that makes sense, i.e., when the user installs a new browser, that shows intention to try it out. But it's still sort of crapola. Is there any documentation on this behavior?