Sharesheet link: No auth method found!

[WinstonSmith73]

I set up an account for my wife on my self-hosted Linkwarden instance. I can log her in through LinkDroid (or Brave) but when I try to save a link via sharing from Brave I get "No auth method found!" error.

Works fine for me in my account on my phone, from Brave.

I've deleted LinkDroid cache & storage, reinstalled it, and restarted the server.

I can save links in LinkDroid by pasting them in via gBoard.

Android 14
CalyxOS 5.12.0
Pixel 6

[Dacid99]

Thats odd, have you set up the access token in LinkDroid?
Alternatively it's sufficient to be logged in via the Linkdroid app so there is a valid cookie.
What app version are you on?

[WinstonSmith73]

v1.4.0. No access token, but successfully logged in via LinkDroid. Didn't see an option to get an access token in her LW account.

[Dacid99]

Are you logged in when reopening the app? Or do you have to manually log in every time?
I thought there should be accesstokens available for all accounts.
If you get the warning 'no auth method found' that means the app could find neither a token (not set in your case) nor a cookie.

[Dacid99]

Did this also happen on an earlier version?

[WinstonSmith73]

Yes, logged-in when reopening. Don't have to login every time. Tried reverting to 1.3.0 but same result.

This is a pretty new LW server so not much history of use with LD.

[Dacid99]

Ok thats odd. It cant be the servers fault. It works on your own phone which is also android 14, so it cant be that either.
Does this also happen when sharing from another browser (i test with firefox) ?

[WinstonSmith73]

I just tried it with Fennec (Firefox) and it gave the same error :(

[WinstonSmith73]

I tried making a new account for her, with the same result. Then I generated an access token from desktop, entered it, and it works now! Not sure why it won't work via share without the token but works just fine otherwise.

Let me know if you want to help debug any further.

[Dacid99]

Ok it's very good that you found a solution 👍 .

There has to be something going wrong with the cookies in the app storage.

The next versions of the app will bring some improved logging in that area so we may be able to get a better grip of the problem then.