I'm trying to get an Android Wear watchface set up that gets the number of steps the user has taken. To do that, apparently I have to get the data from Google Fit. Step 3 of that process is getting an OAuth 2.0 client id. I'm following the steps in the link below.
Request an OAuth 2.0 client ID in the Google API Console
The first step is clicking the blue GET A CLIENT ID button. In there I select my project and click Continue. That enables the Fitness API. Then I click on the blue Go to credentials button. There I choose Android for where I'm calling the API from and User data for the type of data that I will be requesting. Then I click the blue What credentials do I need? button.
This page is where the problem lies. I am supposed to enter a name, SHA-1 fingerprint and package name. However, all three fields are disabled so I can't type in them. If I go ahead and click on the blue Create OAuth client ID button, it marks those three fields in red with some verbiage about being required. I still cannot type in the fields.
How is this supposed to work?
I was facing the same issue today. In case you haven't found a solution to your problem, you can try creating a project with a different Google account. I think it happens because of the conflict with your previous projects.
Related
I'm trying to request access to this API by following their instructions:
https://developers.pinterest.com/blog/2022/04/12/introducing-pinterest-api-v5/
Note, that the location in the help does not exist. I went for "Pinterest API and Developer Tools > API Access".
However, the response from filling in the form was:
Hello there, we could not complete your request because '' appears to be an invalid
advertiser ID. Please enter the correct ID in the Advertiser ID field in the left-hand pane on this page and then
change this ticket back to OPEN.
The form I filled in did not ask for an "advertiser ID" and it is not relevant. There was no link for "this page", and there seems to be no way to find the "ticket".
Has anyone managed to make a request for access? If so, how?
Or does anyone know how to find their tickets?
I am sending an activity Feed notification to the user which is pointing to my personal app.
I have a DeepLink generated to point to the tab and it's working fine but when I add a SubEntuityId to the tab it is not fetched in.
It is always blank.
I have also tried with URIEncode for the same.
So presumably you're replacing APPID with the real app id from your manifest file. Separate to that, make sure that "overview" is registered as the actual entity id for the tab in the manifest. Other than that, the rest looks fine, like it should work.
We have a live application that gives the "The API developer key is invalid" intermittently.
The normal flow:
User clicks "Import from Google Drive"
Gets an OAuth screen
Selects a user (if there are more than one)
Gets prompted with the Google Picker
Picks a file
File gets imported
But for some users, after selecting a user in point 3 (or automatically if there is only one user) the Picker dialog doesn't open, but gets prompted with an "In order to select an item from your online storage, please sign in" message on black background with red Sign in button on it. (see screenshot)
Sign in screen
Then after clicking "Sign in", the user receives the "The API developer key is invalid" error message, and the flow stops. (see screenshot again)
API key error screen
For the majority of the users everything works fine. Seems to be a per user issue, because we have an affected user that has multiple gmail addresses signed in into Chrome, and this issue happens with one email address, but doesn't happen with the other.
Any ideas?
After a long search, I found a workaround. I had to replace the gapi.auth2.init and gapi.auth2. signIn calls with gapi.auth2.authorize and it started to work for those affected users too. Submitted a report to Google about it, but at the time of writing, there was not much reply: https://github.com/google/google-api-javascript-client/issues/613
My scenario is: I send card attachments each with an AcceptButton to users. When 1 user clicks on that button, ideally I want to disable all similar buttons (of the same offer) for all users. I am storing conversation details of each user, and I know the ActivityId of each message-with-said-button (it follows a certain string format).
My issue is similar to this and this but for WebChat not Teams.
I did try those solutions but I got the error "Method not allowed" for both UpdateActivityAsync() and DeleteActivityAsync(). Then I read here that UpdateActivity is not supported in WebChat. (But might be available in the future?)
I would like any visual indication that the offer is no longer available. (Right now, they receive an "Offer was already accepted by {UserX}" which would still be in place on top of changing the card/message.)
Is there a way to do this via backChannel? I can trigger an event and pass the ActivityId (tested by showing a simple alert()) but how do I apply changes to that specific activity?
Per this comment in Web Chat's source code and this open issue in the Web Chat repository for adding support for deleteActivity and updateActivity, Update Activity events are not currently supported in Web Chat. Unfortunately, there is currently no way to really update an activity in Web Chat.
Hope this helps!
I'm trying to add the Cortana channel to a bot I've been working on today. However, when the page loads, the entire form is greyed out except for the knowledge.store Register button, and the Cancel button.
I've read elsewhere that people have managed to get past this by clicking really quickly on the Save button that appears briefly as the page loads, but I've had no luck with that. The (very helpful) tech support guy suggests it could be due to special characters or numbers in the bot name, but I have the exact same issue with a bot name that's just lowercase letters.
UPDATE: I can now see my knowledge.store organisations in a dropdown next to the Register button. Clicking the Register button throws a "Failed to create bot module" error. I am able to connect the channel successfully on another bot I made to test the issue.