I try run Calabash-android test. But i got a trouble.
This is my script test:
Feature: Check Navigation feature
Scenario: Click on Navigation button of menu
When I should see "確認"
Then I wait for 3 seconds
Then I press the "OK" button
When i exec the test. Command Window show me an error.
"\xE7" from ASCII-8BIT to UTF-8 (Encoding:: UndefinedConversionError) (RuntimeError)
Does any body get same problem? can you tell me how to fix it?
I searched from internet and get a solution
http://ytabuchi.hatenablog.com/entry/2014/02/28/204850.
I do set RUBYOPT=-EUTF-8 command but it does not effect.
My calabash version is 0.5.8
Ruby version is 2.2.0
Windows 7 x64
Related
Just updated my Mac to the official release of Ventura, and I cannot launch my application via react-native run-ios.
Expected behavior:
running react-native run-ios will launch an Xcode simulator and a terminal window with Metro running.
Current behavior:
Xcode simulator opens, main terminal says app was built successfully, but an error is thrown instead of the metro terminal opening:
“launchPackager.command” can’t be opened because (null) is not allowed to open documents in Terminal.
The simulator just shows a white screen and can't be interacted with.
What I've tried:
manually opening node_modules/react-native/scripts/launchPackager.command
opens Metro terminal but is not connected to the app
warn No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB.
info Reloading app...
giving Terminal full disk access (no change)
This happened to me after upgrading to macOS Ventura. I happen to use iTerm as my main terminal, not the built-in Terminal.app so the following fix only applies to that scenario:
Set iTerm as the Default Handler for *.command Files
Open node_modules/react-native/scripts/ in Finder (open node_modules/react-native/scripts/)
Right-Click on launchPackager.command and click Open With then choose Other...
In your Applications directory, select iTerm and click Always Open With
After this, you might need to run npm run ios again from this terminal window. However, from now on, Metro will open in a new iTerm tab instead of trying to open the command in a new Terminal window.
For me, this was the desired behaviour and it removed this warning.
Note In future, any *.command files will now open with iTerm instead of Terminal.
I encountered the same problem as you, I installed another terminal (iTerm2), then randomly found a .command file, and in the display introduction, changed the default opening method to iTerm2enter image description here
I'm having this issue after upgrading my MacOS to Ventura 13.1.
If you don't want to use iTerm as the accepted answer suggest, the workaround I found was to look for the launchPackager.command file inside node-modules/react-native/scripts/ and open this file manually every time you run your app for the first time (specifically when the error pop-up appears). This will open the terminal with metro running already.
I know that manually processes are not the best, but I don't want to use iTerm :)
Using Intel version of apps (Webstorm, Android Studio, other IDE etc...) fixed my problems. I encountered the same issue and thanks to Intel version of Webstorm and Xcode on Rosetta I can able to pod install and other operations.
Note: I'm using Intel version of Android Studio, WebStorm. Also Xcode uses Rosetta 2. No problem detected and everything works perfect. I can able to develop React-Native & Native Android & iOS and Flutter apps without problem. Before that I was using Silicon version of WebStorm and almost no function worked.
Config: MacBook Air, macOS Ventura 13.2 on Apple M1 processor.
For Most of the case you just have to delete node_modules and install modules again (npm i). This happens when project was copied from old mac which had node_modules folder created by the old user, or if the system thinks so
This happened to me after i configured my terminal for the look and feel - but with iterm2, oh my zsh, and powerlevel10k
protractor version : 5.0.1
safari version : 11
Mac version : 10.13
selenium version : 3.0.1
Error message: safaridriver could not launch because it is not configured
I have enabled the safari driver using the command --enable but still it is not launching the browser
Any possible solutions for the issue ?
A lot of times, it's because the developer option to allow remote automation isn't clicked. In safari, you can access this by clicking 'preferences' -> advanced. At the bottom it says 'show Developer Menu in Menu Bar.' Click that. Then in the newly appeared develop tab click on 'Allow Remote Automate' towards the bottom of the list. If this doesn't run it, post your code and we can take a more thorough look.
As you see,when I open dev tool in chrome,It will soon turn into this red screen.If I do not open dev mode,it works, and console.log can log infomations in Xcode console.(this way is not use Xcode)
just open localhost:8081/debugger-ui and press Cmd+R in simulator, or dismiss this error, open developer menu in App and disable "Debug in Chrome" option
try to update your react-native version to more stable version may be 0.35 or 0.38.
this basically happens when react-native is not able to load the bundles into developer tool.
I just upgraded my RubyMine to v8.0.0 with the custom bundled JDK. After installing it I tried to open the app from it's icon and nothing happened. I mean it showed me the dialog box if I trust the app (this happens whenever you want to open a new installed app for the first time), but afterwards nothing showed up.
I looked through the app processes, and couldn't find the RubyMine app. I also tried the solution from this question:
RubyMine fails to start on Yosemite
No success.
After I ran chmod +x /Applications/RubyMine.app/Contents/MacOS/rubymine, I tried again from the app icon, but it still doesn't seem to work.
I updated my java version to java version "1.8.0_65" and still no luck.
It works when I run /Applications/RubyMine.app/Contents/MacOS/rubymine from the command line.
Just to be clear, before upgrading to v8.0 this problem didn't occur.
I run OS X Yosemite.
Any ideas what can cause this issue?
[UPDATE] I ended up downgrading to v7.1.4 until this gets solved.
Found the problem. Looks like I had to run the app in 64-bit mode.
Right click app icon -> Get Info -> "Open in 32-bit mode" must be unchecked.
OS X 10.9.3 iMac
Installed Xcode 6 beta today and I am immediately stuck.
Following an apparently successful install, without errors, I have done nothing more than:
Clicked the "Xcode 6 Beta" icon to run
On the "Welcome to Xcode" screen, clic ked "Get started with a playground"
Created a new Playground file
Error thrown. "Error running playground. Failed to prepare for communication with playground"
All options under the "Product" menu are grayed out: Run, build, etc.
Anyone else, or is it just me?
Tyvm
Keith
I had the same problem. Try closing Playground or Xcode 6(Same thing) and reopen. This seemed to fix my problem.