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.

for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?

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

Reassigned to hm...@google.com.

the fractional part of the location data is exactly the same.

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

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

What steps are needed to reproduce this issue? Frequency of occurrence?

Which Android build are you using? (e.g. AP4A.241205.013.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Please provide a 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 (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

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.

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

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

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

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

I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。

as for Android build,all versions have it.
I dont reprodouce this issue.

what may be the cause of this issue?please

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

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

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

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

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

Marked as fixed.

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

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

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

Thank you very much! it is very useful to me . It solved my confusion.

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