isawake | biggest crowdsourced database of people

Stumbled upon a blog that identified a solution that works. https://faithlife.codes/blog/2008/07/casting_delegates/

Excerpt from blog: "Fortunately, it is possible to cast between arbitrary delegate types, though it isn’t as efficient as you might like."

I figured out how it works now and will update the code accordingly. Maybe someone will find it useful.

put Target framework to the latest and the minimum is version 16

right click on Android project then go to options make sure that Release mode in linker tab and choose link SDK Assemblies only

save all changes then clean all solution , close the project and visual studio

go to folder of project then delete bin, obj folders

open visual studio , and try to start deploy project in release mode

When app is closed and not running in background then location never track in iOS 11 it's not an iWatchOS 4 and iOS 11 Bug.

Changes to location tracking in iOS 11

follow this documentation link: Changes to location tracking in iOS 11 iOS 11 also makes some major changes to existing APIs. One of the affected areas is location tracking.

If your app only uses location while the app is in the foreground, as most apps do, you might not have to change anything at all; however, if it’s one of those apps that continuously track user’s location throughout the day, you should probably book some time this summer for making some changes in how you do the tracking and testing possible usage scenarios.

For example, let’s consider those two apps again; the continuous background location and the significant location change monitoring app. Suppose the user goes for a run with the continuous background location app. They’ll go on the run, they’ll come back, they’ll see the solid arrow the whole time, and when they look at their map, they’ll see every twist and turn they took. When they install that app that uses significant location change monitoring, they’ll see the same thing, a solid arrow. As far as the user is aware, this app is probably receiving the same amount of information as their run tracking app. So if users are misinterpreting our signals, we decided the best way to fix this was to adjust how we indicate location usage.

watchOS has access to many of the same technologies found in iOS apps; however, even if a technology is available, you may not be able to use it in quite the same way you did on iPhone.

Do not use background execution modes for a technology. In general, Watch apps are considered foreground apps; they run only while the user interacts with one of their interfaces. As a result, the corresponding WatchKit extension cannot take advantage of most background execution modes to perform tasks. might be help this documentation: Leveraging iOS Technologies for watch

When you use MyProcess.BeginOutputReadLine(); you should not be calling MyProcess.StandardOutput.ReadToEnd();. Also you can't call MyProcess.WaitForExit() either, that will lock up the program.

What you should instead is subscribe to the Exited event. However I believe the event will be raised on a background thread so you will need to use some other mechanism to tell the UI that it is done reading because you can't directly talk to components from threads other than the UI thread.

What I recommend is you use WaitUntil to watch a variable and you set that variable when Exited has fired.