0.8.1, Failed Integration with flutter_background_service

[Alecckie]

In version 0.6.0, it was possible to integrate background_location and flutter_background_service to be able to achieve location updates even when the app is closed, a service that is very vital in taxi apps. Flutter background service allows registering of plugins that you'd want to run in the background in a separate thread hence working even when the app is closed.

From version 0.7.0 upwards to the current 0.8.1, background_location no longer works with flutter_background_service meaning that once the app is closed using the back button, then background_location no longer updates the location like it was in 0.6.0.

I'm not sure if this is really an issue that @Almoullim would be interested in sorting but a combination of these 2 plugins was really helpful especially for us with live apps making use of the 2.

[lbaey-mobizel]

I experience the very same issue. Downgrading to 0.6.0 solved it.

[eduardo-and]

Same problem when used with workmanager...

[jesussmile]

Hey guys any solution ?

[bulgarian-beast]

Same problem.
Everything works until I kill the app, when the app is killed all continue to log except the call to this package.
Any idea ?

NB: Downgrading to 0.6.0 don't solve the problem @lbaey-mobizel, can you add details ?

[MoralCode]

seems similar to #139 (even though this isnt related to firebase)

[jesussmile]

@MoralCode is this package going to be actively maintained ? A lot of users have moved on

[MoralCode]

@MoralCode is this package going to be actively maintained ? A lot of users have moved on

It's hard for me to say since I'm still pretty much an outsider to this project. I can't personally promise that ill maintain it (although I've been doing my best to help out in response to the maintainers call for assistance in #188) and since I don't know @Almoullim personally, I can only point to that issue as evidence to suggest that the answer, realistically (and probably for the last little while as well), is/has been "probably not, unless something about the current situation changes".

Maybe I've been watching too much content from open source conferences lately, but if enough people who depend on this are able to help out instead of switching away, then that might help the project, but if a lot of users have just moved on like you mention then it seems like there won't be much incentive/recognition/support .etc left to encourage any maintainers or contributors to justify continuing to give their limited time and effort here when it seems like people are finding acceptable alternatives on their own.

In the end I think its up to Ali to say what would be needed to keep this going or find an alternative to recommend to existing users. Ali - if you're reading this - thank you for your years of service to this project and for your honesty in reaching out to ask for help. While I didn't get much chance to really use this library a lot, the number of issues on this repo suggests that it provided some value to a lot of people and projects and I hope you find a resolution to the circumstances that prompted you to reach out.

[jesussmile]

@MoralCode Ah! well good luck but there seems to be some fundamental issues with this package, i have personally moved on to this https://pub.dev/packages/background_locator_2 . You can look at this package and try to fix it. This package was really good while it was working. Perhaps you can look into the package i mentioned and try a fix ? It will be too much for me to go back to this project.

[MoralCode]

there seems to be some fundamental issues with this package [ ... ] It will be too much for me to go back to this project.

I would love to learn more about the issues you were having as far as you remember, especially if they were bad enough that it makes migrating back difficult. Can you point to any currently open issues (or file any new issues) that relate to the things you experienced?

https://pub.dev/packages/background_locator_2 . You can look at this package and try to fix it. [...] Perhaps you can look into the package I mentioned and try a fix ?

I took a quick look and it seems as though that package is a fork of a different (and also unmaintained) location package that doesn't share any history with this repository. Comparing every difference in design/architecture and features of these two packages seems like it would require a large amount of time and effort, even moreso without knowing which specific issues to look for resolutions to. Could you point me to any specific part of the package you linked that you think this package could do better?