Skip to content

Build Issue #5701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 2 tasks
Adventure-Hunt opened this issue Apr 17, 2025 · 4 comments
Closed
1 of 2 tasks

Build Issue #5701

Adventure-Hunt opened this issue Apr 17, 2025 · 4 comments
Assignees
Labels
closed: not a bug The behavior is correct/expected.

Comments

@Adventure-Hunt
Copy link

Adventure-Hunt commented Apr 17, 2025

Can we access your project?

  • I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Unable to build project. No idea how to resolve this error. No changes have been made to geolocator related functions.

Project ID: adventure-hunt-litdk0

Error Message

/opt/.pub-cache/hosted/pub.dev/geolocator_android-5.0.1+1/lib/src/types/foreground_settings.dart:122:23: Error: The method 'toARGB32' isn't defined for the class 'Color'.

  • 'Color' is from 'dart:ui'. Try correcting the name to the name of an existing method, or defining a method named 'toARGB32'. 'color': color?.toARGB32(), ^^^^^^^^ Target kernel_snapshot_program failed: Exception

FAILURE: Build failed with an exception.

  • What went wrong: Execution failed for task ':app:compileFlutterBuildRelease'.

Process 'command '/sdks/flutter/bin/flutter'' finished with non-zero exit value 1

  • 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 1m 16s Gradle task assembleRelease failed with exit code 1


Expected Behavior

I expect the project to build without this error.

Steps to Reproduce

  1. Try to build APK

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4wl/H605NOmN8B15DtbcJKmiURMjs8aI0vie5TYCs/CZjnPOwidvfOSFhdZ8OrdkFUOmD9r3w13MLWm9z1FO06YByBbKo41bt1EzzLeHmuVYypC5eWY3FUGshUCEy616SZuxN/CPJ1SV4DwV6PNeutQhDaHrH1PjIBIvGlBNrXmAfuQ0SLb3kNh1JWeC/v

Visual documentation

Error message is above.

Bug report code is not relevant as its a build error.

Environment

- FlutterFlow version: 5.4.0
- Platform: Windows
- Browser name and version: Chrome  135.0.7049.85
- Operating system and version affected: All

Additional Information

No response

@Adventure-Hunt Adventure-Hunt added the status: needs triage A potential issue that has not been confirmed as a bug. label Apr 17, 2025
@Juansarmi Juansarmi self-assigned this Apr 17, 2025
Copy link
Collaborator

Hello! I'm sorry you're experiencing this issue.
It seems that the error is occurring because the geolocator dependency is trying to access a method (toARGB32()) that was introduced in Flutter 3.29, which is not available in the version of Flutter used by FlutterFlow (3.27). I recommend using an older version of the geolocator dependency that doesn't rely on this method.

Captura de pantalla 2025-04-17 204042.png

I’m also providing a link to an open issue in the geolocator dependency that may offer further information on this error: Baseflow/flutter-geolocator#1688 (comment)

Regards!

@Juansarmi Juansarmi removed the status: needs triage A potential issue that has not been confirmed as a bug. label Apr 17, 2025
@sandpat
Copy link

sandpat commented Apr 17, 2025

Some of very basic dependencies are gone:

Image

Obviously the code is not compiling!

@sandpat
Copy link

sandpat commented Apr 17, 2025

I had to manually add file_picker and firebase_storage. I would hope that storage is a basic feature that flutterflow supports. It should be bundled automatically as it is used in configuration as well.

Copy link
Collaborator

Hi there! I'm glad to hear you've found a workaround to resolve this issue. Since it's been solved on your end, I'll go ahead and close the ticket.

If you need further assistance, feel free to reach out.

Best regards

@Juansarmi Juansarmi added the closed: not a bug The behavior is correct/expected. label Apr 18, 2025 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: not a bug The behavior is correct/expected.
Projects
None yet
Development

No branches or pull requests

3 participants