An alert popup to inform user about application exit

[pavelz]

Background

The new functionality of reporting non critical errors #4672 enabled proper reporting of one specific kind of *critical* errors, and that is a failure to initialize on app startup. The app actually should not continue operating - it's missing vital parts.

However, #4672 wasn't originally intended to report critical errors but only non-crashing errors. Due to the fact, that we happen to be able to catch said critical error on runtime, we need to display a more specific notification/error and ask the user to restart ABB.

What to change

When the app fails bootstrapping (app startup initialization) display a notification based on the user's error report settings:

1. If the option "Always Send" (Settings -> Crash Reporting) is selected
   1. Display no notification

2. If the option "Ask Me" (Settings -> Crash Reporting) is selected
   1. Display a notification with the following content
      1. Headline: Adblock Browser
      2. Text: Unable to start browser.
      3. Button 1: Send Report
      4. Button 2: Don't Send
   2. If "Button 1" is clicked, send a crash event and close the notification
   3. If "Button 2" is clicked, close the notification

3. If the option "Don't send" (Settings -> Crash Reporting) is selected
   1. Display no notification

After the notification has been closed (or in case it wasn't shown as per point 1. and 3.), display this error message on the splash screen as specified in ​this style guide. Text:

• Headline: Uh-oh!
• 2nd headline: Something went wrong.
• Text: A critical error prevented Adblock Browser from starting. Follow the steps below to quit the app and try again.
• Bullet point 1: Double-tap the Home button.
• Bullet point 2: Swipe up on Adblock Browser to quit the app.
• Bullet point 3: Restart Adblock Browser.

Assets

• Splash screen error message
• ​Splash screen error message style guide
• Splash screen error icon
• Splash screen line separator

[pavelz]

@lisabielik alert texting proposal

Title: "Adblock Browser"
(it's a good practice to link critical alerts clearly to a specific app)

Message: "Browser failed starting up and will close now. The issue was reported if you allowed it."
(this refers to step 1 of required actions which should have happened before this alert)

Button: "Close"
(it should not say anything regularly cheerful like "OK" or "Got it", as there is nothing cheering about app failure)

[pavelz]

How the alert could look like

[pavelz]

Seeing the screenshot, the beginning of message wording could be different. Saying "Adblock Browser" in title and then immediately "Browser failed" feels somewhat redundant.

[pavelz]

SCREEN SHOT 1 OBSOLETE

After some discussion with @mario, this alert should be the only one displayed. Which means that it should show the applicable error reporting options, preventing the need for displaying the former error reporting selection per #4672. New proposal:

Title stays "Adblock Browser"

Message should be more friendly, something along "Oops, the browser cannot start properly and will close now"

The rest varies by already set HockeyApp reporting option:

1. Option "Always Send"

-> Additional sentence in the message "The issue was reported to developers."
-> Button "Close"

2. Option "Ask me"

-> No additional sentence
-> Two buttons of the same phrasing as crash reporting per #4672
"Send Report", "Don't send"
do not display "Always send" as it actually changes the user's sending preference - a controlled shutdown is considered a rare event

3. Option "Don't send"

-> Technically should not display anything and shutdown right away. But Appstore may reject an app with such unwarranted closing
​http://stackoverflow.com/a/12242357
so the same screen as with option 2. is considered. Not displaying "Always send" makes even more sense here.

[lisabielik]

Title: Adblock Browser
Message: Unable to start browser. The app will now close.
Additional sentence: This issue has been reported to developers.

[mario]

Thanks, Lisa. Updated the description. Ready from our side.

[pavelz]

The UI of closing the app will have to be changed to user-initiated. I.e. the user will have to close the app through swiping in iOS app listing, we can just kindly ask the user to do so. Now the texting challenge:

Title: (stays the same) Adblock Browser
Main message (stays the same): Unable to start browser.

Additional sentence for option 1 above (stays the same):
This issue has been reported to developers.
Button: Close

Additional sentence for option 2 above (already established for HA crash handling):
Would you like to send a report to fix the problem?
Buttons: Send / Don't Send

Additional sentence for option 3 above: (PROPOSAL, to be polished)
You disabled report sending, please consider letting us know error code ABCDEFGH.
Button: Close

Following will be an overlay of the browser splash screen (which is the point of bootstrap failure) with a text, which asks the user kindly to click iPhone Home button and kill the app by swiping in app listing. TEXTING REQUIRED HERE.

[pavelz]

Screencast of the failure exit screen

[pavelz]

Screencast of the completed exit screen

[pavelz]

Regarding bootstrap3 screencast, i have configured ABB to "Don't send crashes & errors", which means that it shows the request for contacting developers in other way, per Option 3. Consider the texting per proposal in Comment #8

[mario]

Replying to pavelz:

Regarding bootstrap3 screencast, i have configured ABB to "Don't send crashes & errors", which means that it shows the request for contacting developers in other way, per Option 3. Consider the texting per proposal in Comment #8

At this point the user has actively decided not to send us reports. Regular crash reporting notifications aren't even shown if this option is selected. Thus we should IMHO handle it the same and respect the user's decision not to send us reports. Which also means not prompting him to send us a report via email or the like.

[pavelz]

While i was finalising the translation body, i realized one thing: if the error/crash option "Don't send" is not supposed to yield any popup, presumably because the regular error reporting does not yield, per change at comment 16, the option "Always Send" should not either! Hence Option 1 of this change description does not apply the same way as option 3. @mario agree?

[mario]

Removed the first notification from the scope of this issue in order to align the notification logic with the crash report logic: Only prompt the user to send a report if the default value "Always ask" is configured in the user's crash/error reporting settings.

[mario]

This hasn't landed yet, but it needs to be included in 1.5.2.
Thus I'm already adding the milestone in order to communicate the intended changes before feature freeze.

[scheer]

'What to Change' section 2-a.-ii. 'Text'. States that the text should read 'Unable to start browser.' Actually, it states, 'Unable to start browser. Would you like to send a report to fix the problem?'. As discussed, the text is incorrect.
ly.

[scheer]

Please see the bold text below that outline the current issue.

• When the option "Always Send" (Settings -> Crash Reporting) is selected no notification is shown and the error is still sent. (Currently, due to SDK issues, the error is sent some 15 seconds after the option is selected and the app still active.)

• When the option "Ask Me After a Crash or Error" (Settings -> Crash Reporting) is selected a notification with the following content is displayed. (Currently, due to SDK issues, the error is sent some 15 seconds after the option is selected and the app still active.)

Headline: Adblock Browser
Text: Unable to start browser.
Button 1: Send Report
Button 2: Don't Send
If "Button 1" is clicked, send a crash event and close the notification
If "Button 2" is clicked, close the notification

• When the option "Don't send" (Settings -> Crash Reporting) is selected no notification is displayed.

• After the notification has been closed (or in case it wasn't shown as per point 1. and 3.), the error message on the splash screen as specified in ​this style guide is shown. The Bold 'Current Text' section below currently does not display the correct sentence in-app. Text:

Headline: Uh-oh!
2nd headline: Something went wrong.
Current Text Reads 'A critical error prevented Adblock Browser from starting. Follow these instructions to quit the app and try again.'
Correct Text: A critical error prevented Adblock Browser from starting. Follow the steps below to quit the app and try again.
Bullet point 1: Double-tap the Home button.
Bullet point 2: Swipe up on Adblock Browser to quit the app.
Bullet point 3: Restart Adblock Browser.

[pavelz]

Alright, the wording is really off. Unfortunately it already flies in translation. Offload to next version?

[mario]

@lisabielik, @shikitita,
See two comments above. Unfortunately a slightly different variation of the string stated above landed in the application:
A critical error prevented Adblock Browser from starting. Follow these instructions to quit the app and try again.
instead of
A critical error prevented Adblock Browser from starting. Follow the steps below to quit the app and try again.

We could easily change the English original, but I fear the translations won't be on point then. Tamara, how do the translations of this string read? If you're fine with them, I'd suggest that we fix the English version manually.

[rraceanu]

Verified working with correct text in place:

Iphone 6
iOS 9.1
ABB 1.5.2-dev (1507)

[suneel]

spam