Catch Exception for Intent.parseUri instead of URISyntaxException

Catch Exception for Intent.parseUri instead of URISyntaxException

Intent.parseUri can throw other excpetions like NumberFormatException.
So we need to catch Exception to avoid crash.

BUG=484336
Committed: https://crrev.com/bf271f140b3e7cec2926e9a24c2f687a39b1cacd
Cr-Commit-Position: refs/heads/master@{#329482}

[Jaekyun Seok (inactive), 2015-05-12 01:49:26]

jaekyun@chromium.org changed reviewers:
+ jbudorick@chromium.org

[Jaekyun Seok (inactive), 2015-05-12 01:49:26]

jbudorick@, please review this CL.

BTW, do you know how to run findbug against this CL on trybot or locally?

[jbudorick, 2015-05-12 01:54:52]

On 2015/05/12 01:49:26, Jaekyun Seok wrote:
> jbudorick@, please review this CL.
> 
> BTW, do you know how to run findbug against this CL on trybot or locally?

locally: https://code.google.com/p/chromium/wiki/UseFindBugsForAndroid

android_clang_dbg_recipe also runs findbugs, but for whatever reason its analyze
step doesn't prompt compilation.

[jbudorick, 2015-05-12 01:55:43]

On 2015/05/12 01:54:52, jbudorick wrote:
> On 2015/05/12 01:49:26, Jaekyun Seok wrote:
> > jbudorick@, please review this CL.
> > 
> > BTW, do you know how to run findbug against this CL on trybot or locally?
> 
> locally: https://code.google.com/p/chromium/wiki/UseFindBugsForAndroid
> 
> android_clang_dbg_recipe also runs findbugs, but for whatever reason its
analyze
> step doesn't prompt compilation.

(which I filed as https://code.google.com/p/chromium/issues/detail?id=486801 and
might look at more tomorrow)

[Jaekyun Seok (inactive), 2015-05-12 02:50:26]

On 2015/05/12 01:55:43, jbudorick wrote:
> On 2015/05/12 01:54:52, jbudorick wrote:
> > On 2015/05/12 01:49:26, Jaekyun Seok wrote:
> > > jbudorick@, please review this CL.
> > > 
> > > BTW, do you know how to run findbug against this CL on trybot or locally?
> > 
> > locally: https://code.google.com/p/chromium/wiki/UseFindBugsForAndroid
> > 
> > android_clang_dbg_recipe also runs findbugs, but for whatever reason its
> analyze
> > step doesn't prompt compilation.
> 
> (which I filed as https://code.google.com/p/chromium/issues/detail?id=486801
and
> might look at more tomorrow)

I confirmed findbugs ran without any failure locally.

[Jaekyun Seok (inactive), 2015-05-12 02:53:13]

jaekyun@chromium.org changed reviewers:
+ tedchoc@chromium.org, torne@chromium.org

[Jaekyun Seok (inactive), 2015-05-12 02:53:14]

torne@ and tedchoc@, please review this CL.

The original CL (https://codereview.chromium.org/1132473004/) was reverted due
to findbugs failure, and so I fixed it.

[Torne, 2015-05-12 10:26:37]

lgtm

[Ted C, 2015-05-12 20:40:58]

lgtm

[Jaekyun Seok (inactive), 2015-05-12 20:45:53]

The CQ bit was checked by jaekyun@chromium.org

[commit-bot: I haz the power, 2015-05-12 20:46:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1134163002/1

[commit-bot: I haz the power, 2015-05-12 20:53:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-12 20:54:45]

Patchset 1 (id:??) landed as
https://crrev.com/bf271f140b3e7cec2926e9a24c2f687a39b1cacd
Cr-Commit-Position: refs/heads/master@{#329482}