I have created my first bot application, but it's giving an error while running in the Bot Framework Emulator. it shows status of message I sent like "Couldn't send". Please suggest me what could be the reason.
I had to launch the emulator with Run as Admin
The url of your bot in the emulator is wrong. It should be http://localhost:3979/api/messages
For those trying to run the mac version of release 4.2.1, download the .zip file.
The .dmg version is not working for some reason.
I also had the same result, running V4 PREVIEW 40025 of the emulator.
The log window was blank, and I saw "couldn't send" (no retry)
I downloaded 3.5.6 and ran it, Windows asked to confirm it was allowed to communciate through the firewall, said yes
Pointed the older emulator at the endpoint (my sample was running on http://localhost:3979/api/messages - web page visible in Edge at the root of this url so I knew that part was ok) and it loaded, did version checks etc, (so log window not blank)
Every message still says "couldn't send" but now says "retry". Putting a breakpoint on the first line of
public async Task<HttpResponseMessage> Post([FromBody]Activity activity, CancellationToken cancellationToken)
{
Shows the request was being sent to the bot, but it only gets to
if(Middleware.RejectMessageBasedOnTenant(activity, activity.GetTenantId())
Before saying "couldn't send" - I haven't followed the instructions ("Set the OFFICE_365_TENANT_FILTER key in web.config file with Tenant Information") yet, but wanted to post this to give a set of steps you can try taking..
Oh, and the V4 emulator also now works as expected/as above..
Check your firewall, restart the web site and the emulator.. Check that the emulator succeeds in comms with the web server, and that you see "Hello I'm your new bot" in the chat window of the emulator
To help those who had the URL right, but still got the "Couldn't send" message.
I was running version 4.0.15 of the emulator and I was getting no response back whatsoever.
Eventually I found that installing an older version of the emulator, (3.5.2) worked for me - if at first it doesn't work, just check that the port is correct as it defaults to port 3978.
Hope this helps!
I had this issue for the emulator V4.2.1. Just we need to allow the app in the firewall and it will work fine. (Provided if you have the url correct and then you are facing the 'couldn't sent' issue.
Check this link. : https://pureinfotech.com/allow-apps-firewall-windows-10/
I had a similar issue - but no logs were showing in the window.
I tried un-installing the Bot Framework Emulator, then re-installed and everything just worked. 🤷♂️
Related
I'm building a Cast app with a chrome sender and custom HTML/CSS/JS receiver. While it works correctly from desktop chrome, I've noticed that I can't connect via the Android Chrome app.
With Android, when clicking the Cast button and selecting the correct receiver device in the Popup, nothing happens (my listener for SESSION_STATE_CHANGE is not called). After clicking the button again, my session listener says:
{type: "sessionstatechanged",
session: null,
sessionState: "SESSION_START_FAILED",
errorCode: "invalid_parameter"}
At first, I thought my setup was incorrect, but after looking at the official chrome sender app and following the same steps as above, I noticed a similar problem with a different error code:
Request session failure:
{"code":"invalid_parameter",
"description":"Already requesting session",
"details":null}
In the above case the visual indicator starts it's 'active' state on first click, but there's no change/activity otherwise it just stays in that state.
This was working before, so I know this is a relatively new issue (at least since Feb, possibly sooner). I also know since it's working on desktop, there's nothing wrong with the setup per se -- but it's still failing for Android.
Any help or feedback here would be great, thank you!
Okay, after updating my Android phone (missed an update this morning) it seems to be fixed.
EDIT:
Turns out, it was due to the restart. So as a patch, restarting your mobile device will reset your Chrome and allow it to send correctly.
TL;DR:
When I have an emulator open, and I try to call the browser using Appium, I get an error saying that the browser isn't callable, even though there is a browser in the device. Not sure what it's called, so I can call it in Desired Capabilities.
Long story long:
I'm new to Appium so trying to get a basic emulator session going. I'm new to Java too, but I'm not using Java here and the Appium site video didn't require Java to get a basic session going, so this isn't a "your code is rubbish" Java issue. (Video link I watched: https://youtu.be/IOSUBda2-g4, though this didnt' call a browser on the device so wasn't a helpful guide for newbies like me).
On Win10, I installed Appium Desktop for Windows (current version 1.2.0 beta).
I have Android Studio installed (v2.3.3), and an image for a Pixel device.
I open Android Studio > Tools > Android > AVD Manager > Pixel API 25 (which is set up using Android 7.1.1 and API 25) and I start the emulator.
The emulator opens, and the first thing I see is "Photos has stopped Close app" and an X. Somewhat worrying but hey, I installed the image from AVD Manager so I got what I got.
If I then go to Appium Desktop (host 0.0.0.0, port 4723) and start the server (v1.6.5), I get the console.
I click Start New Session, and the settings screen comes up.
I am on the Automatic Server tab.
I go to Saved capabilities tab.
I have these settings saved:
{
"platformName": "Android",
"deviceName": "Android Emulator",
"browserName": "Browser",
"avd": "Pixel_API_25",
"platformVersion": "7.1.1",
"": ""
}
NOTE: The last empty entry is because the delete button on Appium for the Desired Capabilities has no effect in this version of Appium Desktop.
I click "Start session" in Appium Desktop.
Since the emulator is already started, I get error "An unknown server-side error occurred while processing the command. Original error: Could not find package com.android.browser on the device"
There is a very simple browser on the Pixel phone, but I can't invoke it because I don't know what it is called. There is no Chrome or Firefox installed by default. If I go on the device I can run a Google search in this basic browser, but I don't know what it is called to try to invoke it from Appium.
I'm trying to use the guidance in https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/caps.md but I'm lost, and trying stuff with no success.
QUESTION: What is the browser called so I can invoke it?
Why am I trying to do this?
I actually wanted to invoke a basic Calculator.apk that I have locally, but that didn't work either (it never started when I specified "app": "C:\android\Calculator.apk"), so I thought I should start with a basic browser session rather than APKs.
I tried the same as above with API 26 but that didn't work either.
I haven't solved the APK invoke issue, but that's likely another issue.
Any assistance with the DCs much appreciated.
Mike
So I am trying to setup Google Play Games Services in the Google Play Developer Console.
This worked for me yesterday.
Today however, when setting up another app, and trying to link an android app to the games services, I get this error:
An unexpected error occurred. Please try again later. (4800001)
I got this in:
Google Play Developer Console -> Games Services -> [game] -> Linked Apps -> STEP 2 Authorize your app.
This happens regardless which key I try, my release key, or my debug key.
I don't understand why this would be happening, as it was working yesterday, albeit for an app without real-time multi player. The app I am trying to setup now needs real-time multiplayer, but I'm not sure whether this difference is the cause of it. Maybe servers at google are down?
I get the error each time I try, regardless which browser I use, or which OS. I tried on Ubuntu Firefox and OSX Safari.
This was a temporary breakage in the Google Play Developer Console.
They fixed it today, by rolling back changes to the console, see:
https://github.com/playgameservices/android-basic-samples/issues/153#issuecomment-134749998
I opened https://console.developers.google.com/ page and successfully registered my app there while I was having same issue as you.
I can't find much documentation around this issue. All other running apps on my pebble have a connection to my phone, and work as expected. However, a Pebble.js application I'm currently working on simply displays Disconnected - run the pebble phone app.
I have noticed that in my Developer Settings that the Connection Manager is listed as Disconnected. Is this part of the problem? I see nothing in the logs.
For reference, the application is doing a simple ajax request and displaying the result.
This message is often caused by the JavaScript crashing on the phone (undefined reference, unknown function, etc) and so the watch thinks it is not running.
Some ideas to debug this:
Replace your code with one very simple console.log("hello world") statement and see if this works.
Look at the Logs (View Logs button in CloudPebble or pebble logs on the command line).
Very rarely, on Android, I have seen situation where the Pebble app is in a bad state where it cannot execute the JS for only one app. When this happens, you need to force-kill the Pebble app and relaunch it.
I have had the same experience.
I usually kill and restart the pebble app on my phone and then I also do refresh the browser. Sometimes you have to log out of and then log back into Cloudpebble.
I'm trying to connect to Windows Live ID using the Live SDK from this site: http://msdn.microsoft.com/en-us/library/live/hh243641.aspx
When I run this code in my emulator, I get the Live SignIn Button. When I click on it, it tries to connect to Windows Live, but always ends up with
"We're unable to complete your request
Windows Live ID is experiencing technical difficulties. Please try again later."
And this happens all the time - does it need some permission or sth like that?
Ok, this happened because I gave a wrong ClientId in the XAML code for the signIn Button.
If you use a Sign In Button, you have to provide the ClientId property along with the ID you got.