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

Geolocation Unautoirized Access in Background Task #807

Closed
rg-burton opened this issue Dec 9, 2017 · 4 comments
Closed

Geolocation Unautoirized Access in Background Task #807

rg-burton opened this issue Dec 9, 2017 · 4 comments

Comments

@rg-burton
Copy link

Downloaded the November Update of samples and ran the Geolocation Sample. Using the Background task always gives a disabled (Unauthorized Access) with Windows Insider Build 17046. Has been doing this on the last several Insider Builds. I also have another UWP app I have been using for over a year that gives the same error on these builds. Both the Geolocation Sample and my program work fine on Build 16299.

The Sample app shows Disabled in the background location sample and setting a breakpoint in the background application in Visual Studio shows it getting the Unauthorized access exception.

capture
capture1

Using November Sample Update C# version of Geolocation
Using Insider Build 17046
Visual Studio 15.4.5
Location Permission is given to sample app when run and verified in Location settings.
PC has default location set in settings as well.

@RealCaptainJ
Copy link

Sounds Good!

@oldnewthing
Copy link
Member

I've asked the feature team to investigate.

@Cheoljin
Copy link

This is from the feature team.

@rg-burton are you still having this issue?

I have tested this with a recent Insider build, i.e., 17080. rs_onecore_sigma_dplat (as of 01/17/2018), but it does not have the issue. It successfully registers the background task in the sample app.

On the other hand, there was a similar report before around this build number, and it has been resolved afterwards: #786

If you have this issue now, please add your comment and contact info (email etc) with build edition (e.g. Enterprise), number, and branch (rs_prerelease).

@rg-burton
Copy link
Author

It does appear to be resolved with the current insider build I have which is 17074.

Thanks for looking into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants