On Ubuntu linux in Bash, credentials are only set after running `assume` twice

[JoshuaWilkes]

When running assume my-profile I get a success message

[cf-dev](ap-southeast-2) session credentials will expire 2022-08-04 11:50:47 +0800 AWST

However running env | grep AWS shows that no credentials are exported into my shell env

Running assume again for the same profile, and repeating the env check shows that credentials are exported.
Then aws commands work as expected

[nocnokneo]

I'm experiencing the same issue. Using SSO with a ~/.aws/config like:

[profile org]
sso_start_url  = https://xxx.awsapps.com/start
sso_region     = us-east-1
sso_account_id = xxx
sso_role_name  = xxx
region         = us-east-2
granted_color  = orange

# ...

And ~/.granted/config:

DefaultBrowser = "FIREFOX"
CustomBrowserPath = "/usr/bin/firefox"
CustomSSOBrowserPath = ""
Ordering = ""
ExportCredentialSuffix = ""

Using Chrome as my default browser for SSO authentication.

❯ assume --version

  /$$$$$$                                                      
 /$$__  $$                                                     
| $$  \ $$  /$$$$$$$ /$$$$$$$ /$$   /$$ /$$$$$$/$$$$   /$$$$$$ 
| $$$$$$$$ /$$_____//$$_____/| $$  | $$| $$_  $$_  $$ /$$__  $$
| $$__  $$|  $$$$$$|  $$$$$$ | $$  | $$| $$ \ $$ \ $$| $$$$$$$$
| $$  | $$ \____  $$\____  $$| $$  | $$| $$ | $$ | $$| $$_____/
| $$  | $$ /$$$$$$$//$$$$$$$/|  $$$$$$/| $$ | $$ | $$|  $$$$$$$
|__/  |__/|_______/|_______/  \______/ |__/ |__/ |__/ \_______/                                                                                                   

Version: 0.20.2

[acolominas]

Same here!
assume -v
Version: 0.20.2

[nocnokneo]

From some debugging of assume with set -x, I can see that the problem is due to the "Opening in existing browser session" output from Chrome:

...
[✔] [test](us-east-2) session credentials will expire in 12 hours
++ GRANTED_OUTPUT='Opening in existing browser session.
GrantedAssume [...REDACTED...] test us-east-2 2023-12-01T21:15:57-05:00 false None None None None'
...
++ GRANTED_FLAG=Opening

In this case, GRANTED_FLAG should have been set to GrantedAssume

[nocnokneo]

Bug still exists in v0.35.2

[gautamg795]

This is still an issue — a workaround would be to set your browser to "CUSTOM' and just use /bin/cat as the browser instead, or a similar no-op binary.

[TGNThump]

I'm seeing this issue breaking a granted credential-process call.

Process returned code 0
stdout:

Opening in existing browser session.
{"Version":1,...