Tapping Ad notification doesn't launch beta app
Tapping Ad notification doesn't launch beta app
Should launch Brave-Beta if app is not running in memory
Easy
Android-Core beta
cc: @gdregalo @samartnik
@srirambv Are you also seeing this behavior in the nightlies? I'm having trouble reproducing it, not sure if I'm missing a step...? When I exit the browser and tap on an ad, the browser relaunches with the ad (although there is a 2-3 second pause between tapping the ad and the browser launching).
Haven't checked it on nightly will run through it. Will check it on nightly and update here
@srirambv Sounds good, thank you!
@emerick I can reproduce this on Nightly CI build as well. Both with sample and actual ad notification as well
@srirambv OK, thanks for confirming - trying the nightly now, just waiting for an ad to show up...
@srirambv Finally got back to this and it's not happening for me with the latest nightly v1.6.21. If you can still repro, can you make a video showing how it happens from beginning to end? If not possible, maybe we can jump on a video call to do the same?
@emerick shared logs and video of issue reproducing on slack
@srirambv I tried with a locally built BraveMonoarm64.apk running on Android 10 and with the previous beta version (1.5.97). In both scenarios, clicking notifications when Brave wasn't running correctly launched Brave. I think there must be some other difference we're missing here. Is the behavior intermittent for you? Any other differences you can think of?
I use Beta as my daily driver on my main device and ads clicks work as expected for me. @srirambv do you see it on some particular device or you can replicate on all Android devices you have?
@SergeyZhukovsky I see the issue on my OnePlus 6T with Android 10. I've shared the recording of the issue with @emerick and the logs.
I don't seem to see any other difference apart from installing the apk. I haven't made any changes to notifications as well at device level
I can see this issue happen on current GPS build as well on my device
Could not reproduce the issue in Samsung Galaxy J3 version 5.1.1 running Android stable 1.5.100 and GPS version 1.5.6
I wasn't able to repro with a OnePlus 6T device, unfortunately. I tried with Android 9 (which it shipped with) and Android 10 (after installing the updates). I tried debug and release builds and regular ARM and Monoarm64 builds with no luck.
Spoke with @SergeyZhukovsky and we're going to move this out of the upcoming 3/17 release as it also happens in browser-android-tabs per https://bravesoftware.slack.com/archives/GUA24E92P/p1582872239001400 and https://github.com/brave/brave-browser/issues/7588#issuecomment-592390442.
I can't seem to reproduce this on my Samsung Galaxy S10+ using 1.5.109 CR: 80.0.3987.132 either. Went through the following:
1.5.109, tapped on the first notification and 1.5.109 oepened1.5.109 opened every single time@srirambv do you see it on some particular device or you can replicate on all Android devices you have?
@srirambv can you reproduce this on other devices? Or just on the OnePlus 6T device?