[Friendica] Cannot login on some instances #85

rokosun commented 2022年05月23日 10:29:04 +02:00

I am not able to login to my friendica account on https://social.trom.tf. But I was able to successfully login to an older unused account I had on https://venera.social, so it works on some instances. These instances might be running different versions of friendica and that could play a role. Not sure if this could have an effect, but I also have 2FA enabled on my account on social.trom.tf.

I am not able to login to my friendica account on https://social.trom.tf. But I was able to successfully login to an older unused account I had on https://venera.social, so it works on some instances. These instances might be running different versions of friendica and that could play a role. Not sure if this could have an effect, but I also have 2FA enabled on my account on social.trom.tf.

rokosun commented 2022年05月23日 10:37:23 +02:00

This was tested on beta release v12 - https://toot.fedilab.app/@apps/108346755623242765

This was tested on beta release v12 - https://toot.fedilab.app/@apps/108346755623242765

foss- commented 2022年05月30日 20:51:18 +02:00

squeet.me also afffected
persisting with Fedilab b15

squeet.me also afffected persisting with Fedilab b15

tom79 commented 2022年05月31日 17:16:19 +02:00

Fixed for last release

Fixed for last release

foss- commented 2022年05月31日 20:49:20 +02:00

verified in Fedilab b16, thank you.

verified in Fedilab b16, thank you.

rokosun commented 2022年06月01日 05:44:19 +02:00

I'm still not able to login to my account on https://social.trom.tf

I'm still not able to login to my account on https://social.trom.tf

tom79 commented 2022年06月01日 10:55:19 +02:00

This is Friendica, version 2022.02 that is running at the web location https://social.trom.tf. The database version is 1449/1449, the post update version is 1427/1427.

But does this instance support the Mastodon API?

