[Remoting Android] Fix crash caused by fetchAuthToken()

[Remoting Android] Fix crash caused by fetchAuthToken()

Previously auth token was only fetched after the account switcher set the
account. A recent refactoring makes the app attempt to fetch the auth token
even before the account is set, so the fetchAuthToken() function just throws
an exception and crashes the app.

Since we are pretty sure that the Java code will soon feed the logger with the
auth code once the account is set, it's safe to fix this by loosening the check
to just a warning log.

Alternatively we can remove the immediate RequestAuthTokenForLogger() call from
ChromotingClientRuntime and make the logger request the auth token before it
tries to send out the logs. It depends on how the iOS client wants to provide
the auth token.

BUG=703381
Review-Url: https://codereview.chromium.org/2761983002
Cr-Commit-Position: refs/heads/master@{#458515}
(cherry picked from commit ced631a3b4de3fd68d98ecc1620d76b47a5ea9b2)

[Yuwei, 2017-03-21 21:03:25]

The CQ bit was checked by yuweih@chromium.org

[commit-bot: I haz the power, 2017-03-21 21:03:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-21 21:03:54]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-21 21:03:55]

No L-G-T-M from a valid reviewer yet.
CQ run can only be started once the patch has received an L-G-T-M from a full
committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,_not_ a
full super star committer.
Committers are members of the group "project-chromium-committers".
Note that this has nothing to do with OWNERS files.

[Yuwei, 2017-03-21 21:43:57]

Description was changed from

==========
[Remoting Android] Fix crash caused by fetchAuthToken()

Previously auth token was only fetched after the account switcher set the
account. A recent refactoring makes the app attempt to fetch the auth token
even before the account is set, so the fetchAuthToken() function just throws
an exception and crashes the app.

Since we are pretty sure that the Java code will soon feed the logger with the
auth code once the account is set, it's safe to fix this by loosening the check
to just a warning log.

Alternatively we can remove the immediate RequestAuthTokenForLogger() call from
ChromotingClientRuntime and make the logger request the auth token before it
tries to send out the logs. It depends on how the iOS client wants to provide
the auth token.

BUG=703381

Review-Url: https://codereview.chromium.org/2761983002
Cr-Commit-Position: refs/heads/master@{#458515}
(cherry picked from commit ced631a3b4de3fd68d98ecc1620d76b47a5ea9b2)
==========

to

==========
[Remoting Android] Fix crash caused by fetchAuthToken()

Previously auth token was only fetched after the account switcher set the
account. A recent refactoring makes the app attempt to fetch the auth token
even before the account is set, so the fetchAuthToken() function just throws
an exception and crashes the app.

Since we are pretty sure that the Java code will soon feed the logger with the
auth code once the account is set, it's safe to fix this by loosening the check
to just a warning log.

Alternatively we can remove the immediate RequestAuthTokenForLogger() call from
ChromotingClientRuntime and make the logger request the auth token before it
tries to send out the logs. It depends on how the iOS client wants to provide
the auth token.

BUG=703381

Review-Url: https://codereview.chromium.org/2761983002
Cr-Commit-Position: refs/heads/master@{#458515}
(cherry picked from commit ced631a3b4de3fd68d98ecc1620d76b47a5ea9b2)
==========