We have a Kiosk app which runs on Chrome Kiosk mode and is written in React JS. But for some of our Kiosk machines (All of our machines are Windows machines), it seems to be crashing regularly (Approx. %4 of the devices) without any user input or fixed time between crashes.
I reviewed the code several times but never found any background tasks running, or any reason for the Chrome to crash at all.
Because the crashes are irregular, I cannot connect to a problematic device and wait for it to crash for hours to debug the process. And because the app is automatically started via a VB script when Windows is started, the clients often "solve" the crashes by restarting the Kiosk machine, which is time consuming and leads to tons of complaints.
So my questions are;
Can I somehow force Chrome to restart, or lets say Go to first page in history if it crashes?
Can I catch errors globally without using ErrorBoundries in JavaScript (It is already implemented and is used for other things)
I tried using --remote-debugging-port=9222 to use Developer Tools, but I need to be connected to the machine and go to localhost:9222 port manually to use this and cannot afford to be connected to the device all the time. So is there a way to connect and use Developer Tools on 9222 port remotely?
I tried saving console logs to a file (using Chrome Command Line Arguments) but never saw any "Errors" on the list, so is there any arguments to help me save crash logs to a file to inspect them after the crash?
Thanks for all your help.
After using sometime App crash on User Device which I don't have access to it. I have read the blog about using the CN1Libs-NativeLogsReader to see the error occurred on remote devices. I would need some help on how to use it for this kind of issue for debug builds. Please advise.
That won't save you from a crash as that would be too late in the game.
You can use the API to get the native log but you can't use it to catch a physical crash.
I've just unpacked my new Pico Pro Maker Kit and started flashing procedure. After creating a product in AndroidThings platform and downloading the build I've started flashing procedure.
Command flash-all.sh failed on fastboot syntax, so I've build that manually and found that it was failing on part "set_active _a". I've skipped that and continued to flash device.
Now device is rebooted, I can see on the screen androidThings logo and version + info about network status ("not connected").
I'm unable to find this device in
fastboot devices
or
adb devices
so it looks like I have no way to connect into it.
Do you know a way of fixing that? Is there any way to force fastboot reboot on that device?
Thanks!
I had a related problem for IMX7 on initial install, I thought I'd pass along the Boundary feedback in case it helps. Tech support at Boundary devices recommended that I try the following:
Please try to add androidboot.dm_verity=disabled and
androidboot.selinux=disabled options to bootargs.
I presume these would be options you'd set at the boot prompt ==> (from the serial connection) but I haven't had a chance to test, which I may get to next week. Interested in your feedback if this has any impact to your situation in the meantime.
I tried all the the different stuff. But its not working. Its something general to linux. I have tried it in Arch Linux and now I have installed Ubuntu 12.04 beta2 also its the same there. I am trying to connect my Samsung mobile phone to my ubuntu box for gprs, buts its not working. I have tried bluetooth and usb both. It pairs fine with bluetooth but on using DUN service or browsing file etc.. it just crashes ... like the phone is not responding to its requests. I have upgraded the kernel to 3.3 from ubuntu PPA. Thought that might solve the problem. But its the same. I have downloaded blueman from another PPA. Which also finds phones, gets paired but whenever I try to browse file, send file or use DUN it says my phone is not responding. I have tried mannual rfcomm bind 0... stuff it creates a /dev/rfcomm0 and when you cat > /dev/rfcomm0 it communitcates with phone and asks for pin code etc... but when i do pppd... chat dailing ... logs says the same no response from my phone. Please guide me ... what should I do. Just for the info. Phone works fine on windows. I am using it right now. Regards
You shall try this project: Android File Transfer For Linux
I have registered my Phone 7 app as a Share Picker Extension. It works—my app is in the list of Share options and it gets launched and I can load the chosen image. Okay, great.
But then things go wrong in my code. I would like to be able to debug the issues, but I can't seem to keep the debugger attached.
I cannot debug this in the simulator, since the Pictures app (and thus the Share Picker functionality) is not present in the simulator.
I cannot debug this on the phone because as soon as I pick my app from the Share list, the debugger detaches... right as my app is "launching" again.
Is it possible to attach the debugger to a running WP7 app? Is it possible to keep the debugger attached? Am I doing it wrong? Any suggestions, advice or guesses are welcome because I'm tearing my hair out.
When doing M+V hub integration (sorry, haven't done any pictures hub integration yet) I initially used a crude debug technique (Messagebox.Show, etc. - like Justin mentioned) to verify what was being passed to the NavigationEventArgs of OnNavigatedTo and wrapped the whole method in a try..catch block to learn what was going on. I then refactored the code when I knew what could be expected. (Remember OnNavigatedTo will be called when your app is launched normally too and so e won't be populated in the same way.)
When the app is launched from a/the hub it creates a new instance of the app and there is currently no way to connect to this for debugging while the main page is being navigated to.
Great question. I'm unsure if that's possible. As far as I know, there's no way to attach the debugger to when the WP7 O/S starts an app (which wasn't triggered by the debugger).
Photo Share picker extensibility, music+Video hub extensibility and other O/S extensibility points seem to not play nicely with the VS debugger. Normally I resort to MessageBox.Show to debug any problems with WP7 O/S integration.
1) Connect the Device
2) Turn off Zune
3) Start C:\Program Files\Microsoft SDKs\Windows Phone\v7.1\Tools\WPConnect\x86\WPConnect.exe
To properly debug your application that uses the Media Library, you'll need to use the Windows Phone Connect Tool (WPConnect.exe) as described on MSDN. Jaime has some additional tips on his blog.
Once you are connected, you should be able to debug your application. Fingers crossed anyway. If that doesn't help, I'll dig a bit further.
It's not so much about the WPConnect tool. The nature of your application means that you have to have it closed and the user should pick a photo. Only after that the data is returned to the application.
You should read about the application execution model on Windows Phone 7. Also a good explanation is available here.
Initially, I would say that you should look at tombstoning (a good explanation here) but then again, the image returned will re-start the app and won't allow you to directly attach the debugger.
Yeah, looks like this is impossible...
All the answers above seem to be missing the point: I presume you're able to debug your app in the "standalone" mode (when it's launched normally), but not when it's launched via the Share Picker Extension. Am I write? This is the wall I'm hitting... :-(
I thought the proper way would be to attach to the process once it's launched.
I tried to use Debug > Attach to Process, then select Smart Device as the Transport and Windows Phone Device as the Qualifier... But in return I get the ugly "Unable to connect to 'Windows Phone Device'. Not implemented" message.
Bummer :-(