```text This is Friendica, version 2022.02 that is running at the web location https://social.trom.tf. The database version is 1449/1449, the post update version is 1427/1427. ```` But does this instance support the Mastodon API?

foss- commented 2022年06月06日 22:13:33 +02:00

Just tried and social.trom.tf was accepted as expected. Is that not the case for you @futureisfoss?

Just tried and social.trom.tf was accepted as expected. Is that not the case for you @futureisfoss?

rokosun commented 2022年06月06日 22:22:13 +02:00

Fedilab brings me to my instance and I'm able to login there on the webpage, but after I click to authorize fedilab then it just closes that webpage and nothing happens.

Fedilab brings me to my instance and I'm able to login there on the webpage, but after I click to authorize fedilab then it just closes that webpage and nothing happens.

rokosun commented 2022年06月06日 22:31:24 +02:00

My instance admin (of social.trom.tf) said he'll be updating the friendica instance soon, so I'll test this again once that update is done.

My instance admin (of social.trom.tf) said he'll be updating the friendica instance soon, so I'll test this again once that update is done.

foss- commented 2022年06月07日 10:32:53 +02:00

In my test fedilab crashed on login on social.trom.tf. Lets wait for that instance to be updated:
This is Friendica, version 2022.02 that is running at the web location https://social.trom.tf. The database version is 1449/1449, the post update version is 1427/1427.

Not using 2FA for the social.trom.tf account in this test.

In my test fedilab crashed on login on social.trom.tf. Lets wait for that instance to be updated: This is Friendica, version 2022.02 that is running at the web location https://social.trom.tf. The database version is 1449/1449, the post update version is 1427/1427. Not using 2FA for the social.trom.tf account in this test.

rokosun commented 2022年06月07日 19:43:31 +02:00

Not using 2FA for the social.trom.tf account in this test.

So it crashes regardless of whether you have 2FA enabled or not.

> Not using 2FA for the social.trom.tf account in this test. So it crashes regardless of whether you have 2FA enabled or not.

foss- commented 2022年06月08日 00:09:19 +02:00

I would conclude so adding your test result, however I personally have only tested a single non-2fa account.

I would conclude so adding your test result, however I personally have only tested a single non-2fa account.

rokosun commented 2022年06月08日 07:23:15 +02:00

My instance admin updated the friendica instance social.trom.tf, so I tested it again and fedilab still doesn't work with it. This is the current stats:

This is Friendica, version 2022.03 that is running at the web location https://social.trom.tf. The database version is 1452/1452, the post update version is 1452/1427.

My instance admin updated the friendica instance social.trom.tf, so I tested it again and fedilab still doesn't work with it. This is the current stats: > This is Friendica, version 2022.03 that is running at the web location https://social.trom.tf. The database version is 1452/1452, the post update version is 1452/1427.

rokosun commented 2022年06月08日 07:36:15 +02:00

I checked the stats for venera.social which worked fine for me in fedilab:

This is Friendica, version 2022.05-rc that is running at the web location https://venera.social. The database version is 1468/1468, the post update version is 1452/1452.

I think the -rc at the end means release candidate, so they must be running a non-stable release.

If you look at friendica's git repo the latest stable release is version 2022.03 which is what social.trom.tf is running - https://github.com/friendica/friendica/releases

I checked the stats for venera.social which worked fine for me in fedilab: > This is Friendica, version 2022.05-rc that is running at the web location https://venera.social. The database version is 1468/1468, the post update version is 1452/1452. I think the `-rc` at the end means release candidate, so they must be running a non-stable release. If you look at friendica's git repo the latest stable release is version 2022.03 which is what social.trom.tf is running - https://github.com/friendica/friendica/releases

rokosun commented 2022年06月12日 11:21:24 +02:00

A new friendica stable release is out - https://github.com/friendica/friendica/releases/tag/2022.06

And this was one of the highlighted changes:

The Mastodon compatible API was improved, you now should be able to use most Mastodon clients with your Friendica account.

So once my instance admin updates https://social.trom.tf to this latest version I will test fedilab support again :)

A new friendica stable release is out - https://github.com/friendica/friendica/releases/tag/2022.06 And this was one of the highlighted changes: > The Mastodon compatible API was improved, you now should be able to use most Mastodon clients with your Friendica account. So once my instance admin updates https://social.trom.tf to this latest version I will test fedilab support again :)

rokosun commented 2022年06月17日 05:33:24 +02:00

So my instance admin updated friendica to the latest stable version, but I'm still not able to login to https://social.trom.tf from fedilab. This is the current server stats:

This is Friendica, version 2022.06 that is running at the web location https://social.trom.tf. The database version is 1469/1469, the post update version is 1452/1452.

And this is the crash report I got when I tried to login and the app crashed - https://bin.disroot.org/?a09dec57a8a15e06#GbciY55D3SgDNMbeqYzZbnr2Gvn8hwbH1xBfS2MDwRPa

So my instance admin updated friendica to the latest stable version, but I'm still not able to login to https://social.trom.tf from fedilab. This is the current server stats: > This is Friendica, version 2022.06 that is running at the web location https://social.trom.tf. The database version is 1469/1469, the post update version is 1452/1452. And this is the crash report I got when I tried to login and the app crashed - https://bin.disroot.org/?a09dec57a8a15e06#GbciY55D3SgDNMbeqYzZbnr2Gvn8hwbH1xBfS2MDwRPa

nolan commented 2022年07月04日 16:26:26 +02:00

Interestingly, I've never gotten Fedilab 3+ authenticating with venera.social, the instance folks here say works. Always gets to the authorization screen, then crashes. Previously it let me email a crash report, but now it just throws up an error and won't let me go further. venera.social runs 2022.06, or whatever the latest release with improved Mastodon API support is.

Here is the most recent crash report I sent:

INSTALLATION_ID=65c7f87e-6fa4-4feb-b838-777465eeb831
APP_VERSION_CODE=391
ANDROID_VERSION=12
PHONE_MODEL=Pixel 4a (5G)
TOTAL_MEM_SIZE=117153181696
AVAILABLE_MEM_SIZE=51184746496
USER_CRASH_DATE=2022年06月29日T19:57:02.708-05:00
STACK_TRACE=java.lang.NullPointerException: Attempt to read from field 'java.lang.String app.fedilab.android.client.entities.api.Account.id' on a null object reference
at app.fedilab.android.activities.WebviewConnectActivity2ドル.lambda$shouldOverrideUrlLoading1ドル$app-fedilab-android-activities-WebviewConnectActivity2ドル(WebviewConnectActivity.java:218)
at app.fedilab.android.activities.WebviewConnectActivity2ドル$$ExternalSyntheticLambda1.onChanged(Unknown Source:6)
at androidx.lifecycle.LiveData.considerNotify(LiveData.java:133)
at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:151)
at androidx.lifecycle.LiveData.setValue(LiveData.java:309)
at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
at app.fedilab.android.viewmodel.mastodon.AccountsVM.lambda$getConnectedAccount0ドル$app-fedilab-android-viewmodel-mastodon-AccountsVM(AccountsVM.java:130)
at app.fedilab.android.viewmodel.mastodon.AccountsVM$$ExternalSyntheticLambda37.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7870)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

IS_SILENT=false
REPORT_ID=557c26d1-5c0b-4d37-86a5-41504067add6
USER_COMMENT=Attempting to sign into venera.social, Friendica. Thanks!
USER_EMAIL=

Interestingly, I've never gotten Fedilab 3+ authenticating with venera.social, the instance folks here say works. Always gets to the authorization screen, then crashes. Previously it let me email a crash report, but now it just throws up an error and won't let me go further. venera.social runs 2022.06, or whatever the latest release with improved Mastodon API support is. Here is the most recent crash report I sent: INSTALLATION_ID=65c7f87e-6fa4-4feb-b838-777465eeb831 APP_VERSION_CODE=391 ANDROID_VERSION=12 PHONE_MODEL=Pixel 4a (5G) TOTAL_MEM_SIZE=117153181696 AVAILABLE_MEM_SIZE=51184746496 USER_CRASH_DATE=2022年06月29日T19:57:02.708-05:00 STACK_TRACE=java.lang.NullPointerException: Attempt to read from field 'java.lang.String app.fedilab.android.client.entities.api.Account.id' on a null object reference at app.fedilab.android.activities.WebviewConnectActivity2ドル.lambda$shouldOverrideUrlLoading1ドル$app-fedilab-android-activities-WebviewConnectActivity2ドル(WebviewConnectActivity.java:218) at app.fedilab.android.activities.WebviewConnectActivity2ドル$$ExternalSyntheticLambda1.onChanged(Unknown Source:6) at androidx.lifecycle.LiveData.considerNotify(LiveData.java:133) at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:151) at androidx.lifecycle.LiveData.setValue(LiveData.java:309) at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50) at app.fedilab.android.viewmodel.mastodon.AccountsVM.lambda$getConnectedAccount0ドル$app-fedilab-android-viewmodel-mastodon-AccountsVM(AccountsVM.java:130) at app.fedilab.android.viewmodel.mastodon.AccountsVM$$ExternalSyntheticLambda37.run(Unknown Source:4) at android.os.Handler.handleCallback(Handler.java:938) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7870) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) IS_SILENT=false REPORT_ID=557c26d1-5c0b-4d37-86a5-41504067add6 USER_COMMENT=Attempting to sign into venera.social, Friendica. Thanks! USER_EMAIL=

rokosun commented 2022年07月05日 16:26:21 +02:00

Sorry for the late update, but my Friendica instance https://social.trom.tf now works with fedilab! 😀

I was a bit busy for a couple of days so I couldn't do much testing, so I don't know exactly which release fixed this login issue, all I know is that when I updated to v3.0.5 and tried logging in, it worked. You can also read my post here - https://social.trom.tf/display/dbc8dc44-1962-c1cf-cbe2-989533827753

Sorry for the late update, but my Friendica instance https://social.trom.tf now works with fedilab! 😀 I was a bit busy for a couple of days so I couldn't do much testing, so I don't know exactly which release fixed this login issue, all I know is that when I updated to v3.0.5 and tried logging in, it worked. You can also read my post here - https://social.trom.tf/display/dbc8dc44-1962-c1cf-cbe2-989533827753

nolan commented 2022年07月05日 17:07:35 +02:00

Rereading my previous comment, I just want to be clear that I've tried accessing my venera.social account with 3.0.5 and it still doesn't work. I just included an older crash report because for whatever reason the new release doesn't give me the opportunity to send a new one.

Thanks.

Rereading my previous comment, I just want to be clear that I've tried accessing my venera.social account with 3.0.5 and it still doesn't work. I just included an older crash report because for whatever reason the new release doesn't give me the opportunity to send a new one. Thanks.

nolan commented 2022年07月26日 19:02:44 +02:00

Made a bit of progress on this. Turns out I had pending notifications, and the login UI attempts to access local storage to set them. This isn't enabled by default in WebViews.

#282 addresses this, but I still can't log into venera.social. I don't see any console errors in the logs, so I'm guessing something somewhere isn't getting what it needs to connect.

Hoping others have some thoughts on this. Fedilab seems to be the most featureful client with background push notifications but I don't know why some folks can log into their instances and I can't.

Thanks.

Made a bit of progress on this. Turns out I had pending notifications, and the login UI attempts to access local storage to set them. This isn't enabled by default in WebViews. #282 addresses this, but I still can't log into venera.social. I don't see any console errors in the logs, so I'm guessing something somewhere isn't getting what it needs to connect. Hoping others have some thoughts on this. Fedilab seems to be the most featureful client with background push notifications but I don't know why some folks can log into their instances and I can't. Thanks.

tom79 commented 2022年07月26日 19:14:44 +02:00

Did you try with external browser? In login page open top menu and select custom tabs.

Did you try with external browser? In login page open top menu and select custom tabs.

nolan commented 2022年07月26日 20:07:11 +02:00

Wow, I totally didn't realize that's what that option did. :) Maybe rename it to "Use external browser" or similar? In any case, now I have an actual error that I'm working to debug further.

Wow, I totally didn't realize that's what that option did. :) Maybe rename it to "Use external browser" or similar? In any case, now I have an actual error that I'm working to debug further.

nolan commented 2022年07月26日 21:43:04 +02:00

I've spent a few hours debugging why this is failing for me and I have a theory, but I don't have the bandwidth to try for a fix right now.

I'm a blind TalkBack user, and the instance popup presents some accessibility challenges. In particular, I try typing "venera.social" and as soon as I type "ven", a bunch of instance names pop up with no ability for me to keep typing. I guess it's possible venera.social is in the lsit but it'd just be quicker for me to type it. I do manage to back out and get another "e" in but then nothing I do brings the keyboard back up. Nor can I get the instance popup to go away.

My workaround for this is to use the built-in Braille IME. This basically takes over the entire screen, so your popup can't appear and I can enter "venera.social" completely. unfortunately, I also flip the phone into lanscape mode to enter the needed characters. It looks like the instance hostname at least is a static on the LoginActivity class.

When Fedilab tries to get a token, it attempts to look up a hostname for null. But I've definitely entered an instance, so that shouldn't be happening.

I suspect flipping the phone into landscape mode, or maybe flipping it back, is destroying the activity containing the statics, one of which contains the hostname. So the token->account conversion loses its state.

I'd like to kindly request that the instance autocomplete popup be either made less aggressive so I can back out of it if I want, or that it be disabled entirely until its accessibility issues can be worked out. That, or we need to figure out how to move at least the instance hostname into the intent. Or, at least, serialize/restore it when the activity is destroyed and recreated.

Thanks.

I've spent a few hours debugging why this is failing for me and I have a theory, but I don't have the bandwidth to try for a fix right now. I'm a blind TalkBack user, and the instance popup presents some accessibility challenges. In particular, I try typing "venera.social" and as soon as I type "ven", a bunch of instance names pop up with no ability for me to keep typing. I guess it's possible venera.social is in the lsit but it'd just be quicker for me to type it. I do manage to back out and get another "e" in but then nothing I do brings the keyboard back up. Nor can I get the instance popup to go away. My workaround for this is to use the built-in Braille IME. This basically takes over the entire screen, so your popup can't appear and I can enter "venera.social" completely. unfortunately, I also flip the phone into lanscape mode to enter the needed characters. It looks like the instance hostname at least is a static on the LoginActivity class. When Fedilab tries to get a token, it attempts to look up a hostname for null. But I've definitely entered an instance, so that shouldn't be happening. I suspect flipping the phone into landscape mode, or maybe flipping it back, is destroying the activity containing the statics, one of which contains the hostname. So the token->account conversion loses its state. I'd like to kindly request that the instance autocomplete popup be either made less aggressive so I can back out of it if I want, or that it be disabled entirely until its accessibility issues can be worked out. That, or we need to figure out how to move at least the instance hostname into the intent. Or, at least, serialize/restore it when the activity is destroyed and recreated. Thanks.

nolan commented 2022年07月26日 22:26:03 +02:00

Update: instance input a11y is resolved by #284, but somehow I'm still getting a null hostname. Out of ideas at this point, other than to think those statics are really sus and probably shouldn't be relied upon.

Update: instance input a11y is resolved by #284, but somehow I'm still getting a null hostname. Out of ideas at this point, other than to think those statics are really sus and probably shouldn't be relied upon.

ildar commented 2022年09月24日 22:41:48 +02:00

got this too with fosstodon.org instance.
logcat whitnesses Unable to resolve host "null".
Please fix.

got this too with `fosstodon.org` instance. logcat whitnesses Unable to resolve host "null". Please fix.

ildar commented 2022年09月24日 23:03:37 +02:00

found a (maybe) workaround:
On the instance Preferences -> Development -> New
create a random token.
Helped me.

found a (maybe) workaround: On the instance Preferences -> Development -> New create a random token. Helped me.

HurricaneWeasel commented 2026年01月27日 20:22:17 +01:00

Hi @nolan and @ildar, is the issue resolved for you? If so, I would like to close this issue. Thank you for some feedback.

Hi @nolan and @ildar, is the issue resolved for you? If so, I would like to close this issue. Thank you for some feedback.

HurricaneWeasel commented 2026年03月13日 21:01:55 +01:00

Closing for now. Please open a new issue, if there are problems again. Thank you.

Closing for now. Please open a new issue, if there are problems again. Thank you.