I have downloaded the Sqlite browser from the official website.
I installed it without any error but after I installed if I try to launch the SQLite browser it shows the following error.
The application was unable to start correctly(0x000007b). Click ok to close the application.
I have tried reinstalling it but the same error occurs.
Note:I am new here so if my question was not clear please ask for the details
I have found a fix for the above error. Using the nightly build of the DB browser which is available on their official site seems to avoid the problem.
Related
I want to automate test a basic Hybrid Mobile Application running in Android.I am able to launch the app in emulator but not able to enter the text in the login screen.
Getting error as
"Exception in thread "main"
io.appium.java_client.NoSuchContextException: An unknown server-side
error occurred while processing the command. Original error: No
Chromedriver found that can automate Chrome '53.0.2785'. See
https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md
for more details. "
Please help me resolving this!!!!!
If you see chromedriver.exe change log you will get the version you require for hybrid app automation. The browser used in your device have versin 53+
See this url http://chromedriver.chromium.org/downloads [check ChromeDriver 2.24 details] it says it supports browser with version 53+. Get this exe from https://chromedriver.storage.googleapis.com/index.html?path=2.24/
How to connect with Appium -
If you are using appium desktop, it gets installed as windows application in program files folder. Now location of chromedriver.exe it uses is as mentioned below.
C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe [This location may be bit different in your case]
Replace above location chromedriver from downloaded chromedriver.exe(from step2)
Note - Ideally automation should work without throwing exception. Incase still it doesn't work then try 1+ or 1- version of 2.24
You got everything you need in exception message:
Go here https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md
and read explanation on compatibility.
No Chromedriver found that can automate Chrome '53.0.2785'
Appium was not able to get chromedriver for your emulator that have Chrome 53.0.2785
So the first solution is to get Chromedriver v2.26 and add absolute path to binary as chromedriverExecutable capability:
1) download chromedriver_win32.zip from the link above and unzip
2) in your code add capability with the path to chromedriver.exe:
DesiredCapabilities caps = new DesiredCapabilities();
...
caps.setCapability("chromedriverExecutable", "/abs/path/to/chromedriver.exe")
If you get new emulator, first check what browser version is preinstalled and try to upgrade.
I am trying to publish the android app from SmartFace app studio and it is giving me an error to check logs. I am not sure where to find these logs. Publish to iOS works fine. Also I verified the android SDK is found in Project Details tab.
I have attached the screenshots here
This kind of publishing error can be caused by many factors. The ones that I know of are:
node.js that comes with Smartface is outdated, so you have to update it mannualy by going to its site and installing the latest version.
Sometimes Smartface says Java is found but it's not, so writing the correct directory could fix the issue.
I have been working on a browser plugin for windows which involves displaying camera output in browser. Presently I'm working on Windows 7. After plugin installation, I want to start the plugin immediately without restarting the browser. I noticed that as soon as plugin is registered, it started working in Google Chrome Version 24.0.1312 as well as in Internet Explorer 9. But it fails to do so in Mozilla Firefox 18.0.1. Can anyone help me solve this problem of restarting the browser after plugin installation. And will this problem occur in MacOS as well?
Thanks
You need to do a navigator.plugins.refresh(false); in javascript to tell the browser to rescan the plugins.
Explore /Installer/js -folder in FireBreath sources
I thank you all for reading this lengthy question. It's really important and I will appreciate it if you can assist me :)
The problem -------
I am have been using the Windows 7.1 SDK for about two months now. The emulator has worked without any problem so far. However, today, it began displaying this error (The saved state (Name of File).dess is corrupt. Please delete the corrupted saved state file and then retry). I had not made any significant changes to my project code, or moved any files. I had just added some Visual State animations for a button.
As it suggested, I went ahead to delete the file. I then started debugging again. However, the emulator now opened and displayed the message (Windows Phone Emulator is doing a complete OS reboot). This message was displayed for a very long time. I closed the emulator and project. Since then, I have been unable to use the emulator. I am able to code normally in Visual Studio, but I cannot test my application.
What I have tried ------
I read up on this issue and found many others who faced the same emulator issue. Following their suggestions, I have run one repair of the Windows Phone SDK 7.1. I have also tried uninstalling and then re-installing the SDK 7.1 once.
System Specifications -----
I am using Visual Studio Express 2010 for Windows Phone (Windows 7 64 bit)
I have downloaded the Windows Phone SDK 7.1 from this link: http://go.microsoft.com/fwlink/?LinkId=258412
I have read that this issue might be because of some hardware incompatibility. However, I think my machine is compatible with the emulator. Here is some information.
DirectX Version: DirectX 11
8GB RAM
Driver Model: WDM 1.1
Additional Information:
I have read that installing the 'January Update' might fix this issue. I tried downloading the update from this link: http://www.microsoft.com/enus/download/details.aspx?id=23854
However, the installer said that the update is not compatible with the product/version of the product I am using.
Usually the Repair function of the WP7.1 SDK is enough to fix all the issues. It runs the generation of the saved state of the emulator again.
Please try to delete files in %ProgramData%\Microsoft\XDE folder first (make sure you backup them somewhere else.), then run the emulator. If the emulator runs with a message "Windows Phone Emulator is doing a complete OS boot," let it boot. It takes some time though. This way you will know that the emulator actually can run on your computer. This won't generate a new saved state image, but the emulator should at least load.
Next, try installing WP7.1.1 SDK update from http://www.microsoft.com/en-us/download/details.aspx?id=29233. This update also installs additional 256MB emulator image besides the original 512MB image. It also generates emulator's saved states in the process, potentially fixing the issue.
If everything fails, then try these instructions to fix the saved state of the emulator:
Uninstall WP7.1 SDK
Manually delete these folders:
%ProgramData%\Microsoft\XDE
%LocalAppData%\Microsoft\XDE
Install WP7.1 SDK again.
Install WP7.1.1 SDK update: http://www.microsoft.com/en-us/download/details.aspx?id=29233.
Edit:
Btw, have you tried to reboot your computer? Once this fixed the issue for me.
Alright, I managed to solve this problem.
I reinstalled Windows and downloaded the SDK 7.1 again. The emulator works fine now!
#Paulos, thanks for helping!
I had the same problem for a long time. Try this:
Start up Visual Studio 2010, but before you start debugging, click on the tabs of all the open pages so that all the xaml pages and code behind pages can load.
I noticed it when I opened Visual Studio, but the first open page was a code behind page and not an xaml page, so when I first clicked on the tab of a xaml page, of course, it took some time to load the xaml page into the editor. However, when that and one or more open xaml pages were also loaded, the emulator started without the error message.
I am creating a simple app using Eclipse and Blackberry JRE 7.0 as per the example given at:
http://docs.blackberry.com/en/developers/deliverables/11958/Configure_a_browser_field_825671_11.jsp
I am trying to load a simple HTML page hosted on a remote server inside browser field in the app.
When running the app on 9930 Simulator I always get the error 'Local connection timeout after 120000 on simulator'. The same remote page shows up fine on the web browser of the same simulator..
I am making sure to start the MDS simulator.
The same link shows up fine in simulator browser. Its only when using browserfield, I am having the problem.
I get the folling error when clicking the icon to launch the app:
Error displaying content for: http://yahoo.com
Error message: java.lang.runtimeException:ApplicationRegistry:waitFor
(0xd0fe7d7338fourd7f0d) timeout
....
On waiting further I get the 'Local connection timeout error..
I know that in Android one has to enable internet connection when using the webview in the manifest file - is there any similar setting one has to do in blackberry?
I tried to run the BrowserField demo app on 9930 (JRE 7.0.0) and encounter the same issues as you did. On the other hand, the demo worked fine on 9800 (JRE 6.0.0). I tried again on 9930 and noticed that though I definitely enabled MDS (enabled the 'Launch Mobile Data System Connection Service (MDS-CS) with simulator' in the Run/Debug Configurations in Eclipse), the MDS window didn't appear which seemed very strange.
I googled a little and found this post on BlackBerry's forums. According to this post:
An incorrect version of MDS-CS simulator was included in 7.0. To correct it you can delete it and copy the version from 6.0.
Well done, RIM!
Then, I deleted the MDS folder from JRE 7.0.0 and copied the one from JRE 6.0.0 as described in the aforementioned post. Closed and rerun simulator and voilà, the MDS window appeared. Rerun application, and everything worked like a charm!