Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chrome.identity.getAuthToken never seems to return #16489

Closed
DartBot opened this issue Feb 2, 2014 · 2 comments
Closed

chrome.identity.getAuthToken never seems to return #16489

DartBot opened this issue Feb 2, 2014 · 2 comments
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue

Comments

@DartBot
Copy link

DartBot commented Feb 2, 2014

This issue was originally filed by @taisph


What steps will reproduce the problem?

  1. Create a new Chrome packaged application with sample content.
  2. Replace the 3 attached files.
  3. Launch the manifest.json

What is the expected output? What do you see instead?

I expected to see the auth token printed in the Output window (or on the console).

App opens the window and the browser window switches to a Google login prompt. After login a small popup is displayed saying "Oops, sync has stopped working". Neither the token or the error is printed.

What version of the product are you using? On what operating system?

Tested with:

Dart Editor version 1.1.1.release (STABLE)
Dart SDK version 1.1.1
Operating System: Ubuntu 13.10

Dart Editor version 1.2.0.dev_02_04 (DEV)
Dart SDK version 1.2.0-dev.2.4
Operating System: Ubuntu 13.10

Please provide any additional information below.
Debugging/exceptions/breakpoints isn't working in packaged apps.


Attachments:
manifest.json (353 Bytes)
dart_chromeapp_identity.dart (518 Bytes)
pubspec.yaml (123 Bytes)

@lrhn
Copy link
Member

lrhn commented Feb 2, 2014

Added Area-ChromeApps, Triaged labels.

@DartBot
Copy link
Author

DartBot commented Feb 4, 2014

This comment was originally written by @taisph


I figured out that the sync problem is related to missing API keys in Dartium. After getting that set up correctly (environment vars in the "manage launches" dialog doesn't seem to have any effect btw.) the sync problem disappears and getAuthToken() then returns properly with either the expected token or an appropriate error.

@mit-mit mit-mit closed this as completed Sep 2, 2015
@kevmoo kevmoo added closed-not-planned Closed as we don't intend to take action on the reported issue and removed triaged labels Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

4 participants