BaselineProfiles are not generated using Firebase Test Lab devices with Gradle Managed Device [285187547]

Fixed

Bug

Status Update

No update yet.

Description

di...@target.com

created issue #1

Jun 1, 2023 01:11PM

We are trying to generate Baseline Profiles for our application using the BaselineProfiles plugin and since we want to generate it on our CI/CD pipelines we are exploring Gradle Managed devices.

As there is an already existing issue where Gradle Managed devices fail to setup on Linux machines, we are exploring the new feature of using Firebase Test Lab devices as Gradle Managed devices.

I am following the performance sample app and included the changes mentioned for running tests on Firebase Test Lab devices as Gradle Managed device. When the task generateBaselineProfile runs locally, Baseline Profiles are generated correctly. However, when run on the FTL configured device, tests are running successfully, but the profiles are not generated and I see this message in the output:

No baseline profile rules were generated for the variant `release`.
This is most likely because there are no instrumentation test for it. If this
is not intentional check that tests for this variant exist in the `baselineProfile`
dependency module.

Comparing the logs from local and FTL, I could see that the profiles are generated in a directory different than the task tries to extract from:

05-26 09:23:41.425: D/Benchmark(9473): Reference profile location: /data/misc/profiles/ref/com.example.macrobenchmark.target/primary.prof
...
05-26 09:23:41.545: D/Benchmark(9473): APK Path: /data/app/~~kpdhuDgDtK4xTg_DWXX1nQ==/com.example.macrobenchmark.target-NvgEVbxIsGXC8BzbuvHGrg==/base.apk
05-26 09:23:41.545: D/Benchmark(9473): Converting to human readable profile format
05-26 09:23:41.545: D/Benchmark(9473): Using profile location: /data/misc/profiles/ref/com.example.macrobenchmark.target/primary.prof
...
05-26 09:23:41.844: D/Benchmark(9473): Using profile location: /data/misc/profiles/cur/0/com.example.macrobenchmark.target/primary.prof
...
05-26 09:23:44.174: D/Benchmark(9473): Pull Baseline Profile with: `adb pull "/storage/emulated/0/Android/media/com.example.benchmark.baselinprofile/ComposeActivityBaselineProfileGenerator_profileGenerator-baseline-prof-2023-05-26-16-23-43.txt" .`
05-26 09:23:44.266: D/Benchmark(9473): Total Run Time Ns: 37069762291
05-26 09:23:44.268: D/Benchmark(9473): Killing process com.example.macrobenchmark.target

When run locally, I can see that it is using the same location from which it is later extracted:

2023-05-27 00:17:09.432  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  additionalTestOutputDir=/sdcard/Android/media/com.example.benchmark.baselinprofile/additional_test_output
...
2023-05-27 00:17:09.448  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  Usable output directory: /storage/emulated/0/Android/media/com.example.benchmark.baselinprofile
2023-05-27 00:17:09.449  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  Output Directory: /sdcard/Android/media/com.example.benchmark.baselinprofile/additional_test_output
2023-05-27 00:17:40.452  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  Copying /storage/emulated/0/Android/media/com.example.benchmark.baselinprofile/LoginBaselineProfileGenerator_profileGenerator-baseline-prof.txt to /sdcard/Android/media/com.example.benchmark.baselinprofile/additional_test_output/LoginBaselineProfileGenerator_profileGenerator-baseline-prof.txt
2023-05-27 00:17:40.462  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  Pull Baseline Profile with: `adb pull "/storage/emulated/0/Android/media/com.example.benchmark.baselinprofile/LoginBaselineProfileGenerator_profileGenerator-baseline-prof-2023-05-26-18-47-40.txt" .`
2023-05-27 00:17:40.467  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  Copying /storage/emulated/0/Android/media/com.example.benchmark.baselinprofile/LoginBaselineProfileGenerator_profileGenerator-baseline-prof-2023-05-26-18-47-40.txt to /sdcard/Android/media/com.example.benchmark.baselinprofile/additional_test_output/LoginBaselineProfileGenerator_profileGenerator-baseline-prof-2023-05-26-18-47-40.txt
2023-05-27 00:17:40.475  7983-8002  Benchmark               com...mple.benchmark.baselinprofile  D  Total Run Time Ns: 10786612088

Setup:

Android Studio Hedgehog | 2023.1.1 Canary 5

Build #AI-231.7864.76.2311.10195651, built on May 25, 2023

Runtime version: 17.0.6+0-17.0.6b829.9-10027231 aarch64

AGP 8.2.0-alpha05

Benchmark 1.2.0-alpha13

Could the copying be an issue?

I have attached the performance sample app code with the changes. Run it in the above configuration with FTL setup and should see a similar output.

performance-samples.zip

7.9 MB

Download

Comments

di...@target.com <di...@target.com> #2Jun 1, 2023 01:15PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build

Which Android build are you using? (e.g. OPP1.170223.012)

Device used - Device Make, Model, Android OS Version

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report capturing

After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.

Alternate method

Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen record of the issue, for clarity

Please capture screen record or video of the issue using following steps:

adb shell screenrecord /sdcard/video.mp4

Subsequently use following command to pull the recorded file:

adb pull /sdcard/video.mp4

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

ra...@google.com <ra...@google.com> Jun 1, 2023 08:06PM

Reassigned to ma...@google.com.

ma...@google.com <ma...@google.com> #3Jun 1, 2023 10:46PM

android 9, 10, 11, 12
Devices: samsung, realme, xiaomi, OPPO, motorola, LGE,

I don't know how to write code reproducing issues in Android framework, unless you explain what does "no event down from INITIALIZED" mean. Then maybe I can prepare a piece of code that doesn't "event down from INITIALIZED". Until then - sorry.

Also - this error doesn't ever show on the device it is just logged to crashlytics, so there's now way to capture anything "after reproducing the issue".

di...@gmail.com <di...@gmail.com> #4Jun 2, 2023 06:49AM

Comment has been deleted.

Message last modified on Jun 2, 2023 06:49AM

di...@target.com <di...@target.com> #5Jun 2, 2023 06:50AM

Glad to hear it was fixed. I'm experiencing it with lifecycle 2.5.1.

ma...@google.com <ma...@google.com> #6Jun 2, 2023 05:23PM

I mean it was fixed to throw the error in Lifecycle 2.5. It was always supposed to be an error.

ma...@google.com <ma...@google.com> #7Jun 2, 2023 05:38PM

So some thing (implementing some lifecycle interface I guess?) somewhere tries to go into destroyed state before this thing was even created.

Whoa! That's some info!

Now - how can I, having this error message and error stack, discover WHAT exactly is causing this error?

Because, you know, I don't really create thingies having their own lifecycle...

di...@target.com <di...@target.com> #8Jun 5, 2023 09:38AM

Well from the stack, your Activity is being started and the fragment is getting destroyed.

So there is some fragment that is added to your activity that is being removed before it's Lifecycle goes to CREATED.

performance-samples.zip

7.7 MB

Download

di...@target.com <di...@target.com> #9Jun 5, 2023 09:48AM

OK, that might indeed help finding something, if indeed I'm destroying a fragment before it was created (although I have no idea how to do such stunt). But would it be impossible to include component name in the error, like i.e. in this helpful and friendly exception:

java.lang.IllegalStateException: The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. Make sure your adapter calls notifyDataSetChanged() when its content changes. [in ListView(2131230928, class android.widget.ListView) with Adapter(class com.students.post.Post_Fragment$Post_listAdapter)]

ma...@google.com <ma...@google.com> #10Jun 5, 2023 09:49PM

The LifecycleOwner is indeed available from the LifecycleRegistry so we can add that as part of the message so you know which component it is referring to.

di...@target.com <di...@target.com> #11Jun 6, 2023 10:41AM

That would be most helpful, thanks! Can you somehow estimate a timeframe for that fix?

Message last modified on Jun 6, 2023 11:13AM

di...@target.com <di...@target.com> #12Jun 12, 2023 09:26AM

Project: platform/frameworks/support
Branch: androidx-main

commit e7dfcd2e09ee1dd3589fbd548f50617a8f1c1356
Author: sanura <sanura@google.com>
Date: Thu Oct 13 03:07:32 2022

Update LifecycleRegistry.moveToState() error message

Include the name of the component in the error
message for LifecycleRegistry.moveToState() to
better help developers debug which component is
trying to do an illegal state movement.

RelNote: "`LifecycleRegistry.moveToState()` now
includes more helpful error messaging that informs
developers of the component causing the error."
Test: moveInitializedToDestroyed update
Bug: 244910446

Change-Id: Idf4b23476f809e6c6ff2361d9e864653c90fea2a

M lifecycle/lifecycle-runtime/src/main/java/androidx/lifecycle/LifecycleRegistry.java
M lifecycle/lifecycle-runtime/src/test/java/androidx/lifecycle/LifecycleRegistryTest.java

https://android-review.googlesource.com/2253416

ma...@google.com <ma...@google.com> #13Jun 14, 2023 06:19PM

Any way to know when and where this fix will be available for us, devs?

di...@target.com <di...@target.com> #14Jun 15, 2023 11:28AM

This has been fixed internally and will be available in Lifecycle 2.6.0-alpha03

Message last modified on Jun 15, 2023 11:36AM

ma...@google.com <ma...@google.com> #15Jun 15, 2023 04:52PM

When would 2.6.0-alpha03 be available to developers?

ed...@gmail.com <ed...@gmail.com> #16Jun 17, 2023 09:03PM

The following release(s) address this bug:

androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03

ma...@google.com <ma...@google.com> #17Jun 20, 2023 05:15PM

Reassigned to bu...@google.com.

Uuuuum... Indeed, the error show something, but what is it?! How am I supposed to decipher this?

Fatal Exception: java.lang.IllegalStateException: no event down from INITIALIZED in component d{7f1b10e} (0b387363-3c6b-4f7d-af8f-22ebafc87084 id=0x7f0a0302 tag=a::)

bu...@google.com <bu...@google.com> #18Jun 20, 2023 05:17PM

Accepted by bu...@google.com.

Re comment#17 - you have ProGuard obfuscation on, so you'd need to use your mapping file to figure out what class d is in your app, following the 'You can identify your Fragment' section in the debug your fragments guide.

di...@target.com <di...@target.com> #19Jun 21, 2023 02:48PM

Well, I haven't checked proguard files in a long time, but I can see they got somehow worse. I see hundreds of things that get mapped to JUST "d"!

ma...@google.com <ma...@google.com> #20Jun 21, 2023 05:51PM

I have:

androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03
androidx.navigation:navigation-fragment-ktx:2.5.3
androidx.navigation:navigation-ui-ktx:2.5.3

and got crash:

java.lang.RuntimeException: Unable to destroy activity {<package name hidden by me>.MainActivity}: java.lang.IllegalStateException: no event down from INITIALIZED in component androidx.navigation.NavBackStackEntry

with reason:

Caused by: java.lang.IllegalStateException: no event down from INITIALIZED in component androidx.navigation.NavBackStackEntry

(I see that issue is connected with NavBackStackEntry thanks update to :lifecycle-runtime:2.6.0-alpha03)

In my MainActivity there is NavHostFragment with NavController and queue of NavBackStackEntries inside.
When I navigate from Acitivity to some fragment using code below:

Log.i("showSomeFragment","state just before navigate: ${findNavController().currentBackStackEntry?.lifecycle?.currentState}")
findNavController().navigate(
MainNavgraphDirections.actionShowSomeFragment(...)
)

Log shows that NavBackStackEntry's lifecycle's is in state RESUMED, but in target fragment's onCreate (after navigation)
NavBackStackEntry's lifecycle's is in state INITIALIZED

Therefore, when I minimize app being on that fragment - app crashes, because I go from INITIALIZED to DESTROYED state (skipping other states).

When I navigate similarly between fragments (using findNavController().navigate in fragment, not in activity) ->
NavBackStackEntry's lifecycle's state is in state RESUMED in target's fragment onCreate an there is no crash after minimize.

Do I don't understand something/do you have any hints for that, or there is bug in navigation library?

For clarity: Yes, I understand that when we go from INITIALIZED directly to DESTROYED state - error SHOULD be thrown

za...@gmail.com <za...@gmail.com> #21Jan 10, 2024 11:34PM

Exactly same problem as

comment#20

be...@google.com <be...@google.com> #22Jan 15, 2024 11:03AM

Re comment#20 - please file a bug against Navigation that includes a same project that reproduces your issue.

li...@gmail.com <li...@gmail.com> #23Aug 23, 2024 04:38PM

I have a same problem
Fatal Exception: java.lang.RuntimeException: Unable to destroy activity {path to MainActivity}: java.lang.IllegalStateException: no event down from INITIALIZED
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5253)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:5282)
at android.app.servertransaction.DestroyActivityItem.execute(DestroyActivityItem.java:44)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2146)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:8057)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)

se...@team.bumble.com <se...@team.bumble.com> #24Aug 27, 2024 11:24AM

Re comment#23 - please file a bug against Activity that includes a sample project that reproduces your issue. We really, really, really need you to include a sample project.

Message last modified on Sep 13, 2024 12:48PM

li...@gmail.com <li...@gmail.com> #25Sep 8, 2024 03:55PM

deleted

Message last modified on Sep 8, 2024 03:56PM

bu...@google.com <bu...@google.com> Sep 12, 2024 11:03PM

Assigned to ma...@google.com.

se...@team.bumble.com <se...@team.bumble.com> #26Sep 13, 2024 01:00PM

deleted

Message last modified on Sep 13, 2024 01:02PM

li...@gmail.com <li...@gmail.com> #27Sep 13, 2024 03:08PM

deleted

Message last modified on Sep 16, 2024 04:08PM

ma...@google.com <ma...@google.com> #28Sep 17, 2024 11:36PM

Hi also having the same problem here, and not able to reproduce it locally, seems from the log that it happened when onBackPressed is triggered. I have tried to put dismiss inside init function of my dialog fragment also not able to reproduce it. Is there any thing I can look into? I'm using Lifecycle 2.6.1, happened as well in 2.5.1

androidx.lifecycle.LifecycleRegistry.moveToState (LifecycleRegistry.kt:126)
androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent (LifecycleRegistry.kt:119)
androidx.activity.ComponentDialog.onStop (ComponentDialog.kt:87)
androidx.appcompat.app.AppCompatDialog.onStop (AppCompatDialog.java:134)
android.app.Dialog.dismissDialog (Dialog.java:382)
android.app.Dialog.dismiss (Dialog.java:358)
androidx.appcompat.app.AppCompatDialog.dismiss (AppCompatDialog.java:140)
android.app.Dialog.cancel (Dialog.java:1269)
android.app.Dialog.onBackPressed (Dialog.java:684)
androidx.activity.ComponentDialog.onBackPressedDispatcher$lambda$1 (ComponentDialog.kt:94)
androidx.activity.OnBackPressedDispatcher.onBackPressed (OnBackPressedDispatcher.kt:216)
androidx.activity.ComponentDialog.onBackPressed (ComponentDialog.kt:99)
android.app.Dialog.onKeyUp (Dialog.java:661)
android.view.KeyEvent.dispatch (KeyEvent.java:2729)
android.app.Dialog.dispatchKeyEvent (Dialog.java:814)
androidx.appcompat.app.AppCompatDialog.superDispatchKeyEvent (AppCompatDialog.java:209)
androidx.core.view.KeyEventDispatcher.dispatchKeyEvent (KeyEventDispatcher.java:86)
androidx.appcompat.app.AppCompatDialog.dispatchKeyEvent (AppCompatDialog.java:215)
androidx.appcompat.view.WindowCallbackWrapper.dispatchKeyEvent (WindowCallbackWrapper.java:60)
androidx.appcompat.app.AppCompatDelegateImpl$AppCompatWindowCallback.dispatchKeyEvent (AppCompatDelegateImpl.java:3413)
com.android.internal.policy.DecorView.dispatchKeyEvent (DecorView.java:346)
android.view.ViewRootImpl$ViewPostImeInputStage.processKeyEvent (ViewRootImpl.java:5214)
android.view.ViewRootImpl$ViewPostImeInputStage.onProcess (ViewRootImpl.java:5082)
android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:4601)
android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:4654)
android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:4620)
android.view.ViewRootImpl$AsyncInputStage.forward (ViewRootImpl.java:4760)
android.view.ViewRootImpl$InputStage.apply (ViewRootImpl.java:4628)
android.view.ViewRootImpl$AsyncInputStage.apply (ViewRootImpl.java:4817)
android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:4601)
android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:4654)
android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:4620)
android.view.ViewRootImpl$InputStage.apply (ViewRootImpl.java:4628)
android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:4601)
android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:4654)
android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:4620)
android.view.ViewRootImpl$AsyncInputStage.forward (ViewRootImpl.java:4793)
android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent (ViewRootImpl.java:4956)
android.view.inputmethod.InputMethodManager$PendingEvent.run (InputMethodManager.java:2580)
android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback (InputMethodManager.java:2090)
android.view.inputmethod.InputMethodManager.finishedInputEvent (InputMethodManager.java:2081)
android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished (InputMethodManager.java:2557)
android.view.InputEventSender.dispatchInputEventFinished (InputEventSender.java:141)
android.os.MessageQueue.nativePollOnce (MessageQueue.java)
android.os.MessageQueue.next (MessageQueue.java:326)
android.os.Looper.loop (Looper.java:165)
android.app.ActivityThread.main (ActivityThread.java:6861)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:547)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:873)

Message last modified on Sep 18, 2024 09:18PM

ap...@google.com <ap...@google.com> #29Sep 18, 2024 10:56PM

Project: platform/frameworks/support
Branch: androidx-main

commit 7e25ec644b2fd621b7a96016f9e397dab254540d
Author: Marcello Albano <maralb@google.com>
Date: Tue Sep 17 15:11:56 2024

Added support for FTL to Baseline Profile Gradle Plugin

FTL devices don't use per test artifacts, rather global ones,
so in test-results.pb they need to be found separately.
Note that the ftl plugin still needs to be configured separately.

Relnote: "Added support for FTL to Baseline Profile Gradle Plugin.
To use FTL apply the plugin to the baseline profile module in the
plugin block, with:
```
plugins {
...
id(\"com.google.firebase.testlab\")
}
```

and then configure firebase test lab with:

```
firebaseTestLab {

// Credentials for FTL service
serviceAccountCredentials.set(file(\"credentials.json\"))

// Creates one or more managed devices to run the tests on.
managedDevices {
\"ftlDeviceShiba34\" {
device = \"shiba\"
apiLevel = 34
}
}

// Ensures the baseline profile are pulled from the device.
// Note that this will be automated as well later with aosp/3272935.
testOptions {
results {
directoriesToPull.addAll(\"/storage/emulated/0/Android/media/${android.namespace}\")
}
}
}
```

Also the created ftl device needs to be added to the baseline profile extension:

```
baselineProfile {
managedDevices += \"ftlDeviceShiba34\"
useConnectedDevices = false
}
```"
Test: ./gradlew :benchmark:benchmark-baseline-profile-gradle-plugin:test
Bug: 285187547

Change-Id: I2f6789d81a32d04df976437c2be426cbe04488ac

M benchmark/baseline-profile-gradle-plugin/src/main/kotlin/androidx/baselineprofile/gradle/producer/tasks/CollectBaselineProfileTask.kt
M benchmark/baseline-profile-gradle-plugin/src/test/kotlin/androidx/baselineprofile/gradle/consumer/BaselineProfileConsumerPluginTest.kt
M benchmark/baseline-profile-gradle-plugin/src/test/kotlin/androidx/baselineprofile/gradle/utils/BaselineProfileProjectSetupRule.kt
M benchmark/baseline-profile-gradle-plugin/src/test/kotlin/androidx/baselineprofile/gradle/utils/TestUtils.kt

https://android-review.googlesource.com/3267102

li...@gmail.com <li...@gmail.com> #30Sep 21, 2024 08:25PM

I apologise for posting an offtopic, but attempting to setup Baseline Profiles generation, using the above instructions and FTL Gradle plugin, I've encountered a strange dependency issue: https://issuetracker.google.com/issues/368628050

Firebase section of the issue tracker is not available for me, so posting a reference here with a hope, that somebody with access could check for duplicates and maybe suggest a solution.

ma...@google.com <ma...@google.com> #31Oct 1, 2024 05:18PM

Marked as fixed.

Thanks, the dependency issue is a different one already been tracked. Closing this one.

li...@gmail.com <li...@gmail.com> #32Oct 1, 2024 08:59PM

Thanks!

Which version is this fix coming to? Will it be 1.3.2 or we'll need to wait for 1.4.0 release?

pr...@google.com <pr...@google.com> #33Oct 2, 2024 05:37PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.annotation:annotation-wasm-js:1.9.0-rc01
androidx.annotation:annotation-watchosdevicearm64:1.9.0-rc01
androidx.benchmark:benchmark-baseline-profile-gradle-plugin:1.3.2
androidx.benchmark:benchmark-baseline-profile-gradle-plugin:1.4.0-alpha02

mo...@hungerstation.com <mo...@hungerstation.com> #34Oct 21, 2024 08:21AM

Hello googlers,

I did as this comment #28

Our CI stack is Bitrise + Fastlane, I'm getting this error even when i run this sh "gcloud auth activate-service-account --key-file=#{decoded_service_account}"

Execution failed for task ':macrobenchmark:ftlDeviceShiba34Setup'.

A failure occurred while executing com.android.build.gradle.internal.tasks.ManagedDeviceSetupTask$SetupTaskWorkAction Unable to find the application-default credentials to send a request to Firebase TestLab. Please initialize your credentials using gcloud CLI. Examples: gcloud config set project $YOUR_PROJECT_ID gcloud auth application-default login gcloud auth application-default set-quota-project $YOUR_PROJECT_ID Please read https://cloud.google.com/sdk/gcloud for details.

Message last modified on Oct 21, 2024 08:27AM