Open Viktorh89 opened 4 weeks ago
For some reason azureLogicAppsStandard.projectSubpath is not set on project creation. You need to set it to reference the LogiApp folder. Then you can edit the workflow.
Forget the previous response @Viktorh89 most likely is that you have not opened the workspace but just the folder. At least for me when I happen to open the folder I get the error if I open with the workspace file it works as expected.
We are hitting this same error. It works only on the machine that created the Workspace. We have the code checked in and if another developer clones the project and try to open a workflow in the designer, it states that there is an error in determining the root. Something must be getting hardcoded to a path somewhere, but we cannot figure it out. If anyone has a fix, please let us know.
@mikeholdorf after your post I did a test to see if I could sort it out with no success. I'm using the latest extension 4.57.7 After recreating the workspace file (it was in .gitignore) and changing the paths in solution file that was created I was able to open the designer. When it comes to having a function in the same project The metadata files are created when I build the function. That said I'm not able to have the environment to use the "Call a local function" action. I get "Failed to retrieve dynamic inputs", see output below.
Everything is working for me and I can bring up the workspace and all works fine with the Designer. The other developers on the project are cloning the repo and when they try and bring up the Designer, it just states Error determining the Root. So the good old saying...works on my machine. We have not been able to figure out a resolution. It looks like the workspace file has some hardcoded paths using my username and it also appears that not all of the .vscode files were created properly. Works different on a Mac vs a Windows machine, so is a big concern for multiple developer projects right now.
Agree with @mikeholdorf, to clarify on my test. On the machine where I created the Logic App it works fine in the machine where I have cloned the repo it does not.
Also experiencing this still, if i redo it manually l can reach designer, but reaching the local function seems to never work
@mikeholdorf @Viktorh89 I've been able to get it working. The problem for me was that Logic Apps is dependent on settings that are in local.settings.json
and that is included in different ignore files. When I changed so local.settings.json
is included in the repo it works.
If you want to test I have created a simple repo to be able to test.
def01.code-workspace
local.settings.json
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "UseDevelopmentStorage=true",
"WORKFLOWS_SUBSCRIPTION_ID": "",
"FUNCTIONS_WORKER_RUNTIME": "node",
"APP_KIND": "workflowapp",
"AzureWebJobsFeatureFlags": "EnableMultiLanguageWorker"
}
}```
@skastberg yes, just did the same today - seems to be working, but I have to keep rebuilding the function because the lib folder keeps disapearing, maybe thats by design or im missing something, and not sure how i feel about needing to have the local.setting commited
I'm logging an issue about local.setting, there are no secrets in mine but as we're used to have them in gitignore not ideal. Agree, a bit annoying building and think it is by design. You can see in the csproj file steps to do that. I assume it is the way to keep the description files under lib current.
I was able to pull down your repo and get to the designer with no problem. We will test this with our internal projects and make sure this will work. Thanks.
Describe the Bug with repro steps
Start new LA workspace project
Select with new LA with "custom code"
Try to view designer
What type of Logic App Is this happening in?
Standard VSCODE
Which operating system are you using?
Windows
Are you using new designer or old designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
VScode
Additional context
No response