@kasun Made a quick by memory update to documentation. The complexity of the newer format lies mostly on nino granting you granularity on letting you choose keystore per project or even task, as well as deploy targets per project/task/split but not even I have usecases for this
I think I should drop deploying through adb support out of nino because after all it's either not convenient (connecting via USB to get updates) or too risky (listening on a network port).
Maybe I should focus the effort on supporting different methods like rsyncing or scp to copy the files to a final destination
@cesese Are you certain you logged in with the keys? Like if you tweet anything does it get flagged as sent from "Twitter for Android"?
@cesese master branch is at 3.7.6 but the maintenance, from which I'm building is at 3.7.8.
I would suggest giving a last try getting it from my fdroid repo if you wish.
Direct link follows:
@cesese from where did you got the build?
@cesese this is how I have it and can sync and send dms, is weird
@cesese Twitter for Android should work, note that if you already had login you have logoff and login back again after changing the keys