No runtime version available when ejecting bot runtime
See original GitHub issueDescribe the bug
When trying to eject the bot runtime, no runtime version is available to select. The runtime versions field is empty. Since the selection is not available, the runtime cannot be ejected, which blocks (amongst others) creating custom actions.
Version
The issue is producing in a nightly build version.
Browser
- Electron distribution
- Chrome
- Safari
- Firefox
- Edge
OS
- macOS
- Windows
- Ubuntu
To Reproduce
Steps to reproduce the behavior:
- Make a new bot based on the sample Echobot.
- Navigate to the Settings page and select Runtime Config.
- Toggle Use custom runtime in the Bot runtime settings field and select Get a new copy of the runtime code.
- The dialog box which appears has no runtime versions listed.
Expected behavior
There should be the option in the dialog box to select C# and click OK, after which the ejected runtime directory should show in the Runtime code location field.
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Robot Licensing Failed. There are no available runtime ...
Hi everyone, When I run any process by Schedule or manually, status is pending all the time. In the process information, you can...
Read more >The extension APIs in Bot Framework Composer
Runtime templates: extensions can provide a runtime template used when ejecting from Composer. Combining these endpoints, it's possible to ...
Read more >Could not load file or assembly System.Runtime, Version=4.1 ...
I updated my company's build server to VS 15.5 when it was released and triggered a rebuild and deployment (through our on-prem TFS)...
Read more >Upgrading Mule Runtime Engine(Versions 3.x to 3.n)
If there are no relevant changes between the Mule Runtime version in which ... to work properly (these would be found in the...
Read more >WALL-E - Wikipedia
WALL-E is a 2008 American computer-animated science fiction film produced by Pixar Animation Studios and released by Walt Disney Pictures. ... He is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in https://github.com/microsoft/BotFramework-Composer/pull/3479
Hi @tonyanziano, It seems like the electron load plugins folder error. I tested in local and found the plugins our nightly-build version loaded was previously. FYI. For example, the azure function plugin name was changed to @bfc/plugin-azure-functions-publish.
I try to build electron locally by
yarn dist:full
, but it fail to load plugins folder either. I try to runyarn start:electron
locally and find thepluginsDir
is[Composer folder]\Composer\packages\electron-server
, but the path need to be[Composer folder]\Composer\packages\electron-server\dist\win-unpacked\resources\app.asar.unpacked
.I am not sure how to debug in electron, could you help to take a look? Thanks!