Add notification for users using an old SBrowser version

[mario]

Background

Samsung released Samsung Internet (aka SBrowser) 4.0 for Android Lollipop which enables Lollipop users to use content blockers. (So far this has only been possible for Marshmallow users.)

Thus we're aiming for updating ABP for Samsung Browser in the Google Play Store to remove the restriction for Lollipop which enables Lollipop users to download and use ABP for Samsung Browser as well.
However if users using Lollipop haven't updated SBrowser to version 4.0 already and go ahead and download ABP for Samsung Browser, ABP won't work. Thus we need to detect the SBrowser version on ABP start-up and notify the user to update SBrowser if needed.

What to change

Implement a standard Android notification as shown in this workflow under Step 3 and reduce the minimum Android API version to 21 (Android 5).

The notification is shown on every ABP startup if all of the following requirements are met:

• The user runs any Android version above Android 5 (Lollipop)
• The user runs any SBrowser version older than 4.0

The notification is not closable.

Ressources

• The link for "Get update" on Step 3: ​https://play.google.com/store/apps/details?id=com.sec.android.app.sbrowser

Notification Text
Notification headline:
Update your browser

Notification body:
Before you can use Adblock Plus, you must update to Samsung Internet Browser 4.0.

After installing the update for Samsung Internet Browser, relaunch Adblock Plus to finish.

Notification button:
Get update

[vickyyu]

The Samsung Browser 4.0 is only going to be available for Android 5.0 and above, so the notification requirement "The user runs any Android version older than Marshmallow" should be revised to "The users runs any Android 5.0 and above" to exclude users with Android versions older than 5.0.

[scheer]

Additionally the image shown for 'in this workflow under Step 3' is an iOS pop-up style guide (ABP_for_iOS_ALERT_v2.0.pdf). Was the wrong screenshot uploaded?

[vickyyu]

Replying to scheer:

Additionally the image shown for 'in this workflow under Step 3' is an iOS pop-up style guide (ABP_for_iOS_ALERT_v2.0.pdf). Was the wrong screenshot uploaded?

Thanks! I've added the right screenshot (ABP_for_SamsungBrowser_First-run_V3.pdf) and updated the link in the description. I hope @rene has got the right one.

[scheer]

The notification flow runs as described in ABP_for_SamsungBrowser_First-run_V3.pdf, however, after step 8, Samsung Browser does not open and the user is not able to enable the content blocking options.

However, if the user manually enters into Samsung Browser and unlocks the content blocker by entering 'about:contentblock' in the address bar, then selecting Settings > advanced > blocking, they are then able to enable the content blocker.

Galaxy S5 - Android 5.0
Galaxy S4 - Android 5.0.1
Galaxy S6 - Android 6.0.1

[abpbot]

A commit referencing this issue has landed:
​https://hg.adblockplus.org/adblockplussbrowser/rev/0235d72d590a

[scheer]

ABP Sbrowser adblockplussbrowser-1.0.2-20160426113120-release
Sbrowser 4.0
Samsung Galaxy S5
Android 5.0

• The user is now able to update to the latest version of Sbrowser (4.0) after launching ABP for the first time and selecting the option 'Get Update' on Android 5.0.

• The first time message of the required browser update links the user correctly to the Sbrowser version within the Google Play Store.

• Once the user has upgraded and launched the updated Sbrowser at least once, then the user is able to launch ABP again and proceed with the normal setup of ABP in Sbrowser.

I must note here, that in ABP_for_SamsungBrowser_First-run_V3.pdf, steps 4 and 5 are wrong. When the user is taken to the store page, the options that are displayed are 'Upgrade' in white on the left and 'Open' in Green on the right. Normally this is not an issue, but this could lead to confusion for the user as, where in the screenshots the user is automatically loaded into the updated Sbrowser after install, the actual behaviour is that that once the Sbrowser is upgraded, they are not loaded immediately into the Sbrowser at all. If the user then opens ABP without opening Sbrowser, then ABP will not initialise correctly and when ABP attempts to launch Sbrowser to enable ABP, nothing happens.

So, assuming that the user opens Sbrowser at least once after the upgrade before trying to launch ABP and enable it, then this is fine. But, if they don't launch Sbrowser at all after upgrading, then they will hit the issue mentioned above.