React-native-windows: react-native run-windows on Playground app causes "Failed to deploy" error if not using admin prompt

[harinikmsft]

Open regular command prompt.

1. Follow all the steps in Getting Started guide
2. Run yarn build at the root of the repo
3. Navigate to the playground folder and run react-native run-windows

Expected Behavior

Playground project compiles, metro bundler is started and the app launches successfully

Actual Behavior

Error in the command window at the last step before installing/deployment of the app:
Failed to deploy: Fail to check the installed app, maybe developer mode is off on Windows

Developer mode is ON in Windows settings. The only way to get around this was to retry with admin prompt and it worked.

[chrisglein]

@harinikmsft You've updated the readme (thank you). I assume you want this issue to track removing the elevation requirement?

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 14 days of this comment.

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 14 days of this comment.

[liudonghua123]

I have the same issue, after I run it in a admin cmd, then it works, so the message should be more clear about this. Now the current error message is misunderstand.

[Lechus]

same error, running from VS code terminal.
The error message should be clear why.
× Failed to deploy: Fail to check the installed app, maybe developer mode is off on Windows

[linkstrifer]

Running the project as an Administrator fixed the problem for me

[parksj10]

Getting the same failure, except with the following error:

Add-AppxPackage : Deployment failed with HRESULT: 0x80073D1F, Remote drives are not supported

This is happening because I'm developing in MacOS and testing on a Windows VM (Parallels), with the Mac repo access happening through a network drive (Z:).

Any suggestions on workarounds/fixes? I think this might become a common issue for Mac developers trying to develop windows apps

[chrisglein]

@parksj10 I don't think this issue from last October really captures your scenario. Can you please log a new issue, in particular following the template steps to capture your environment so we can dig into the interaction with your macOS config?