-
Why exactly does the latest minor release requires new target & compileSDKs? Edit:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
I have only just added react-native-track-player to a project which was already working fine, and so installed version 3.2. My android build also failed as above. I went back to 3.1 but I am still getting the same set of errors. Very strange. I am using Expo with a custom dev client and used EAS build to build. Anyone have any suggestions? Thanks |
Beta Was this translation helpful? Give feedback.
-
same as above - I just added this dependency and faced the same issue. tried updating target to android 33, but that proved to be too complicated. I tried going down to 3.0 (which resulted in other build errors) and 3.1, which resulted in a correct build! my goal was actually to rewrite a sound-based approach to RNTP, but maybe the two cannot coexist in the same project? @SteveWaterfall - not quite sure about your case, but whenever I change the version, reinstall with npm and then rebuild locally - it works as excepted (fails or builds) |
Beta Was this translation helpful? Give feedback.
-
All you can see more info on this both here and here. You shouldn't need to update your |
Beta Was this translation helpful? Give feedback.
-
Delete the whole android folder if you have it committed
…On Tue, 4 Oct 2022, 23:07 SteveWaterfall, ***@***.***> wrote:
I am still getting the same errors if I downgrade to 3.1, even on a local
build. This is the first time I've used a package with custom code - is
there something else I need to do other than reinstall do you know?
—
Reply to this email directly, view it on GitHub
<#1761 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF4E6EVHK7UYNALWWWKCHDWBSMADANCNFSM6AAAAAAQX3JVC4>
.
You are receiving this because you commented.Message ID:
<doublesymmetry/react-native-track-player/repo-discussions/1761/comments/3799678
@github.com>
|
Beta Was this translation helpful? Give feedback.
All you can see more info on this both here and here.
You shouldn't need to update your
targetSdk
, but only yourcompileSdk
if I'm not mistaken. It's something we're looking into, and discussing the best path forward on internally.