Update to use the new remoting API keys
Previously Chrome Remote Desktop uses GOOGLE_API_KEY_REMOTING_FTL and GOOGLE_API_KEY_REMOTING_FTL_MOBILE. This internal CL defines a GOOGLE_API_KEY_REMOTING macro for each of the platform: https://chrome-internal-review.googlesource.com/c/chrome/google_apis/internal/+/1283134 This CL updates google_apis and existing code to use the new GOOGLE_API_KEY_REMOTING. I'll remove GOOGLE_API_KEY_REMOTING_FTL(_MOBILE)? once this CL is checked in. Bug: 961541 Change-Id: I03073acb23950fe0d361081b1bbf2c2fdfe750f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1605159 Reviewed-by: Roger Tawa <rogerta@chromium.org> Reviewed-by: Joe Downing <joedow@chromium.org> Commit-Queue: Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#658779}
This commit is contained in:
@ -73,10 +73,8 @@ std::string GetAPIKey();
|
||||
// Non-stable channels may have a different Google API key.
|
||||
std::string GetNonStableAPIKey();
|
||||
|
||||
// Retrieves the Chrome Remote Desktop FTL API key to be used during the
|
||||
// signaling process.
|
||||
std::string GetRemotingFtlAPIKey();
|
||||
std::string GetRemotingFtlMobileAPIKey();
|
||||
// Retrieves the Chrome Remote Desktop API key.
|
||||
std::string GetRemotingAPIKey();
|
||||
|
||||
#if defined(OS_IOS)
|
||||
// Sets the API key. This should be called as early as possible before this
|
||||
|
Reference in New Issue
Block a user