Android Question Deprecated edge to edge api

I don't know how to fix this; Erel will most likely have to step in.

I just want to report here what Perplexity replied, hoping it can be useful:


"Your app uses deprecated edge-to-edge display APIs or parameters," indicates that the application is using APIs or parameters for edge-to-edge display that have been deprecated starting from Android 15 (API level 35). This has significant technical implications.

Technical Meaning of Deprecated API​

1. Edge-to-Edge Display:

• The edge-to-edge design means that the app's content extends to the edges of the screen, eliminating black bars or empty spaces. This approach aims to create a more immersive and modern visual experience, especially on devices with large or curved screens.

2. Deprecated APIs:

• Deprecated APIs, such as android.view.Window.setDecorFitsSystemWindows and android.view.Window.setNavigationBarColor, are no longer recommended for use and may be removed in future versions of the operating system. Using these APIs can lead to unexpected behaviors or compatibility issues with newer versions of Android.

3. Implications for Development:

• Developers need to update their code to use new APIs that support edge-to-edge behavior, such as applying insets to ensure that content is not hidden behind navigation or status bars. Failing to migrate to these new APIs could result in a compromised user interface and a poor user experience.

4. Opt-Out Option:

• Google has introduced a temporary opt-out feature allowing developers to avoid immediate compliance with edge-to-edge requirements, but this is only a short-term solution. Developers should plan to adapt their apps to conform to future standards, as this option will be removed eventually.

In summary, the message received implies that the app needs to be updated to remove the use of deprecated APIs and adopt new recommended practices to ensure compatibility and enhance user experience on Android 15 and later versions.

Agreed it is too many potential scenarios to isolate the issue to then try to comply. I have two apps that use all the same API's and Libraries and one gets the warning and the other doesn't so It is also possible it is a false positive detection by Google. If not then it may be in my case a visual object obscuring/overlapping another object that Google looks for visual object clashes either in your screen layout static template or when you dynamically place visual objects. Oh well I'm sure Erel will get to the root cause and solution so we can remedy this anomally.

Once you target SDK 35 or higher on a device running Android 15 or higher, your app is displayed edge-to-edge. The window spans the entire width and height of the display by drawing behind the system bars. System bars include the status bar, caption bar, and navigation bar.

Pendrush said:

Once you target SDK 35 or higher on a device running Android 15 or higher, your app is displayed edge-to-edge. The window spans the entire width and height of the display by drawing behind the system bars. System bars include the status bar, caption bar, and navigation bar.

Display content edge-to-edge in your app | Views | Android Developers

developer.android.com

Click to expand...

Your insight suggests we need to offset from the top to avoid conflict or blocking of our content by the system bar? I'm using Android sdk34 to get that warning from googleplay. But your point is noteworthy for future development when using sdk35 and up

Markos said:

Your insight suggests we need to offset from the top to avoid conflict or blocking of our content by the system bar? I'm using Android sdk34 to get that warning from googleplay. But your point is noteworthy for future development when using sdk35 and up

Click to expand...

Since you are now targeting API 34, there is no reason for concern. Only with target API 35 does the edge-to-edge API come into effect. What you see on Google Play is just a warning for libraries that need to be upgraded for upcoming changes.

Pendrush said:

Since you are now targeting API 34, there is no reason for concern. Only with target API 35 does the edge-to-edge API come into effect. What you see on Google Play is just a warning for libraries that need to be upgraded for upcoming changes.

Click to expand...

Thats great to hear. But pray tell any hints what libraroes we should look out to upgrade to comply. Would be splendid!