Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Mac installers are not arch-aware
See original GitHub issueRight now the installers for x64 and ARM64 will install to the same location and overwrite the other one. This results in an unusable product for both architectures.
The correct behavior is to install x64 to an x64 subdirectory when on an Apple Si machine. The apphost should decide which arch to load.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >macOS installation guide
Previous versions of macOS did not need the modification ... Step-by-step Guide to install Archiware P5 specifically on. macOS Catalina 10.15.
Read more >macOS Could Not Be Installed on Your Computer? Read ...
Part 1: What Are the Common Cause of macOS Couldn't Be Installed on Your Computer Error? · The installer files are corrupted ·...
Read more >How to reinstall macOS from macOS Recovery — Apple Support
Learn how to reinstall the operating system on your Mac, using macOS Recovery. To learn more about this topic, visit the follow article:...
Read more >What to try if you can't install or activate Office for Mac
If you're having trouble installing or activating Office for Mac, you can find self-help troubleshooting steps for common issues.
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 Free
Top 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
Found a way to use .net6.0 and .net5.0 together with setup below.
In Rider in Launch Profile add this override env before each start\debug project.
DOTNET_ROOT=/usr/local/share/dotnet/x64As far as I know,
dotnet runshould change this env itself, depending on the version of the dotnet in project, and the RID. But in version6.0.0-rc.2.21428.1this doesn’t work yet.This was fixed by https://github.com/dotnet/installer/pull/11813 (among other runtime/arcade PRs)