I upgraded the nightwatch version to 2.6.8 and tried to run . But the problem is the window size was not maximized . I used below API command to maximize window
Browser.windowMaximize.
Error is mulitiple entries with same key : windowHandle= current and windowHandle = current.
Any one help me on this how to resolve this issue.
I am expecting to maximize the window with nightwatch latest version 2.6.8
Related
I'm running into 2 issues that I'm not sure how to solve regarding validating apps to publish to the Mac App Store.
A new Version of iTMStransporter is available on the early-access update channel. Specify '-updateChannel earlyAccess' on the command line to test it out.
---Irrelavant issue about sandbox---
Your version of iTMSTransporter will be updated in approximately in 2 days.
I have looked into the App Store and I have not found anything that seems relevant. Executing that command returns command not found: -updateChannel
This solved my problem:
Open terminal
navigate to /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/Current/itms/bin
Fill in ./iTMSTransporter -updateChannel earlyAccess in the cmd
Use transporter
I'm usingn Aptana Studio 3 on Mac High Sierra. I have imported my Rails 5 project and set "Rails" as my project natures in the "Properties" section of my project. However when editing some Ruby files, Aptana is incorrectly reporting syntax errors on the left side of the editor. For example, this line
creds = PasswordService.find_user(params[:login])&.object
is flagged with this error
syntax error, unexpected tDOT
even though this doesn't raise any errors when I run my project. I'm wondering if Aptana is not picking up the correct version of Ruby associated with my project but I'm not sure how to check/set that.
I don't use Aptana, but maybe you want to set your Ruby version too because the safe navigation & is a Ruby feature.
In the project directory run ruby -v in the console and check the ruby version, it must be higher than 2.3.
If you use a ruby version manager (rbenv or rvm) make sure you configure the right Ruby version for the project.
Is studio3-ruby the plugin you're using?
If so, I found this open issue that seems related to Ruby 2.0 support:
https://github.com/aptana/studio3-ruby/issues/8
I am trying to run an example from the plexe-veins folder on my Mac OS High Sierra system, to my knowledge I have installed all necessary libs.
The only problem I have is with installing the omnetpp__0.7-1.tar.gz file. Some research online leads me to believe the version of R on my computer is unable to compile the file since the file is an older version. I have tried installing older versions but failed because of compatibility issues with my OS. I am at a complete dead-end with regards to that.
When I run the platooning example, the GUI opens up of and I am able to run the simulation for a few seconds until I get the error:
(omnetpp::cDoubleParImpl)simulationDuration: Cannot cast from type
double to integer -- in module (SimplePlatooningApp)
scenario.node[0].appl (id=11), at t=1.01s, event #204 TRAPPING on the
exception above, due to a debug-on-errors=true configuration option.
Is your debugger ready? ./run: line 2: 90810 Trace/BPT trap: 5
../../run "$#"
The version of omnet I installed is omnet++-5.4 and I also followed the procedure from the manual which includes the "./configure" and "make" commands. I run the example by entering the dir in question and run:
./run -u Cmdenv -c Sinusoidal -r 2
It appears my problem was multi-pronged. These are the steps I took to solve the problem:
I followed the suggestions offered by Julian with regards to the version of Omnet++ I installed, I downgraded to Omnet++ 5.0
I also noticed that I had a previously installed sumo (not plexe-sumo) on my system and thus it seemed to be running the simulation instead of plex-sumo. So I uninstalled it.
There also seemed to be a problem with a static declaration of 'abs'followed by a non-static declaration which caused omnetpp_0.7.1.tar.gz to fail while compiling. I solved this issue by locating the stdlib.h file in xcode.app/Contents/Developer/Toolchains/usr/include/v1 and commented out "inline _LIBCPP_INLINE_VISIBILITY" (there should be a better fix).
I appreciate the help!!!
The part of OMNeT is a casting error. This is due to OMNeT++ 5.4 which changed some internals on parameters and therefore is simply to new for Plexe 2.0. You have to use an older version like OMNeT 5.0 or 5.1 as this is what Plexe 2.0 was built upon.
Also see these posts:
Error in Veins tutorial simulation
Error while running example of the veins in the last step of the installation
Is casting possible in parameter expressions in OMNET++?
Ever since I switched to Yosemite, I have been getting an Xcode quit unexpectedly error whenever I try to run SDL2. I can't even get a "hello world" to run.
I am trying the fix it by following the directions on this page:
Xcode 5 crashes when running an app with SDL 2
But I don't know how to "Compile the "Framework" target in Xcode/SDL/SDL.xcodeproj" I tried just simply building it but that doesn't seem to work because I don't see any framework file showing up.
Can someone help me figure out how to get rid of this error?
I assume you have got the latest version of the code either by doing hg clone http://hg.libsdl.org/SDL or by downloading the latest snapshot from https://www.libsdl.org/hg.php
This should give you a directory called SDL which contains the source and all of the projects. You will want to open 'Xcode/SDL/SDL.xcodeproj'
Then ensure the following is set as your build target - Framework > My Mac (64-bit) You can change it by clicking on it.
Then hit CMD+B (or select Product->Build from the menu) to build the framework. You will then be able to find the SDL2.framework in the following location:
/Users/*yourusername*/Library/Developer/Xcode/DerivedData/SDL2-*randomstring*/Build/Products/<*Debug/Release*>
Copy the framework to /Library/Frameworks
I have an Mac OS X app working fine on XULRunner ver 18.0.
Now I am upgrading the XULRunner version from 18.0 to 30.0. Have followed the steps below:
Downloaded the XULRunner 30.0 Runtime
Remove the content from XULRunner.Framework directory
Copied the latest files downloaded in XULRunner 30.0 Runtime
Now while launching the application, I am getting this error:
Dyld Error Message:
Library not loaded: #executable_path/libmozglue.dylib
Referenced from: /Users/USER/Desktop/*/MyApp.app/Contents/MacOS/xulrunner
Reason: image not found
Unfortunately XULRunner is not well supported, but I was able to get around most of the errors and get it working, except for one issue which I will get to later.
Basically, all the instructions I can find for how to structure the bundle are outdated. Mozilla had to restructure the binaries due to changes in the Mac code signing layout requirements. From this bug report and some trial and error I was able to determine the layout requirements.
The first error we can see when running the Contents/MacOS/xulrunner binary from the command line.
Error 1:
dyld: Library not loaded: #executable_path/libmozglue.dylib
The entirety of the XUL.framework contents must be placed into the App's Contents/MacOS/ directory. So to fix this error, copy everything from XUL.framework/Versions/Current into your app's MacOS directory.
Ok, now the binary will run. However, that brings us to the next error which can also be seen from the command line.
Error 2:
Couldn't load XPCOM.
This error is anything but descriptive, but to solve it you simple need to copy the dependentlibs.list file (now in your MacOS directory) to your Contents/Resources/ directory.
Error 3:
Now when you run by the command line, you will get something like the following.
Mozilla XULRunner 36.0.4
Usage: xulrunner [OPTIONS]
xulrunner APP-FILE [APP-OPTIONS...]
OPTIONS
--app specify APP-FILE (optional)
-h, --help show this message
-v, --version show version
--gre-version print the GRE version string on stdout
APP-FILE
Application initialization file.
APP-OPTIONS
Application specific options.
Unfortunately, xulrunner is not automatically finding the application.ini file in Contents/Resources. For testing, we can force it through the command line. Something like the following will do the trick:
./MyApp.app/Contents/MacOS/xulrunner MyApp.app/Contents/Resources/application.ini
At the moment, the only possible solution to this last issue I can offer at the moment is to make a stud loaded, either a shell script or compiled binary that executes the necessary command to run application.ini in xulrunner.