Getting bearer token from developer Network tab doesn't work - unexpected argument
Getting bearer token from browser developer Network tab doesn't work
Unexpected argument when rexit messages --token ey.... command is executed.
Hey that's not quite the usage, just add the --token to the command and a prompt will pop up to actually enter the token. So it's not needed to add it to the command.
Let me know if it works!
Has it helped at all?
Hey, thanks for getting in touch with me again. I tried it but I'm not sure if I was inserting it correctly at the prompt and implied it hadn't worked somehow.
But I'm not certain. I'll do it again this weekend properly and get back to you with exactly what happens.
Cheers
On Thu, 17 Apr 2025, 14:22 Maximilian Pult, @.***> wrote:
Has it helped at all?
— Reply to this email directly, view it on GitHub https://github.com/MPult/Rexit/issues/125#issuecomment-2812886193, or unsubscribe https://github.com/notifications/unsubscribe-auth/AURNAN74GVBWAP4RZACTPTD2Z6TJ5AVCNFSM6AAAAAB2U4E5G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJSHA4DMMJZGM . You are receiving this because you authored the thread.Message ID: @.***> MPult left a comment (MPult/Rexit#125) https://github.com/MPult/Rexit/issues/125#issuecomment-2812886193
Has it helped at all?
— Reply to this email directly, view it on GitHub https://github.com/MPult/Rexit/issues/125#issuecomment-2812886193, or unsubscribe https://github.com/notifications/unsubscribe-auth/AURNAN74GVBWAP4RZACTPTD2Z6TJ5AVCNFSM6AAAAAB2U4E5G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJSHA4DMMJZGM . You are receiving this because you authored the thread.Message ID: @.***>