Logging in via the browser does not log in

[fkeet]

Describe the bug
From the main Excilence window the login with pathofexile.com button opens a browser window, but authorizing in the browser window does not authorize the app.

To Reproduce
1 Open Exilence Next
2 Click 'Log in with pathofexile.com' button with 'PC' selected
3 In browser window click 'Authorize'
4 Nothing happens

Expected behavior
I expect Exilence Next to now continue with authorization

Version
v0.5.0

Additional context
Using Firefox 90.0.2

[sbsrnt]

What is your OS? Linux & MacOS are not supported yet

Edit: make sure you have popouts enabled on poe website

Edit 2: To those that still have an issue - see #700 (comment)

[fkeet]

I assumed so, unfortunately I'm using Windows.

…

On Sun, Aug 1, 2021 at 12:00 PM Sebastian Krzyżanowski < ***@***.***> wrote: Wthat is your OS? Linux & MacOS are not supported yet — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#700 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN5SBXLZ4AJDYLITN2N2ALT2WKTPANCNFSM5BKJX4XQ> .

[sbsrnt]

Seems like this is affecting few users and another thing that comes to my mind is maybe your OS / browser / antivirus are blocking custom protocols (in our case it's exilence)

The last thing that comes to my mind is that we probably didn't register custom protocols properly for windows users which may be covered in #692

[fkeet]

Thank you, I'll check on that.

…

On Tue, Aug 3, 2021 at 5:48 AM Sebastian Krzyżanowski < ***@***.***> wrote: Seems like this is affecting few users and another thing that comes to my mind is maybe your OS / browser / antivirus are blocking custom protocols <https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler/Web-based_protocol_handlers> (in our case it's exilence) The last thing that comes to my mind is that we probably didn't register custom protocols properly for windows users which may be covered in #692 <#692> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#700 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN5SBSCQ2LC7UBC4I2KVYTT27QTVANCNFSM5BKJX4XQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[oplosthee]

What is your OS? Linux & MacOS are not supported yet

Edit: make sure you have popouts enabled on poe website

Is Linux support something that is planned for the future? I remember having used Exilence during the previous league locally, which seemed to work fine, but like you mentioned the API authentication doesn't work at the moment.

Or if there are instructions available on how to set this up on Linux, that would be great too! Thanks for your work!

[elmo667]

Happens on Linux too, used to work fine in previous versions (will have to revert for now).

The problem is that Exilence Next does not register the next.exilence.app protocol with the OS/Firefox so the redirect to the local exilence fails. If we can find out where that is done in the code for windows, it might be possible to self-add the protocol handler to the MIME types. Just registering the binary as the handler doesnt seem to work. Firefox is not cooperating.

Alternatively: would it be possible to re-add the old manual POESESSIONID process as a fallback until unix support is sorted out?

[sbsrnt]

#692

[elmo667]

thanks for this! I pulled the master repo after the PR got merged. I figured out the manual steps required at the moment to make it work:

Create ~/.local/share/applications/ExilenceNext.desktop with:

[Desktop Entry]
Name=Exilence Next
Exec=<ABSOLUTE PATH TO ExilenceNext>/ExilenceNextApp/dist/appimage %u
Icon=<ABSOLUTE PATH TO ExilenceNext>/ExilenceNextApp/public/icon.ico
Terminal=false
Type=Application
MimeType=x-scheme-handler/exilence;

Run:
update-mime-database ~/.local/share/mime
update-desktop-database ~/.local/share/applications

[sbsrnt]

Issue should be fixed with 0.5.4 but feel free to get the latest here https://github.com/viktorgullmark/exilence-next/releases

For those that want to have the issue fixed before release that may potentially fix the issue and are on windows

1. Type in windows search regedit
   

2. Navigate to this path Computer\HKEY_CLASSES_ROOT\exilence
   

3. Select exilence
   

4. Double click on
   

5. add value URL:exilence and click OK
   

6. right click anywhere in the empty space and create a new string
   

7. type URL Protocol
   

8. If you try to authorize and get 401 - relaunch Exilence

[sbsrnt]

Most likely fixed in 0.5.4