background_locator: Build fails after upgrade to flutter 3.0

Hello,

just wanted to let you know that there seems an issue with the latest flutter release 3.0 and this plugin.

After upgrading my flutter the build of my app using background_locator 1.6.12 gives following errors:

background_locator\android\src\main\kotlin\rekab\app\background_locator\BackgroundLocatorPlugin.kt: (25, 1): Class 'BackgroundLocatorPlugin' is not abstract and does not implement abstract member public abstract fun onNewIntent(p0: Intent): Boolean defined in io.flutter.plugin.common.PluginRegistry.NewIntentListener

background_locator\android\src\main\kotlin\rekab\app\background_locator\pluggables\InitPluggable.kt: (22, 55): Type mismatch: inferred type is BinaryMessenger? but BinaryMessenger was expected

Best regards Thomas

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 6
Comments: 24

Most upvoted comments

https://github.com/imsamgarg/background_locator

try it, fixes all flutter 3 issues

imsamgarg on May 16, 2022

I’m getting this issue when I run it in the emulator:

Running Gradle task ‘assembleDebug’… e: D:\develop\flutter.pub-cache\git\background_locator-08beb61507f472de767fa918365fa2601c879c63\android\src\main\kotlin\rekab\app\background_locator\provider\LocationParserUtil.kt: (21, 20): Type mismatch: inferred type is String? but Any was expected

FAILURE: Build failed with an exception.

What went wrong: Execution failed for task ‘:background_locator:compileDebugKotlin’.

Compilation error. See log for more details

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 17s Exception: Gradle task assembleDebug failed with exit code 1

casva2022 on Aug 9, 2022

The @imsamgarg solution did it!

Added in pubspec.yaml

background_locator:
    git:
      url: https://github.com/imsamgarg/background_locator
      ref: master

guistrutzki on Jul 16, 2022

Just in case someone is experiencing the same issue. Seems that the fork here has already a fix for this problem!

stingrayx on May 12, 2022