| 29 Mar 2024 |
 josce | It's playstore installed, and playstore doesn't mention a newer one | 21:07:51 |
| josce | I tried another server, same result but slightly slower the first time. | 21:08:23 |
| josce | So sequence is: click "login with browser", there's this looping arc of circle for a frac of a sec, then "failed to auth" in red in the same tusky screen | 21:08:58 |
| josce | not given a chance to enter credentials | 21:09:06 |
| josce | Just tried mastodon.social, there I reach credential stage! | 21:09:42 |
| josce | same with mas.to, here I tried "login w tusky" | 21:10:11 |
| josce | but my instances at gougere, and also scicomm.xyz and mathstodon.xyz don't | 21:10:48 |
| josce | seems not correlated w version 4.2.7 or 4.2.8... | 21:12:04 |
| josce | oh, now scicomm.xyz woirks with login w Tusky.... | 21:12:58 |
| josce | Right, so scicomm.xyz works again now | 21:15:50 |
| josce | (I hadn't told you I was multiaccounting and all accounts had stopped in tusky) | 21:16:13 |
| josce | So maybe there's sthg with 4.2.7? scicomm is the 4.2.8 one among the 3. | 21:16:38 |
| josce | Well well... I'm now on credential page with gougere. | 21:17:57 |
| josce | within tusky... | 21:18:08 |
| josce | Hem. 🥳 but 🤔🤔🤪 | 21:19:45 |
| josce | thks for your time anyway... | 21:20:09 |
| josce | I hadn't logged out of the 3rd server, mathstodon.xyz, and now it's getting notifications again there too - without any change. | 21:21:26 |
| josce | Earlier today my posts (web app sent) couldn't be seen from osm.town if people not @mentioned - and people couldn't @ me, the handle remained text. | 21:24:39 |
| josce | * Earlier today my posts (web app sent) couldn't be seen from osm.town if people were not @mentioned - and people couldn't @ me, the handle remained text. | 21:24:55 |
| 30 Mar 2024 |
| josce | Hm. So, 9 hours on, same problem reappearing. No notifications, can't reach credential page when attempting to log in to any of my servers, but can reach that page for mas.to or mastodon.social... | 08:12:09 |
| josce | But it's still the same with fedilab too. Where shall I enquire? It's weird as it happens:
- for different apps, but never with web connection,
- I also tryed with tootle on a desktop linux, and I can connect,
- for different servers, but not all of them.
- plus they are running different mastodon version.
...So it's difficult to define a suspect -- my old Android seems the most likely?
| 17:39:12 |
| 1 Apr 2024 |
 mcc111 | In reply to @josce:matrix.org
But it's still the same with fedilab too. Where shall I enquire? It's weird as it happens:
- for different apps, but never with web connection,
- I also tryed with tootle on a desktop linux, and I can connect,
- for different servers, but not all of them.
- plus they are running different mastodon version.
...So it's difficult to define a suspect -- my old Android seems the most likely?
This is a stretch, but what does it say in the top box if you visit this in your android in the browser? https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html | 19:35:29 |
| 3 Apr 2024 |
| josce | Hi. It says "good protocol support" with TLS 1.2 and 1.3, "not vulnerable", the only negative results seem to be "no TLS compression" and "no SSL 2 handshake compatibility". | 09:52:19 |
| mcc111 | Desktop Chrome doesn't have those last two features so that couldn't be it. OK thanks for checking. | 17:50:12 |
 trillian | so i've been having a mildly annoying issue with tusky for a while now. it seems like sometimes, a background thread would get into an infinite loop or something, constantly consuming cpu whenever tusky is open. after much trouble i managed to get android studio setup properly to allow profiling tusky, as an attempt to see what the stuck threads are doing. i've been using the development version for a few hours, but since i never figured out what triggers the bug, i can't tell if this has been fixed or if i just haven't hit the trigger yet. so i just wanted to ask whether this is something anyone else has encountered | 21:32:36 |
| trillian | (for context, i first noticed this just because my phone would get extremely hot when using tusky. then top in adb shell revealed tusky using 400% cpu. this was after i hadn't force-closed the app for a few days probably, force-closing fixed it. but the stuck threads would reappear later (i think i once saw it eat 40% cpu just a few minutes after restarting, so i'm guessing that's the cpu load of one stuck thread)) | 21:34:54 |
| 4 Apr 2024 |
| mcc111 | On iPhone there's something called a "stackshot" that lets you get the stacks of currently running threads on a non-development build. I wonder if there's an equivalent on Android. | 01:51:00 |
| josce | For the authentication issue on Android 7, I've been referred to this thread: https://gultsch.social/@daniel/112205723911295152
If I understand correctly, the suggested fix is for apps to do? | 06:40:57 |
| 5 Apr 2024 |
| josce | Pachli Current now gives the error when it fails to redirect me to the "enter credentials" page: "java.security.cert.CertPathValidatorException: Trust anchor for certification path not found." (both with "Login with Pachli" and "Login with Browser") | 13:20:21 |
| josce | * Pachli Current now gives the error when it fails to redirect me to the "enter credentials" page: "java.security.cert.CertPathValidatorException: Trust anchor for certification path not found." (both with "Login with Pachli" and "Login with Browser"). Chances are it's the same with Tusky? Would this apply : https://codeberg.org//iNPUTmice/Conversations/commit/88851ea12a9ea9d546a04321742a9656733291c3 ? | 14:17:05 |
