Anyone know why navigation component 2.4.0 require...
# compose
m
Anyone know why navigation component 2.4.0 requires compile sdk 31? I’m running into this because we’re using compile sdk 30, and i’m trying to use accompanist to do the navigation animation, which depends on 2.4.0 alpha 7 of navigation. That happens to require sdk 31. The issue is that upgrading our app with this would mean reworking a bunch of our bluetooth code to account for the new bluetooth permissions. We’ll have to do this eventually, but it does present a barrier.
e
compile sdk != target sdk, you shouldn't need to adapt to new permissions until you bump the target sdk
👆 3
i
You'll note that every AndroidX release since API 31 was finalized compiles with API 31 - Navigation is not unique in that case. You should always compile with the latest SDK as per https://medium.com/androiddevelopers/picking-your-compilesdkversion-minsdkversion-targetsdkversion-a098a0341ebd