Obsolete
Status Update
No update yet.
Comments
vi...@google.com
Can you provide the below requested information to better understand the issue:
Android build
Which Android build are you using? (e.g. KVT49L)
Device used
Which device did you use to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Android build
Which Android build are you using? (e.g. KVT49L)
Device used
Which device did you use to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
vi...@google.com
Please provide the information requested in
vi...@google.com
We are closing this issue as we don't have enough actionable information. If you are still facing this problem, please open new issue and add the relevant information along with reference to earlier issue.
yu...@google.com
Running into a same issue,
So far we have seen this reported in VFD 610, WP5000, SM-J415FN.
https://screenshot.googleplex.com/escwx1XJ7t1
So far we have seen this reported in VFD 610, WP5000, SM-J415FN.
yu...@google.com
You can take a look at this tracking bug for more info :
sa...@google.com
We will be closing this bug as Obsolete. If you still think this issue is reproducible and relevant in the latest Android release (Android Q), please attach a new bug report along with reproduction details. If a reply is not received within the next 14 days, this issue will be closed. Thank you for your understanding.
te...@google.com
cu...@gmail.com
"But alas, it was not Obsolete." - the narrator.
still reproduceable from time to time.
still reproduceable from time to time.
Description
calling `super.setText()` with default provided parameters (the raw values without any modifications) throws an exception which implies WebView is not installed on the device. I figured out setting `setAutoLinkMask(Linkify.ALL)` causes the problem. Following the stack trace shows following lines produce the exception.
```java
if ((mask & MAP_ADDRESSES) != 0) {
gatherMapLinks(links, text);
}
```
**Additional Information**
- **supportLibVersion:** 27.1.1
- **compileSdkVersion:** 27
- **buildToolsVersion:** 27.0.3
- **minSdkVersion:** 16
- **targetSdkVersion:** 22
**Workaround**
```java
try {
super.setText(spannableStringBuilder, type);
} catch (Exception e) {
// WebView is not installed in some devices by default, Linkify.MAP_ADDRESSES causes the exception
if (e.getMessage().contains("webview")){
setAutoLinkMask(Linkify.WEB_URLS | Linkify.EMAIL_ADDRESSES | Linkify.PHONE_NUMBERS);
}
super.setText(spannableStringBuilder, type);
}
```