Closed GoogleCodeExporter closed 8 years ago
Did you change the manifest.json file?
Original comment by foran.pa...@gmail.com
on 6 Aug 2010 at 11:18
Yup got it swapped out with the following.
{
"name": "nexus2chrome",
"version": "1.0.1.1",
"description": "A way to push content from your Android phone to your Chrome web browser.",
"browser_action": {
"default_icon": "icon.png"
},
"permissions": [
"tabs",
"notifications",
"http://nexus2chrome.appspot.com/",
"https://nexus2chrome.appspot.com/"
],
"background_page": "background.html",
"icons": { "16": "icon.png",
"48": "icon48.png",
"128": "icon128.png" }
}
Original comment by Vince.KO...@gmail.com
on 6 Aug 2010 at 11:50
edit to last post.
I grabbed the wrong file, I have been also playing with one that is created on
a gmail.com email. Here is the correct file.
{
"name": "nexus2cloud",
"version": "1.0.1.1",
"description": "A way to push content from your Android phone to your Chrome web browser.",
"browser_action": {
"default_icon": "icon.png"
},
"permissions": [
"tabs",
"notifications",
"http://nexus2cloud.appspot.com/",
"https://nexus2cloud.appspot.com/"
],
"background_page": "background.html",
"icons": { "16": "icon.png",
"48": "icon48.png",
"128": "icon128.png" }
}
Original comment by Vince.KO...@gmail.com
on 6 Aug 2010 at 11:53
Can you check your datastore? Click the background.html link, and open the
storage tab. Does it have an oauth_token and oauth_token_secret value?
Original comment by foran.pa...@gmail.com
on 7 Aug 2010 at 1:26
No background.html link in the datastore tabs. Only a id=1 link
Original comment by Vince.KO...@gmail.com
on 7 Aug 2010 at 2:26
If you open chrome://extensions, under android2cloud, you should see a
background.html link. Clicking on it opens the development menu. In that,
there's a datastore tab. It should have a last_link, oauth_token, and
oauth_token_secret value.
Original comment by foran.pa...@gmail.com
on 7 Aug 2010 at 8:03
ok, going in that way and looking at your extension i see the values that you
are talking about. When i do the same steps for my copy of your extension that
area is blank.
Your extension did have one occurrence of the same error generated at the same
line as posted above. Mine continues to produce the same error over and over as
the extension is left on.
Original comment by Vince.KO...@gmail.com
on 9 Aug 2010 at 11:22
Vince, thanks for the information. i'm going to investigate this, and see if I
can't get to the bottom of it. It definitely sounds like something's going
wrong, but I can't say for sure what it is yet.
Original comment by foran.pa...@gmail.com
on 10 Aug 2010 at 12:58
Just cleaning up issues and labels. Still trying to get to the bottom of this--
sorry!
Original comment by foran.pa...@gmail.com
on 7 Sep 2010 at 7:02
Issue 25 has been merged into this issue.
Original comment by foran.pa...@gmail.com
on 7 Sep 2010 at 7:03
Issue 36 has been merged into this issue.
Original comment by foran.pa...@gmail.com
on 7 Sep 2010 at 7:09
Original comment by foran.pa...@gmail.com
on 28 Dec 2010 at 7:25
Original issue reported on code.google.com by
Vince.KO...@gmail.com
on 6 Aug 2010 at 8:45