Newer packages available

[solitudery]

When running "fvm flutter pub get" with Flutter 3.41.2 set in fvm in the project directory, it outputs:

Downloading packages... (45.0s)
  cli_util 0.4.2 (0.5.1 available)
  image 4.8.0 (4.9.1 available)
  intl 0.20.2 (0.20.3 available)
  local_auth_android 2.0.8 (2.0.9 available)
  matcher 0.12.18 (0.12.20 available)
  meta 1.17.0 (1.18.3 available)
  shared_preferences_android 2.4.23 (2.4.26 available)
  test_api 0.7.9 (0.7.13 available)
  url_launcher_android 6.3.30 (6.3.32 available)
  vector_math 2.2.0 (2.4.0 available)
  xml 6.6.1 (7.0.1 available)
Got dependencies!
11 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.

Am I supposed to run the pub outdated command or is this a red herring / unnecessary? I'm new to this so forgive me if it's a peculiar or out of place question.

[resurrectdev1]

Hello @solitudery,

No worries I had the same question myself when first starting out in flutter! As for the newer versions, no need to update them yourself since I take care of that and publish updates once everything's tested and stable. Those specific packages can't be bumped yet due to constraints (usually a major/minor version bump that could break stuff). So you are safe to continue building the apk without worries.

And always feel free to open more discussions or leave comments if you're curious about anything else!

[solitudery]

Thanks for your input.

I installed java 21 and ran fvm flutter run, the build failed however, and there seems to be a license issue? I can't use Android Studio since I don't have the sys requirements, and I'm using Kate:

Checking the license for package NDK (Side by side) 28.2.13676358 in /usr/lib/android-sdk/licenses
Warning: License for package NDK (Side by side) 28.2.13676358 not accepted.

FAILURE: Build failed with an exception.

* Where:
Build file '/home/solitude/Grove/android/build.gradle.kts' line: 22

* What went wrong:
A problem occurred configuring project ':app'.
> com.android.builder.sdk.LicenceNotAcceptedException: Failed to install the following Android SDK packages as some licences have not been accepted.
     ndk;28.2.13676358 NDK (Side by side) 28.2.13676358
  To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
  All licenses can be accepted using the sdkmanager command line tool:
  sdkmanager.bat --licenses
  Or, to transfer the license agreements from one workstation to another, see https://developer.android.com/studio/intro/update.html#download-with-gradle

  Using Android SDK: /usr/lib/android-sdk

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 5m 40s
Running Gradle task 'assembleDebug'...                            341.2s
Error: Gradle task assembleDebug failed with exit code 1

So I installed sdkmanager and ran sudo sdkmanager --licenses which said "All SDK licenses accepted" with no prompts. Ran the build again and it still failed. After (perhaps regretfully) asking Claude Haiku 4.5 for the fix, it told me the issue was that I ran it as sudo which could've wrote it to the wrong location. I ran sdkmanager --licenses without sudo, still failed. I even wrote them manually.

Here's what Haiku said:

"You have licenses in ~/.android/licenses/, but Gradle is looking in /usr/lib/android-sdk/licenses/ (which is root-owned and only has apache-2.0).
When you ran sdkmanager --licenses, it accepted them but didn't write them to /usr/lib/android-sdk/licenses/ because that directory is owned by root and not writable by your user."

I'm thinking about deleting everything and starting over again.

[resurrectdev1]

I see, it does seem to be a perms issue, nothing actually looks broken I think the cause is /usr/lib/android-sdk being root-owned so sdkmanager --licenses can't write into <sdk>/licenses/, instead it wrote to ~/.android/, which Gradle doesn't want to read.

Try:

sudo sdkmanager --licenses --sdk_root=/usr/lib/android-sdk

If that doesn't work I would switch to a user-owned SDK so sudo's not a part of the problem anymore:

mkdir -p ~/Android/Sdk
export ANDROID_SDK_ROOT=~/Android/Sdk
export ANDROID_HOME=~/Android/Sdk

Add those to your ~/.bashrc, re-run sdkmanager --licenses, then fvm flutter run.

If it's still broken the simplest way would be to just fork the repo and let GitHub Actions build it, then grab the APK from the build artifacts. Sign it yourself after with apksigner/jarsigner if you want.

[solitudery]

I'm trying to translate Grove to another language, could I do that with an already built APK? Don't I have to modify some files in the code before building?

[resurrectdev1]

You can't add translations to the built apk so you would need to add new .arb files into the l10n folder in /lib and then add the changes in other files so it shows up there, are much better instructions in the CONTRIBUTING.md that go into depth with this process