Build on and support Android 12 (SDK 31).

[PieterAelse]

Fixes #639
Fixes #702

[PieterAelse]

@Lyokone Could you have a look at this PR and get it merged? In order to support Android 12!

[chedwin41]

Hi @Lyokone, could you have a quick look to this PR ? This is the only package left so I can migrate my app to Android 12.
Thanks a lot !

[PieterAelse]

@Lyokone any updates on merging this PR to unblock everybody from building on Android 12?

[magnuswikhog]

@Lyokone Any plans to merge this pull request in the near future? This issue is really blocking a lot of app releases.

[rubenaster]

@Lyokone any updates on that current topic? Can we help? Unfortunately this prevents Android 12 devices from running the application.

[note11g]

@Lyokone Please merge this PR....

[PieterAelse]

Did not try it myself, but in the mean-time maybe everybody who is blocked can use the following:

dependencies:
  flutterlocation:
    git:
      url: [email protected]:pieteraelse/flutterlocation.git
      ref: build_on_and_support_android_12_sdk_31

Source: https://dart.dev/tools/pub/dependencies#git-packages

[carloserazo47]

Did not try it myself, but in the mean-time maybe everybody who is blocked can use the following:

dependencies:
  flutterlocation:
    git:
      url: [email protected]:pieteraelse/flutterlocation.git
      ref: build_on_and_support_android_12_sdk_31

Source: https://dart.dev/tools/pub/dependencies#git-packages

Thanks @PieterAelse, it works well with your fork but you have to set the path as well:

dependencies:
  location:
      git:
        url: https://github.com/PieterAelse/flutterlocation.git
        path: packages/location
        ref: issue_639/build_on_and_support_android_12_sdk_31

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[PieterAelse]

@Lyokone trying to unflag as it's not stale

[lukaskurz]

How is this still not merged? Nearly half a year since the creation of the PR has passed, without any direct feedback of the maintainer @Lyokone . I understand that they are in the process of a new major version, but I think merging code from the community should still be possible in the meantime. I would greatly appreciate it (and I'm sure others would too), if you could quickly take a look at this and merge it.

[akhatriST]

@Lyokone Any chance of the PR getting merged of the fix?

btw How is everyone tackling this issue?

[lukaskurz]

@akhatriST I just forked the repo, merged the contents of all the PRs which were needed and use that repo for now.

[xunreal75]

Can you try to contribute your fork. The package has no changes since 3 months. Doesn’t know whether package is orbaned orphaned/abandoned Thanks

…

Am 08.09.2022 um 09:46 schrieb Lukas Kurz ***@***.***>:  @akhatriST I just forked the repo, merged the contents of all the PRs which were needed and use that repo for now. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

[Cotspheer]

@Lyokone any chance to get this merged?

[PieterAelse]

@bartekpacia Since you closed #639 in favor of #702 (a newer issue? but okay..), could you review this PR to get it merged?

[bartekpacia]

Will take a look at it soon and hopefully merge

a newer issue? but okay..

I was just trying to clean up the repo, many issues had often ~5 duplicates, so I wasn't really looking which one was newer

[bartekpacia]

The build is failing.

[PieterAelse]

@bartekpacia Looks like the main change of my PR is already done on master now: 187734c

Maybe this PR can be closed, if you agree.

[bartekpacia]

Yeah, looks like it. Sorry for that coincidence, I just wanted to release the fix asap. Thank you for the contribution nevertheless!