Mac OS X version of 4.15.1 is missing

[taoari]

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.

Version

What version of the Emulator are you using.

Describe the bug

Give a clear and concise description of what the bug is.

No mac os x version for 4.15.1: https://github.com/microsoft/BotFramework-Emulator/releases/tag/v4.15.1.

To Reproduce

Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

Give a clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[bug]

[rido-min]

Hi @taoari

Thanks for reporting this issue. We are working to get a signed/notarized installer for Mac, although we don't have any ETA yet.

In the meantime, you can download the previous version https://github.com/microsoft/BotFramework-Emulator/releases/tag/v4.14.1, and if you want to try the latest you can get unsigned bits from the artifacts produced in this run (Keep in mind you will need to configure your MacOS to enable installs from developers)

[taoari]

@rido-min Thank you, This one works!

[sevron-gil]

Bumping this one as well if there is any movment for the notarized installer. the artifact seems to have expired!

[alexrecuenco]

Where can we subscribe to an issue to find out when it gets resolved?

[ter24]

Any assistance on this would be appreciated. We're mostly a MacOS shop and the working version still uses ngrok, which I believe is no longer open source.

[rido-min]

hi @ter24, apologies for the delays here.

As we dont have any ETA to produce the signed MacOS installer, I'd suggest to use the unsigned bits from this run.

You will have to enable Developer Installs in your mac.

I'd love to understand what's your use case requiring NGrok, if you have time you can reach out to me: rmpablos at msft dot com and we can take this offline, or setup a 30 mins call if you are available.

[alexrecuenco]

I'd love to understand what's your use case requiring NGrok, if you have time you can reach out to me: rmpablos at msft dot com and we can take this offline, or setup a 30 mins call if you are available.

In general. The single sign on tokens with the oAuthPrompt doesn't work through the bot emulator without ngrok or something like it.

[rido-min]

have you tried with webchat? you can use devtunnels to configure your ABS instance to reach out your localhost, so no need to use the emulator.

[alexrecuenco]

have you tried with webchat? you can use devtunnels to configure your ABS instance to reach out your localhost, so no need to use the emulator.

How do you make a webchat that connects to localhost:8080, for example?

And I always had the impression the Emulator gives more feedback, since it givws you trace activities and integrates well with debuggers

[ter24]

Hi, thanks so much for the responses. I'm very new to the Bot Framework, so my answer may be a bit off but essentially:

• I am using the Bot Framework Emulator for local testing.
• I am using the web Chat for remote testing.
• My web service gets deployed as a container within my AWS infrastructure.
• Ultimately, I connect to it using MS Teams for right now.

This approach works fine. For local development, I was hoping to use containers (either Compose or Composer+DevContainers, but ran into issues with the emulator. To be fair I didn't put a lot of effort into it. For remote, I'm fine sticking with the web chat/Teams approach.

Thanks again for the response, still learning the framework and truly appreciate it!

[rido-min]

local testing has some limitations, especially when getting into OAuth flows, since it requires the EntraID configuration to be able to interact with the token service.

There is a way to do local development AND use remote clients suchs as Teams or WebChat, the only thing you need to do is configure the EndpointURL to point your devtunnel.

Whatever is in your localhost should not matter, so you can still use a container locally, or run the web service in your box, as long the port is exposed to devtunnels.

[rido-min]

How do you make a webchat that connects to localhost:8080, for example?

run devtunnel in your host, and configure ABS endpoint to use the URL provided by devtunnel.

Yes, the trace activities are handy, but if you can debug you can always inspect the incoming/outgoing messages from your debugger.

[ter24]

Oh perfect, I'll set this up then! I'm not using OAuth flows right now, so we're okay there.

[alexrecuenco]

if I may, the issue with devtunnels on a registered app —and why the emulator can be better— is that you basically require to open a new bot per developer and to register them.

It is also quite cumbersome to try multiple bots at the same time, or to try multi bot interactions where they interact with each other... All of the sudden you need to register a NxM number of bots where M is your number of developers. It gets more cumbersome very quickly and it is a need that the Emulator fills perfectly well.

Also, the botframework as an open source tool doesn't actually require any Microsoft registration to work. I've used it before within infrastructure that contains custom adapter and authentication that has nothing to do with Microsoft's infrastructure.

Having said that, I understand if it isn't the company priority to work on the Bot Framework Emulator for whichever reason, but all I am saying is that it would be greatly appreciated if there was an issue we could subscribe to get updates on when it becomes a bigger priority.

If we could help to move the needle as well in any other way, I would appreciate some guidance in how to contribute to that.