Skip to content
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

[question]: OneSignal 5.0.0 did not collect location #747

Closed
1 task done
Suzven opened this issue Sep 19, 2023 · 2 comments
Closed
1 task done

[question]: OneSignal 5.0.0 did not collect location #747

Suzven opened this issue Sep 19, 2023 · 2 comments

Comments

@Suzven
Copy link

Suzven commented Sep 19, 2023

How can we help?

Hi! I updated the SDK version in my flutter application and get problem that the user's geolocation not collected. Prompt location request did not show

I tried:

  1. checked for isSharedLocation() - in response I received "true":
  2. Add to manifest permissions ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_BACKGROUND_LOCATION;
  3. add to build.gradle implementation of gms:play-services-location:21.0.1;
  4. rebuild project;
  5. tested it on 3 real devices and 4 emulators;
  6. downgrade to previous version 3.5.1 of flutter sdk - all works fine;
  7. added/removed the await modifier.

My code on screenshot:
Знімок екрана 2023-09-19 о 21 08 33

Screenshot from OneSignal Dashbord with examples of test installs:
Знімок екрана 2023-09-19 о 21 14 57

Code of Conduct

  • I agree to follow this project's Code of Conduct
@Suzven Suzven changed the title [question]: OneSignal 5.0.0 did not prompt location permission [question]: OneSignal 5.0.0 did not collect location Sep 22, 2023
@nan-li
Copy link
Contributor

nan-li commented Sep 25, 2023

Hi @Suzven, thank you for reaching out with your question.

Did you try setting location shared to true before asking for permission?

You likely need to call OneSignal.Location.setShared(true) before calling OneSignal.Location.requestPermission().

@nan-li
Copy link
Contributor

nan-li commented Dec 14, 2023

closing due to no response

@nan-li nan-li closed this as completed Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants