Skip to content
This repository has been archived by the owner on Feb 19, 2024. It is now read-only.

Lock file location can not be read from process when Lol run in Admin mode #25

Open
timhaines opened this issue Oct 12, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@timhaines
Copy link

Describe the bug
If you start LOL via run as administrator, getting the MainModule of the process raises an exception. It turns out Riot has a page telling users to run in administrator mode. Our first beta tester was doing this (on advice of a coach).

If there's another way to reliably get the current folder to read the lockfile from (I tried it hardcoded), then the LCU API works correctly.

Hardcoding the lockfile path isn't a good solution though, as the user may have installed Lol in a different location.

@timhaines timhaines added the bug Something isn't working label Oct 12, 2022
@bryanhitc
Copy link
Owner

What exception is raised? Does running the app that uses LCU Sharp as admin fix the problem?

I don't maintain this project, but feel free to submit a PR to handle the exception gracefully.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants