Fixed

Bug

Status Update

No update yet.

Description

au...@google.com

created issue #1

May 31, 2024 09:07PM

DESCRIBE THE ISSUE IN DETAIL:

Android is about to ship API 35, AGP should support.

STEPS TO REPRODUCE:

Build with AGP against android SDK 35

Expected

No warnings

Actual

WARNING: We recommend using a newer Android Gradle plugin to use compileSdk = 35
  
  This Android Gradle plugin (8.6.0-alpha03) was tested up to compileSdk = 34.
  
  You are strongly encouraged to update your project to use a newer
  Android Gradle plugin that has been tested with compileSdk = 35.
  
  If you are already using the latest version of the Android Gradle plugin,
  you may need to wait until a newer version with support for compileSdk = 35 is available.
  
  For more information refer to the compatibility table:
  https://d.android.com/r/tools/api-level-support
  
  To suppress this warning, add/update
      android.suppressUnsupportedCompileSdk=UpsideDownCake,VanillaIceCream,33,34,35
  to this project's gradle.properties.

Studio Build: n/a
Version of Gradle Plugin: 8.6.0-alpha03
Version of Gradle: 8.8-rc-1
Version of Java: 21
OS: linux

Comments

je...@google.com <je...@google.com> #2May 31, 2024 09:28PM

Assigned to cm...@google.com.

It seems the print is benign so I'll remove it; Could be worth it to find out how the message carrying information about "cb 0" (0 is not a valid color buffer handle) ever arrives to that line though

cm...@google.com <cm...@google.com> #3Jun 3, 2024 08:08AM

Reassigned to hm...@google.com.

I don't think we should necessarily remove these messages from the emulator code since at least some of them may point to real problems. I'm going to make sure that they are not treated as errors in Studio.

ko...@google.com <ko...@google.com> Jun 3, 2024 01:43PM

Reassigned to an...@google.com.

sp...@google.com <sp...@google.com> Jun 3, 2024 03:27PM

Reassigned to hm...@google.com.

cm...@google.com <cm...@google.com> #4Jun 3, 2024 04:15PM

I agree with Sergey -- while I think it's fine to remove some logging messages that aren't necessary, the root problem here is that Studio shows everything emitted as if they are errors, with one notification bubble per message. We don't do that for other tools that Studio launches, and in particular, this isn't specific to the "cb 0" message I showed here; there were earlier (different) error messages during the boot as well.

hm...@google.com <hm...@google.com> Jun 12, 2024 10:02AM

Reassigned to wf...@google.com.

ja...@geokeyaccess.com <ja...@geokeyaccess.com> #5Jun 13, 2024 09:21AM

This behavior was requested specifically by the emulator team (vharron@ iirc, so at least 3-4 years ago). Let me see if I have any more details on why this was requested.

au...@google.com <au...@google.com> #6Jul 24, 2024 08:55PM

I couldn't find any relevant threads. IIRC, the main concern at that time was that warnings at startup (e.g. missing acceleration) really needed to be bubbled up to the users. If that is not an issue anymore, and the emulator team only wants errors to be visible, then the proposed change SGTM.

au...@google.com <au...@google.com> #7Jul 30, 2024 04:37PM

Yes, I vaguely remember that in some cases, you'd hit run, and then the emulator would fail to start (for example aborting because of some missing thing it needed), so we needed a way to surface these reasons. I don't know if there are any fatal startup errors like this. It seems like there are several things we could do here:

(1) Simplest: just reroute the errors into the log, and if emulator fails to start, that's where people can look. (I think that's what Sergey has already implemented?)

(2) If emulator could update itself to prefix truly fatal error messages in some way (such as error:) and use that for only fatal/exit(-1) reasons, then we could multiplex the output -- errors are shown in notifications as today, everything else is silently dumped to the log

(3) Hold on to the emulator output, and if there's a problem starting the emulator (say if it exits within a few seconds), then show all the emulator output.

al...@google.com <al...@google.com> #8Jul 30, 2024 04:39PM

(1) ag/11396356 does write all emulator's messages into Studio log at INFO level.
(2) More discipline in the emulator's messages would definitely help. Right now they don't seem to follow any simple set of rules (the "Emulator: " prefix is added by Studio):

2020-05-06 11:07:04,587 [ 38858] INFO - manager.EmulatorProcessHandler - Emulator: /usr/local/google/home/sprigogin/Android/Sdk/emulator/emulator -netdelay none -netspeed full -avd Nexus_10_API_29 -no-window -gpu auto-no-window -grpc-use-token
2020-05-06 11:07:04,976 [ 39247] INFO - manager.EmulatorProcessHandler - Emulator: pulseaudio: Failed to initialize PA contextaudio: Could not init `pa' audio driver
2020-05-06 11:07:04,985 [ 39256] INFO - manager.EmulatorProcessHandler - Emulator: E0506 11:07:04.983601525 31440 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {"created":"@1588788424.983585430","description":"SO_REUSEPORT unavailable on compiling system","file":"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":169}
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator: Your emulator is out of date, please update by launching Android Studio:
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator: - Start Android Studio
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator: - Select menu "Tools > Android > SDK Manager"
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator: - Click "SDK Tools" tab
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator: - Check "Android Emulator" checkbox
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator: - Click "OK"
2020-05-06 11:07:05,321 [ 39592] INFO - manager.EmulatorProcessHandler - Emulator:
2020-05-06 11:07:06,475 [ 40746] INFO - manager.EmulatorProcessHandler - Emulator: emulator: INFO: LoggingInterceptor.cpp:70: 1588788426470945, rcvTime: 84, sndTime: 995, UNARY, rcv: 24, snd: 12156, /android.emulation.control.EmulatorController/getStatus() -> [...], OK
2020-05-06 11:07:07,355 [ 41626] INFO - manager.EmulatorProcessHandler - Emulator: emulator: INFO: LoggingInterceptor.cpp:70: 1588788426597819, rcvTime: 34, sndTime: 12945, SERVER_STREAMING, rcv: 48, snd: 1104071, /android.emulation.control.EmulatorController/streamScreenshot(format: RGBA8888 width: 665 height: 1064) -> [...], OK

cm...@google.com <cm...@google.com> #9Aug 2, 2024 09:24AM

Marked as fixed.

~~There are no warnings for API 35 in AGP 8.5.0~~ (this is not correct, see below)

The only known issue is in lint (internal Issue 354798431)

Message last modified on Sep 23, 2024 03:57PM

an...@google.com <an...@google.com> #10Aug 6, 2024 10:12PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Ladybug | 2024.2.1 Canary 4
Android Gradle Plugin 8.7.0-alpha04

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

wf...@google.com <wf...@google.com> #11Aug 7, 2024 02:07PM

I think the warnings are showing in 8.5.0, as the change was done in 8.6.0. To be discussed.

an...@google.com <an...@google.com> #12Aug 15, 2024 10:31PM

Further fixes for this issue are now available in:

Android Studio Ladybug | 2024.2.1 Canary 7
Android Gradle Plugin 8.7.0-alpha07

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

ro...@gmail.com <ro...@gmail.com> Aug 21, 2024 04:17PM

GoogleCybersecurityTimeline_Vertical_RGB (1).pdf

12 MB

View

Download

cm...@google.com <cm...@google.com> #13Aug 23, 2024 01:42PM

Sorry looking back at this I got the version wrong in #comment9.

#comment11 is correct - this AGP 8.6.0 (which is in RC now and should be stable very soon) declares it supports API 35.

an...@google.com <an...@google.com> #14Aug 28, 2024 05:38PM

Further fixes for this issue are now available in:

Android Studio Ladybug | 2024.2.1 Canary 8
Android Gradle Plugin 8.7.0-alpha08

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

wa...@gmail.com <wa...@gmail.com> #15Aug 30, 2024 04:19PM

val networkRequestBuilder = NetworkRequest.Builder() // Add or remove capabilities based on your requirements. // For example, this code specifies that the job won't run // unless there's a connection to the internet (not just a local // network), and the connection doesn't charge per-byte. .addCapability(NET_CAPABILITY_INTERNET) .addCapability(NET_CAPABILITY_NOT_METERED) .build()

val jobInfo = JobInfo.Builder(jobId, ComponentName(mContext, CustomTransferService::class.java)) // ... .setUserInitiated(true) .setRequiredNetwork(networkRequestBuilder) // Provide your estimate of the network traffic here .setEstimatedNetworkBytes(1024 * 1024 * 1024) // ... .build()

ro...@gmail.com <ro...@gmail.com> #16Oct 12, 2024 01:37AM

Comment has been deleted.

Message last modified on Oct 14, 2024 01:07PM

an...@google.com <an...@google.com> #17Jan 23, 2025 08:52PM

The fixes for this issue are now also available in:

Android Studio Meerkat Feature Drop | 2024.3.2 Canary 2
Android Gradle Plugin 8.10.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

IssueTracker

AGP should claim that it supports API 35 that is about to ship

Status Update

Description

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

Expected

Actual

Comments

je...@google.com <je...@google.com> #2May 31, 2024 09:28PM

cm...@google.com <cm...@google.com> #3Jun 3, 2024 08:08AM

ko...@google.com <ko...@google.com> Jun 3, 2024 01:43PM

sp...@google.com <sp...@google.com> Jun 3, 2024 03:27PM

cm...@google.com <cm...@google.com> #4Jun 3, 2024 04:15PM

hm...@google.com <hm...@google.com> Jun 12, 2024 10:02AM

ja...@geokeyaccess.com <ja...@geokeyaccess.com> #5Jun 13, 2024 09:21AM

au...@google.com <au...@google.com> #6Jul 24, 2024 08:55PM

au...@google.com <au...@google.com> #7Jul 30, 2024 04:37PM

al...@google.com <al...@google.com> #8Jul 30, 2024 04:39PM

cm...@google.com <cm...@google.com> #9Aug 2, 2024 09:24AM

an...@google.com <an...@google.com> #10Aug 6, 2024 10:12PM

wf...@google.com <wf...@google.com> #11Aug 7, 2024 02:07PM

an...@google.com <an...@google.com> #12Aug 15, 2024 10:31PM

ro...@gmail.com <ro...@gmail.com> Aug 21, 2024 04:17PM

cm...@google.com <cm...@google.com> #13Aug 23, 2024 01:42PM

an...@google.com <an...@google.com> #14Aug 28, 2024 05:38PM

wa...@gmail.com <wa...@gmail.com> #15Aug 30, 2024 04:19PM

ro...@gmail.com <ro...@gmail.com> #16Oct 12, 2024 01:37AM

an...@google.com <an...@google.com> #17Jan 23, 2025 08:52PM

sa...@gmail.com <sa...@gmail.com> #18Jan 31, 2025 08:41PM

Issue 344016691

Description

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

Expected

Actual

Issue summary

Comments

je...@google.com <je...@google.com> #2May 31, 2024 09:28PM

cm...@google.com <cm...@google.com> #3Jun 3, 2024 08:08AM

ko...@google.com <ko...@google.com> Jun 3, 2024 01:43PM

sp...@google.com <sp...@google.com> Jun 3, 2024 03:27PM

cm...@google.com <cm...@google.com> #4Jun 3, 2024 04:15PM

hm...@google.com <hm...@google.com> Jun 12, 2024 10:02AM

ja...@geokeyaccess.com <ja...@geokeyaccess.com> #5Jun 13, 2024 09:21AM

au...@google.com <au...@google.com> #6Jul 24, 2024 08:55PM

au...@google.com <au...@google.com> #7Jul 30, 2024 04:37PM

al...@google.com <al...@google.com> #8Jul 30, 2024 04:39PM

cm...@google.com <cm...@google.com> #9Aug 2, 2024 09:24AM

an...@google.com <an...@google.com> #10Aug 6, 2024 10:12PM

wf...@google.com <wf...@google.com> #11Aug 7, 2024 02:07PM

an...@google.com <an...@google.com> #12Aug 15, 2024 10:31PM

ro...@gmail.com <ro...@gmail.com> Aug 21, 2024 04:17PM

cm...@google.com <cm...@google.com> #13Aug 23, 2024 01:42PM

an...@google.com <an...@google.com> #14Aug 28, 2024 05:38PM

wa...@gmail.com <wa...@gmail.com> #15Aug 30, 2024 04:19PM

ro...@gmail.com <ro...@gmail.com> #16Oct 12, 2024 01:37AM

an...@google.com <an...@google.com> #17Jan 23, 2025 08:52PM

sa...@gmail.com <sa...@gmail.com> #18Jan 31, 2025 08:41PM

Add comment

Issue metadata