Obsolete
Status Update
No update yet.
Comments
ma...@gmail.com
Can you elaborate on the end goal/use-case? We have service accounts that are designed for non-interactive authentication: https://cloud.google.com/docs/authentication
ma...@gmail.com
We both use Service accounts, API keys and OAuth client credentials in our projects. The first two types can be created using the gcloud command, such as 'gcloud beta iam service-accounts create some-account --display-name "My Service Account"' for a Service Account.
OAuth client credentials don't seem to be able to be created using the gcloud command as far as we know and need to be created through the developer console. Since we create new projects from time to time and setup our environments in those projects in an almost automated way, this step means we have to manually create the OAuth client credentials ergo blocking our automation.
OAuth client credentials don't seem to be able to be created using the gcloud command as far as we know and need to be created through the developer console. Since we create new projects from time to time and setup our environments in those projects in an almost automated way, this step means we have to manually create the OAuth client credentials ergo blocking our automation.
ma...@gmail.com
Being able to automate changes to the consent screen with gcloud CLI would be very useful. Updating configuration for: Email address, Product name, Homepage URL, Product logo URL, Privacy policy URL, Terms of service URL.
Description
App Starts with [1], User can only navigate to [2] and then optionally to [3]. Since [3] is deep down, I want [3] to go back to [1] directly.
Currently I call [2] using addToBackStack(null). Since I do NOT call addToBackStack on [3] I assumed it will go back to [1].
What happens is, that [3] returns to [1], but now both fragments are displayed overlapping(!). Fragment [3] does not call onPause(). Calling fragment [2] again will display [2] on top of the others, not clearing the screen.
Navigating back and forth will crash the app. Sometimes on opening a new fragment, sometimes when hitting the back button. Always with "Fragment already added" error (which is extremely odd for the back button, but I check that also before switching fragments).
Sample App attached. Appcompat v7 used.