I'm trying to access the Facebook config page for my bot and I keep getting "Sad bot is sad... can't find a bot named bot_name"
Is anyone having issues with the platform right now?
Microsoft's team solved it, as it's showed here.
We're not having any portal specific problems. If you want to share your bot handle with us at BotFramework#microsoft.com I can see if there's anything interesting in our logs.
-- just a note, we were actually having portal problems, it was just impacting only one box in one datacenter making it erratic to track down. Thanks for the report!
Related
I got the below popup when I tried to execute the google form api from google developer documentation.
I tried this same process with google docs api which work perfectly. I tried tp turn on less secure app access, but it seems google made it unavailable.
what is the other way out.
Thanks
This appears to be a bug with the try me on forms.
I have logged it on the issue form and im going to see if i can find someone at google to ping about it
Forms.get try me not working
I suspect however that this may have something to do with the app being in early access. That being said i would have expected a different error message if that was the issue.
It is most likely due to the permission for the client they are using. It is an internal error and not something you have done.
May i suggest creating your own app and testing it that way. Just remember this api is in early access so be sure that you fill out the form found on this page Google Forms API now available in open beta
Developers can apply to join our Early Adopter Program and begin developing using the Google Forms API by filling out this form.
I submitted our company Outlook add-in and received a review email asking for corrections. I saved the URL of the submission page https://partner.microsoft.com/en-us/dashboard/office/products/ce33a138-e74c-4db2-a241-47f05ef4f9c7/packages before submitting the add-on. This is that page:
If I log in now to I can no longer open this page and see the default page instead https://partner.microsoft.com/en-US/dashboard/directory
It is hard to believe that Microsoft requires a brand new add-on submission with all icons and screenshots to be added again. I definitely use the same Microsoft account - we have one company account associated with an email group in our company.
Both links in the Microsoft review email lead to https://partner.microsoft.com/en-US/dashboard/support where I see
"You don’t have access.
You don’t have permission to view this page. Contact your account
admin for access. Learn how to manage permissions."
The submission process was way easier and way friendlier compared to doing the same with submitting Google add-in until this point where I literally lost access to all hard work already done and can not move forward.
Any help will be greatly appreciated!
I think you should be contacting the support team for Partner Center and they can help you here. Please start from here https://partner.microsoft.com/en-US/support/v2/?stage=1
I hope you will be getting the answer what you are looking for.
Thanks,
Jeevan Desarda
Even though I am sure I used account type (1) to submit the application for a review I finally tried to use (2) and was able to access my application submission again. I was able to resubmit it with corrections being made based on the MSFT team feedback.
[![Microsoft account type selector][1]][1]
[1]: https://i.stack.imgur.com/iSaLb.png
I have my bot registered in dev.botframework.com. It is published, up and running well. I'm trying to integrate it on Microsoft Teams. For that, I need to create a manifest, which I'm doing using App Studio. When I arrive to the part of configuring the the bot endpoint on App Studio, App Studio says that I need to add teamsappstudio#microsoft.com to my bot, admin textbox in order for it to find my bot. Here's what it says that I should do:
So, I added teamsappstudio#microsoft.com to my bot as an admin as AppStudio says that I should do, but when I click "Setup" in the last part, it shows me the error: "We couldn't access your bot. Make sure you've added "teamsappstudio#microsoft.com" as an admin and try again".
I don't know what else to do!!
Help me with this one guys.
Thank you!
The of Teams App Studio that's live now has a bug - sometimes the email address we extract from your authentication token has uppercase characters. We assumed they were all lowercase but it's likely yours are not. We are changing the logic to ignore case so in a week or two it should work properly.
Sorry for the confusion and hassle.
I have created a bot service app in Azure that works fine when I create it. I go through the Microsoft App ID, password screen and it loads the chat emulator and code in browser (using the LUIS template and node.js language). After sometime, if I go back to load that app service from Azure dashboard, it keeps giving me "An Internal error occurred at the server" error message. I am not sure if I shouldn't be going to the newly created Bot Service from dashboard? I did this 3-4 times already, with new names, new RG etc., it's the same issue every time.
Thanks
Unfortunately this looks like a bug, there are are two open issues right now on the SDK's repo that look very similar to yours. Here is one of them; 'InternalServerError - Bot & QnA Maker'.
Regarding the downvote, it might be because there isn't a screenshot of the issue which usually helps in answering questions. Also, explaining the steps you undertook or compared against would have helped give a clearer picture for the community to answer.
I'm Trying to modify information in the Linked Apps section of Google Play Games Services in the Developer console. Things such as translated titles and whether or not the game uses anti-piracy or not.
It is coming up with the following error every time:
Your changes could not be saved. Please try again. (-32600)
Has anyone come across this?
That's because you're logged in to the above console using account 1, and later tried accessing the console from another Google Account. I faced the same issue and was resolved once I was logged back in to the correct account