I had this working before moving to iOS 11, but now the queries are not returning. I had thought this might have something to do with Core Location, and have also been setting breakpoints. But, so far, I'm not seeing anything that would have changed for HealthKit with iOS 11. Does anyone reading this have suggestions for other items to check?
Related
We are building a kiosk app and noticing some odd behavior with Google Chrome. To debug, we are monitoring all of the incoming events with monitorEvents(document); through the dev console and noticed 2 different kind of scenarios.
Eventually after a few minutes of heavy multi-finger/gesture use, we are stuck in a touchstart/touchend loop where touchend does not propagate down to a mouse/click event (breaking our app as we only handle onClick). It is continuously stuck in touchstart-touchend-touchstart-touchend for every finger click.
A continuation of scenario 1 with heavier use, we are getting absolutely no events in the console, not even a touchstart.
We are using Chrome 62 with Windows 10 with the following flags:
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --kiosk --incognito --disable-pinch --overscroll-history-navigation=0 URL
We have tried to add --touch-events, add --disable-gpu, remove our previous flags, but still facing the same issue. It seems to be an issue between Chrome and Windows as we are able to replicate it on google.com (with getting no events). When we plug in a mouse, we are able to click the buttons so the app is not frozen, we are just not getting any touch events (only mouse works at this point). Touch is still working on the Windows and Chrome App level, just not our app viewport.
The kiosk is a Dell All-in-One machine. Has anyone else experienced this kind of issue?
Thanks!
UPDATE: Using Chrome 68+ I no longer have this issue. I have not tried versions between 62 and 68 to see where it was fixed but I am glad that it is!
It is a little late now, but maybe this will bring some closure. I experienced the same problem and like you, only in Chrome. The best I could determine was that this glitch is dependent on a particular model of touchscreen in the computer.
Check the hardware IDs for the touchscreen in Device Manager. Only the Inspiron 20-3059 models with a touchscreen made by Advanced Silicon (VID_2149&PID_4C39) exhibit this behavior. Other 20-3059 models with a different touchscreen model (VID_0457&PID_1192) work fine.
Oddly enough, later Inspiron 20-3064 models also work fine, though they also had Advanced Silicon touchscreens. The PID was increased to 4C3E so perhaps they discovered this issue and fixed it for the newer model.
I wasn't able to find any combination of driver/firmware/Chrome versions that would fix the problem, but this is as close to a root cause as I could get.
I'm having some trouble with WebExtensions in Firefox. I've got some code to track downloads, and it's working in Chrome, but not in FF.
I've boiled the code down to the minimal surface that works in Chrome but not FF:
function handleChanged(delta) {
console.log(delta);
}
chrome.downloads.onChanged.addListener(handleChanged);
Whether I use chrome.* or browser.*, the behavior remains the same: it doesn't work. I've tried executing this line:
console.log(chrome.downloads.onChanged.hasListener(handleChanged));
After adding the listener, and it does log a value of true. Oddly enough, adding an onCreated listener works just fine:
function handleCreated(delta) {
console.log(delta);
}
chrome.downloads.onCreated.addListener(handleCreated);
This yields the expected object dump in the console when a download is started. Unless I'm missing something extremely obvious, I'm inclined to think this is a bug. It is not mentioned to the incompatibilities list, and it is documented by Mozilla. The thing is, I don't see anybody else asking this question online, so I'm inclined to think a bug is unlikely and I'm messing something up.
If it helps, I'm running Firefox 51.0.1 (32-bit) on Windows 7 Enterprise x64 inside of VMWare Workstation on a Windows 7 Enterprise x64 host. I'm loading the extension using the "Load Temporary Add-on" button. It's not a problem with the core manifest or add-on itself, because three other types of listeners are working just fine. The script is running as a background script.
I appreciate any guidance. Thanks!
My application is crashing sometimes while running on real device but the debugger always goes to "main.m" class not where the app is exactly crashing.
Infect console log is also not telling anything about the crash.
I think there is some settings required for debugger but not exactly know the right solution for that. Please help.
Check your device logs for an app type of Unknown. Often, an app will crash by being killed by the OS and an unknown log entry will appear on your device logs showing that your app is the largest memory consumer. To figure out which piece of code is causing the crash, evaluate the UI behavior and add a breakpoint at the appropriate spot (probably where you start working with your data).
Perphaps this could be a memory issue. In that case debugger does not show warning or exceptions. you can use instruments like profile provided in xcode to backtrace the issue. You can also backtrace your issue in Report navigator in xcode.
You can also use apps like crashlytics. Upload your build to crashlytics and then download it from theer and use it. Once it gets crashed .Login on web and check for the crashes. It will show the exact line where got gets crashed.
I hope it can help you.
Im trying to make apps and always when I set the elements in the xib, it looks fine, then I open the simulator running 6.0 and some elements appear lower than they should, or some are a bit bigger than in the xib.
Why is this? I unchecked the "Use Autolayout" and still it appears in a different way.
Any idea?
I am trying White for the first time. I tried to run a sample test to get a window of notepad, it doesnt seem to work. Here is what I did:
//Launch the app
Application app = Application.Launch("notepad.exe");
//Get the main window after launching the app
Window win = app.GetWindow("Untitled - Notepad");
This last line throws an error as type initializer exception. When I go into the source code for White, it fails at finding the window.
When I used GetWindows() and try to get first window, it works fine.
But the same error is thrown for the child objects as well.
I have Win7, 32 bit. By build configuration is Debug|x86. I also tried the same code on Win XP, 32 bit and it worked well.
Can anyone please tell me how do I go about this.
I think I found the solution. When I tried running same code on a Win 7, 64 bit machine, it seemed to work perfectly alright.
I tried using the dependency walker and found that there is some issue with the dlls on my machine. Though I dont think I can get my system fixed just for that, I guess it might help others if they are facing this issue.