You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The minimal android SDK version required by the Google Play store to be able to publish an app has been bumped to version 34. However the current release of xbuild does not support this, being maxed at 33.
The text was updated successfully, but these errors were encountered:
As far as I can tell all that really needs to happen is for the sdk workflow to be re-run (possibly with minor updates, I'm not sure). It simply packages the sdk libs and puts them on the release assets page, and the ubuntu-latest runner image which is used (at least for the linux part of that workflow) contains SDK versions 33-35.
Then the hard-coded link in the xbuild source would have to be updated to pull the latest release assets for the SDK as before.
PS As a temporary workaround, I copied my standalone android sdk platform and ndk libs into ~/.cache/x/, in the same layout as what's already there, and changed the version to 34 in the xbuild src. That got things working for me, in case you need a hacky workaround until this gets fixed.
Alternatively, the cargo-mobile2 tool by the tauri peeps uses whatever android system you have installed, so you're fairly free to do as you please with that, though their android support is in the process of being updated.
The minimal android SDK version required by the Google Play store to be able to publish an app has been bumped to version 34. However the current release of
xbuild
does not support this, being maxed at 33.The text was updated successfully, but these errors were encountered: