[QUESTION] Could not access Provider
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, node.js, playwright, powershell
- Domain
- authentication, devtools, testing-qa
Research direction
Start with the samples/basicgallery PowerShell command, config.json, and bin/Debug/PowerAppsTestEngine/config.dev.json, then inspect the logs referenced by the critical error. Done means the provider can be accessed successfully or the missing authentication or configuration requirement is documented.
Written by the indexing model from the issue text.
Description
Does this question already exist in our backlog?
- I have checked and confirm this is a new question.
What is your question?
I believe I have all the requirements are installed in VS Code. node.js installed, playwright extension
In PowerApps-TestEngine\bin\Debug\PowerAppsTestEngine I have made environment and tenant are correct in config.dev.json
in current project samples folder i.e. ..\samples\basicgallery
I have also a config.json with same environmentID, tenantID and user1email set to correct email
When I run the powershell script in that samples folder I get the following
dotnet PowerAppsTestEngine.dll -u "storagestate" --provider "canvas" -a "none" -i "$currentDirectory\testPlan.fx.yaml" -t $tenantId -e $environmentId
[Critical Error] Could not access Provider. For more details, check the logs.
I never see an authentication window but not sure how to go further. Can you help guide as unclear what I am missing?
What component are you experiencing the issue with?
None
What pac version are you using?
Microsoft PowerPlatform CLI Version: 1.48.2+g9bed644 (.NET Framework 4.8.9310.0)
- Dominant language
- C#
- Stars
- 150
- Forks
- 55
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PowerApps-TestEngine
-
new
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
new
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
new
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/PowerApps-TestEngine
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·