Need quick fix for discrepancy between compileSdk and dependency with minCompileSdkVersion [308175247]

Fixed

Feature Request

Status Update

No update yet.

Description

xa...@google.com

created issue #1

Oct 27, 2023 06:43PM

Upgrading to a new dependency may trigger an error if the new dependency requires a compileSdk that's higher than the one used in the project.

The error, coming from Gradle will look like this:

5 issues were found when checking AAR metadata:
  1.  Dependency 'androidx.navigation:navigation-common:2.7.0-beta02' requires libraries and applications that
      depend on it to compile against version 34 or later of the
      Android APIs.

      :app is currently compiled against android-33.

      Also, the maximum recommended compile SDK version for Android Gradle
      plugin 7.4.2 is 33.

      Recommended action: Update this project's version of the Android Gradle
      plugin to one that supports 34, then update this project to use
      compileSdkVerion of at least 34.

      Note that updating a library or application's compileSdkVersion (which
      allows newer APIs to be used) can be done separately from updating
      targetSdkVersion (which opts the app in to new runtime behavior) and
      minSdkVersion (which determines which devices the app can be installed
      on).

  2.  ...

(it's possible the formatting is slightly different if there's only one issue).

Studio should provide a quick fix on this to automatically upgrade compileSdk to the right version.

Comments

xa...@google.com <xa...@google.com> #2Oct 27, 2023 06:44PM

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?

er...@google.com <er...@google.com> Oct 30, 2023 10:46PM

Assigned to an...@google.com.

xa...@google.com <xa...@google.com> #3Oct 30, 2023 11:01PM

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

je...@google.com <je...@google.com> Nov 2, 2023 06:11AM

Reassigned to am...@google.com.

am...@google.com <am...@google.com> Nov 29, 2023 06:10PM

Accepted by am...@google.com.

am...@google.com <am...@google.com> Dec 1, 2023 05:18PM

Marked as fixed.

an...@google.com <an...@google.com> #4Dec 7, 2023 11:03PM

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.