I am working on server side (Receiving print jobs to printer); I am following the developers guide mentioned as "https://developers.google.com/cloud-print/docs/devguide#registering"
I am able to register/add printer to google cloud. Got a register_token;
I am able to claim the ownership of the printer and then till refresh and access tokens.
The printer I am just adding, I am able to see in my printers list through browser.
But, the status of it remains 'offline'. I am really wondering if I am missing some basic thing. How to make this printer online
Printer come to online when we restart computer and sign in again but it does not work always :(
Related
I have been banging my head against a wall for the last two weeks. I'm trying to set up a contact me web page for my business. Having read all the warnings about mailto, I opted to use phpmailer for this. Similarly, I decided to use XOAUTH2 for sending the mail through gmail. I found several sites, including instructions at the phpmailer github page, that should have walked me through doing this.
Here's where I run into problems. After logging into the Google developer console, creating my project, and enabling the gmail api, all of the sites that I found talk about creating my new client ID. Every single one of them tell me that I will get a simple pop-up where I click that I want to create a web application, fill in a few items, and voila, out will pop my ID. When I did this, however, I was required to complete the consent screen before I could do anything else, and these screens did not match anything that was shown on the web sites I used as a guide. I muddled through as best I could and did finally get a client ID (I think/hope).
Does anyone know of a site or sites that walk a person through this in a way that matches what the development site actually displays? Did Google recently change things and the help sites haven't caught up? Having to guess at some of this is definitely not the way to do things. I'll be testing the results in a couple of days, but won't be surprised if things don't work right. At that point, I'll probably need more help to figure out what went wrong.
Thank you for listening to my rant.
Initially, I built up a test agent on DialogFlow console according to the document, and it works well on the Actions On Google which is a simulator of Google Assistant on mobile devices.
Then, I deployed it through the Release in the left menu as you can see the pic attached.
deployed successfully
After that, I added some Alpha Testers including my colleague and sent my opt-in link to my colleague, besides, I granted them all the viewer permission in IAM.
However, problem appeared. It didn't work well on my testers’ phone(IOS 10+) but only worked well on developer's account(mine). When they opened the link I sent to them, and clicked send to devices, then clicked the notification on top of the screen.
send to device
The result is shown as below.
Google Assistant didn't respond to "Talk to mytest app"
In my case the command was set as "Talk to hello qad", and it did work well on my phone used the developer account.
developer account works well
If my tester input the text "Talk to hello qad", it just replied some direct searching results not hello qad diaglog.
To recap:
My action has already been in "deployed" status for couple of days
I've added the tester accounts in whitelist and give them "Viewer" permission in IAM
Testers could see the action directory page in devices by open opt-in link, but they couldn't see the "I'm In" button and couldn't access the action
Appreciate for any help or advice
During my project development, I also faced a similar issue. This is how managed to do testing:
Made sure all Google Accounts were created with the US as the country.
Through IAM, share AoG project with the tester's Google accounts.
All testers to open the shared simulator link in their browsers. This is important!
Test the app on browser first using the simulator.
Once tested, use any device with the whitelisted Google Accounts.
US country was required for my use case as I was having Transaction API in my Assistant. I had to also mock my location to the US on mobile for testing US specific features.
See if the above steps help you.
I contacted Google and this is what they said:
You have to copy the link to the notes app, and then click it and in the prompt, choose “Open in Assistant”.
Full text:
Please ensure that the opt-in link is opened in Google Assistant app and not in a browser. At this time, Google Assistant app is only available in USA. For opening an opt-in link in iPhone or any iOS device, please follow the steps below:
1. Download the Assistant App in App Store
2. Log in using the included account for Beta testing
3. Copy the opt-in URL to Notes app
4. Hold press the opt-in link then select 'Open in "Assistant"'. Google Assistant and App page in the Assistant Directory will be displayed.
5. Scroll down the page until you see the "Become a Beta tester" section
6. Click the I'M IN button
7. Test the Action
This does not work for me, probably because I am not in the US. However, the app is of course available here.
I ran into a similar issue with Google Actions/Dialog Flow. Here is how I resolved it...
Share the app from within DialogFlow to the test user
Copy the current DialogFlow URL from the address bar
Launch an Incognito Window
Paste the DialogFlow URL from Step 2 in the address bar
Log into DialogFlow using the test account
At the Standard Google Account Access Prompt Allow the access so your Google Action can talk to DialogFlow.
I couldn't find this documented anywhere and wasted about 8 hours figuring it out.
For me it only worked after I shared with the user the link to test on desktop that look likes: https://console.actions.google.com/project/XXX/simulatorcreate?isDeepLink the one you can get the the console menu on the sharing icon.
I asked him to login with same google email he has opted-in in Google Assistant and
to verify if when mouse over on the devices icon on the menu he would see "Testing on Device: Enabled
You currently are able to test your Actions on all
Assistant devices connected to "xxxx#gmail.com". "
Then he could invoque almost right away the alpha version of the BOT.
All that considering that he has already clicked on the opt-in link, I had added his emails as a Alpha tester and I had also added him as a Viewer on Permissions at the console admin https://console.cloud.google.com/iam-admin.
If you are a developer of the project, the test version is enabled by default on your device. If you want to access the alpha and beta versions, make sure to disable the ‘Testing on device’ option on the Actions Console simulator.
Add users before deploying alpha release
I feel obligated to copy dedman's comment on your question here, since his solution worked for me and is the only one directly addressing the problem at hand: an alpha release is not available to testers you have added after deploying the release.
As stated in question, you first deployed the test version and then added alpha testers. You might have to publish new alpha version "after adding the testers" and then wait till you get "deployed" status on the new alpha release too... – dedman
I was encountering this exact problem with the Alpha release of my Action, i.e. assistant not responding on alpha users devices, even though I had deployed the release, shared the opt-in link with users and had them click on it to opt-in. Deploying a new alpha release after users had clicked the opt-in link solved the problem and the action is now responding correctly for all users.
IAM Viewer status is not mandatory
By the way, I can also confirm your suspicion that "Viewer" permission in IAM is not needed for alpha users to have access to your release - they only need to opt-in before you deploy a new release.
Link to previous issue: Gmail contextual gadget broken
Yesterday we received a couple of customer complaints regarding our Gmail gadget. They claimed that it had gone missing from their account. This morning, several of our employees have reported the same although, this isn't happening for everyone.
We haven't made any changes to the gadget and since it loads for some, I don't think this was caused by us.
What happens:
The window of the contextual gadget does not appear in the main Gmail interface
The window of the contextual gadget does not appear when opening an email in a new window (shift + click). This differs from when this happened previously.
We've also contacted Google and they have responded that they are looking into the issue. We've also seen that the shift-click to open an email in a new window doesn't work as a work around this time.
The last time this happened our monitoring showed that about 10% of users lost their access to the gadget per-day. We seeing a similar drop off in activity this time around.
Here are the details of the response I received from Google for this issue
Thank you for contacting Google for Work Support. I understand that
that you Gmail Contextual Gadgets have disappeared again from the
Gmail web interface.
I notice there are other user reporting a similar behavior hence he
have requested an update from our Eng team and I am currently waiting
for their response. As soon as I have an official response, I will be
contacting you back directly with the next steps.
Also I notice you mentioned that the previous workaround is no longer
working. Previously the workaround provided was to press "Shift" and
then click on the email. The email will be opened in a new window and
then the gadgets should be displayed. Can you please confirm if the
above workaround is working or not?
I’ll keep this case open while I wait for your reply. If you have any
other questions or additional comments, don’t hesitate to reply and
I'll be happy to continue helping you.
Sincerely,
Wilmer Google for Work Support
Here is the latest update from Google
As before this issue appears to be UI based as opposed to any problem with the Contextual Gadget API itself, we've gathered some troubleshooting information from affected test environments and are working on identifying a clear root cause and then remedying the behaviour at the moment.
There isn't any further you need to do on your end, I'll update you as I learn of any changes in the status of this behaviour.
Regards,
Patrick
I am trying to make it so that when a user turns on their device (will either be a tablet or a laptop) a DocuSign document loads up immediately. The user must sign the agreement before using the device. After that I want them to have access to the device and each boot thereafter I want the device to boot up normally. Can anyone help me with that. I would prefer that the DocuSign document is a pdf, but the format is not the most important variable in this equation. Getting the idea to work is important, I'm completely open as far as file formats and computer languages go. The signed document would be sent to a predetermined email address. Thank you in advance for any help provided. -Domitros
Also, all devices will be running on windows 8
I was thinking of using a batch file to load the DocuSign document? But, like I said, I'm open to suggestion.
What I've done so far is as follows: I created a new standard local account. I set windows to boot up as the newly created user. On their desktop is only 1 icon, a shortcut to the Docusign user agreement that they need to sign. I'm set to receive notification when a document has been signed. Unless I can figure out a means of automation I will have to remote into the users device, via citrix, and erase the user mentioned above and set windows to boot up as the user with access to all the software necessary for the user to do their job. Seems like there is a better way, but I'm not seeing it.
Obviously, after the crash Developer tools at port 9222 is of no use, because "Remote debugging has been terminated with reason: websocket_closed". How can I retrieve, for example, recorded timeline; or get call stack; or find anything about the reason the Chromecast decided to reboot itself? What are the best (or, for that matter, any) approach to debug Chromecast crashes?
We need to look at your log file to see what is causing the crash. It is relatively easy to do that but we need some help from your side.
First, open the Chromecast setup app on, say, your Android device and go to the settings for your device. You should see a check box that states something like: "Send Chromecast usage data and crash reports to Google". If it is not checked, make sure you check it and then wait 15 minutes or so and reboot your chromecast.
Try to recreate issue and as soon as it crashes and reboots itself, open the setup app again and select "Submit feedback report" from the overflow menu. You will see a new window on your phone and make sure you enter the following text in the text box there "crash-vmt". We will be using this text to search among the reports that we receive to identify your log.
After doing that, please let us know (add a comment here) so we can grab the log for further investigation.