We have been using GCM to send Push notifications for a long time, in the past days, the sending log starts give me the error:
The Push Notification System rejected the request because of an invalid credential
After searching on the web, it seems that a Server API Key is now required to get service working again.
The API Key was created and restricted to IP of my production server on Amazon.
When I try to register the Server API Key in Azure GCM, I got an error 401 unauthorized.
Can anyone give me any suggestion? I don't know what to do anymore, my users can't access our system because authentication token is not being sent. Thanks.
Screen errors:
There is now a visible note in the GCM docs saying:
Starting from Sept. 2016 new server key can only be created in the Firebase Console using the Cloud Messaging tab of the Settings panel. Existing projects that need to create a new server key can be imported in the Firebase console without affecting their existing configuration.
Migrating from GCM to FCM fixes the issue for 401 Unauthorized Error.
If you are just starting to use GCM, instead of creating a project in the Google Developers Console, do it in the Firebase Console. After creating the project, simply use the auto-generated Server Key. Here are the steps where to find the Server Key:
Go to your Firebase Console and click on CREATE NEW PROJECT.
Fill in your desired Project Name and select your Country. After this, the new Project should be active.
Then on left-side panel, click on the gear button and select Project Settings.
Then go to the Cloud-Messaging Tab.
For old GCM projects, you can simply Import the project to the Firebase Console:
Go to your Firebase Console and click on IMPORT PROJECT.
Select the project you want to import and your country.
Click on ADD FIREBASE. After this, the new Project should be active.
Then on left-side panel, click on the gear button and select Project Settings.
Then go to the Cloud-Messaging Tab.
See my answer here for more details.
Related
I am creating Google Smart Home action of google home. But I have not idea, how to connect the dynamo DB with smart home action but I can see here using with firebase. When I ran the command with invocation name in google assistant then it is showing "something went wrong".
I have enabled the home graph API and also created the JSON key file. I also can see their upload JS file button but don't know, what files should I upload there?
Thank You
It sounds like you are going through the Washer codelab, which is a great first step.
When you are configuring your project in the Actions console, you would need to enter your fulfillment URL from your application (rather than the Firebase URLs shown in the codelab).
You also need to set up an authentication server to enable account linking. Once you've completed this, you should be able to test your Smart Home Action through the Google Home app. Remember that you need to configure the console with your application's URLs for authorization and tokens in place of the demo URLs in the codelab.
The JS upload you are seeing in the console is for local fulfillment applications, which would be a feature to consider adding after you have successfully uploaded and tested your Smart Home Action.
I am trying to publish a project from Visual Studio 2019 (fully updated) to azure. But when I try to login I get the message:
Your account is at risk
To help you—and only you—get back into . I verify my account by sms message and enter the old and new email address. But then again when I try to login it again wants me to verify.
At the same time, the email works when I go into Azure portal and I also managed to deply a Microsoft SQL database into Azure SQL. (Though initially I had to add the IP address in the firewall on Azure). Also I updated the location of the user to Thailand (Where I am), in case the system matches the IP address to the location.
OTher things I have in place are for example the resource group. And I also tried to create an app in Azure portal and then publish it to this, but the issue is that I can't login from Visual Studio.
Any suggestions on how I can publish a project to Azure?
------- UPDATE --------------
Still in the loop of login, verify, new password and login again. The screen I get is like this:
The following screens are:
enter code send by sms
Enter old and new password
Login
-. And back at the verify screen again.
Any suggestions.
Based on the suggestion below I also removed some of the credentials in the credential manager (those that I thought might have to do with this issue).
One possiblity is that there is an old version of your password stored in Credential Manager.
When you try to login via Visual Studio it fails because the password is incorrect. Trying to login with the incorrect password also causes the account to lock, requiring you to verify with SMS.
If this is an Azure WebApp, your best bet is to download the publish profile and use it in your Visual Studio, this way you'll be able to publish your app.
I could see API Keys section, when I initially created an agent and I could get the client access token under this and use this in my app successfully. But then, when I updated Dialogflow agent with some more input, it wasn't reflected, when I ran the app.
Then I thought, the client access token could have been updated and checked for API Keys section. To my surprise, this section is completely missing now. Even deleting the agent and recreating a new agent, didn't help. API Keys section is still missing. Please help
API Keys were a feature of v1, which has been shut down.
You should be using Google Cloud service accounts with Dialogflow v2.
Working with the Azure enterprise bot model, everything is deployed, enabled and functioning. But all calls to LUIS are failing in the chatbot, both on desktop and in Azure's web environment. My LUIS model works in luis.ai when testing, but when connecting to LUIS from the bot I get the error below:
The only thing that does not work is the call to LUIS from the chatbot. It returns unauthorized. I've spent about 8 hours on google and verifying settings. Can somebody tell me where the checkbox is that i've missed?
Basic chatbot function is good.
microsoft app id and secret are good.
QNA maker implementation is good.
Publish cycles from Visual Studio is working fine.
I have verified the LUIS app functions in luis.ai.
I have verified all keys are properly written in cognitivemodels.json
I have verified all keys are correct by changing them incrementally, noting that the app fails, restoring to the correct value, and noting that the app functions.
trace results:
App ID:
Version: Unknown
Slot: Production
Recognizer ResultRaw Response
{
"recognizerResult": {
"alteredText": null,
"entities": {
"$instance": {}
},
"intents": {
"l_general": {
"score": 0.6153312
}
},
"text": "test"
}
}
Top-Scoring Intent
l_general (0.6153312)
Please add your LUIS service to enable reassigning.
Entities
No Entities
error from emulator log:
[LUIS] Unauthorized: Your bot is not configured to interact with LUIS app: . Please connect your bot to LUIS using the services pane.
The service pane appears, I add in all the keys and information as copied from luis.ai for the referenced appID. On save, the pane disappears and nothing changes.
This error looks to be specific to the Bot Framework Emulator as per this code.
I can reproduce the error locally by doing the following:
Debugging my bot.
Submitting a query that will trigger a request to LUIS.
Clicking on the hyperlinked trace text next to a LUIS Trace log entry in the log pane.
You aren't actually able to add a service to a bot without creating a bot configuration first (File > New Bot Configuration). Fill out the following:
Bot name
Endpoint URL (use your local one)
Microsoft App ID
Microsoft App password
Save and connect
Save the configuration somewhere
Then you will be able to add the services:
Click the + next to the Service.
Add your LUIS apps by filling out the dialogs.
Try the steps in the first set of my bullet points again and see if errors come through. If they do then you will need to add a service for the GUID that comes back in the error message - this GUID will match one of your LUIS app ids.
Even after doing this I still got the error message in the Log page, starting the emulator and bot didn't help. So I would advise raising an issue on the official GitHub for the Bot Framework Emulator about adding the services not working.
My AD password changed, Powershell had cached my credentials. Although I was not actively using powershell, apparently my credentials are locally cached on the dev box and used for some specific funcitons, which manifests as seemingly random authentication errors in logs. logging out of azure and logging back in (in powershell) resolved the issue.
Oh the hours of my life I will never get back.
I am developing Windows 8.1 Application and want to implement push notification using WNS.
I have updated my app to dashboard and also associated my app with app store . I followed Push and periodic notifications client-side sample.
I debugged this sample and found the channel URI (notify.....com) .I am trying to get my app channel Uri but I am not able to get any Uri .I think I am not implemented properly.
Please help me to troubleshoot this issue and share some idea for the below points.
How to associate Windows 8.1 App with App Store.
How to enable Push Notification Service using WNS ( any other procedure also).
Local Configuration.
How to get channel URI.
link
Please find the error on the below attached image.
How to associate Windows 8.1 App with App Store.**
In your store dashboard navigate to the particular app and on the left you will see a list having items like analyitcs,services etc. Click on services->Push Notification. Then click on the live service site. See Screenshot
Then update your solution with Name and publisher. This should set you up. and also take cares of question 2 and 3 of your post.(Associating your app from store should do this automatically once you have enabled push from dashboard)
And to get channel URI just call the following method in your code:
PushNotificationChannel channel = await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
var myuri = channel.Uri;