Today our Calabash-iOS tests stopped working, after XCode updated to 6.1. Yesterday all was fine, today (with no code changes having occurred) it does not work.
When trying to call touch inside our step definitions, nothing happens, until eventually a timeout occurs and the following error is displayed:
uia action failed because: Timed out running command uia.tapOffset('{:x 160.5, :y 295}')
This worked fine yesterday (before XCode updated itself). The problem affects both machines we have that updated but does not affect another machine that has not updated.
We are using the latest calabash gem (0.11.1), but I've tried downgrading to 0.10.1 with no effect.
Incidentally, I tried downloading some sample apps from Apple (https://developer.apple.com/devcenter/download.action?path=/wwdc_2014/wwdc_2014_sample_code/advanceduserinterfacesusingcollectionview.zip and https://developer.apple.com/library/ios/samplecode/UICatalog/UICatalogCreatingandCustomizingUIKitControlsObj-CandSwift.zip) and then following the installation instructions at https://github.com/calabash/calabash-ios . The simulator could be started with the -cal Target with the expected console output, but trying to run cucumber failed as it would keep attempting to launch the app in a continuous loop.
Any ideas or suggestions would be welcome. If necessary I will uninstall XCode and re-install the previous version, but I'd like to get this resolved in a more satisfactory manner.
This now works, as of calabash-ios 0.11.4 with Xamarin Test Cloud Agent Component 11.4.
Related
I am new to coding. I recently had a coder update a React Native appI got it to run on Android with an emulator but there are multiple issues when getting the app to run on IOS. I am assuming the main issue is that I need to clean the react native app for IOS, and I have trouble finding information how to do this...WHat I tried was going to the iOS in the terminal and typing "xcodebuild clean" but errors still pursue....I tried opening up xxx. xcodeproj and I got an error that said "yogakit/yogakit.modulemap' not found". Then I tried opening up xxx.xcworkspace and it got an error saying that I need to update to Swift 5 but the update fails. I ve tried to research this issue everywhere but could not find a solution. What is it that I am doing wrong here? How do you take an updated code from Native React and get it to successfully run in Xcode?
I have an issue that has come up before however in this situation I have two development machines and the code build and runs on one machine but not on the other.
I have a MBP and a Mac Pro, the code is in git and once I have built on one machine and committed and pushed to git when the code is fetched on the other machine I receive the error message WatchKit App won't compile: “error: WatchKit Extension doesn't contain any WatchKit apps”.
I have checked bundle identifiers and they all look correct which makes sense as it builds on one machine.
I also downloaded a sample app from Xamarin.com, the WatchTables demo. The bundle identifiers are correct but I am receiving the same build error with that solution.
Any thoughts, I have checked the version of Mono and other frameworks on both machines, Xcode and VSfM are the same version and up to date. Any ideas would be helpful.
After downloading additional updates on the machine that was failing when I went to install and restart an error occurred and VSfM would no longer start. So I reinstalled VSfM again, this allowed it to start and I was able to apply the updates.
Once I started the IDE again I was then able to build the solutions.
I would seem that something had become corrupt with VSfM and until the failure of the updates broke the IDE this wasn't getting sorted.
All is good now.
So I have been struggling with a weird issue with my expo setup for about the last month or so. I created my project through Expo and when I use exp start in the terminal or try to load the project through Expo XDE, it hangs after dependency graph loaded. I thought it was an NPM issue (and worked on my coding environment for weeks trying to fix it) but then I created a new project using create-react-native-app and noticed there seems to be an issue with the connection with the simulator. When I instantiate a new project with create-react-native-app (not expo) I get this error exp://localhost:19000 — Error while loading: a server with specified hostname could not be found. (code - 1003) Here is a photo of what it looks like:
Then I tried to put the address of the project from the terminal into the simulator:
And it actually works! The app loads!
This is making me think there is a problem with the simulator's connection. Perhaps it is pointed to the wrong port? Using this method, I can run apps that were made from create-react-native-app but not my original projected I created through expo because that still gets hung and won’t launch the simulator. Projects created through Expo don't have an iOS file which is how you launch a create-react-native-app project (yarn run ios).
Any ideas about how I could go about fixing this?
Try uninstalling both Xcode & Expo.
Seems like the ports for the simulator are on different references of some kind.
Make sure that all of x-code, simulators, and expo local version are up to date before you launch the simulator after reinstalling Xcode & Expo.
I'm trying to generate release version of my app using React-native :
./gradlew assembleRelease
It's progress until app::bundleReleaseJsAndAssets gets stuck at 93% and never progress. I dont have any error on terminal.
About OS I'm on Mac OS.
issue reported https://github.com/facebook/react-native/issues/10078
If you are using realm, please consider that comment:
:app:bundleReleaseJsAndAssets was trying to bundle the default.realm* in the root folder generated from the tests in jest... So it was hanging there.
It couldn't decompile them or whatever. So i just deleted them and it worked again
I used to have realm in my project but removed it. I still had files not tracked by git, hanging around. I simply removed everything related to realm and it worked again
If you are building the react native app in android studio and you are stuck at
app::bundleReleaseJsAndAssets never progress
It could be the issue with "CMD" in the android studio. Please Make sure you install the plugin.
I'm able to resolve the issue.
Today I got the memo from Apple as probably every other Apple developer about potentially infected Xcode installations. (https://developer.apple.com/news/?id=09222015a)
I followed the instructions and tried to validate my Xcode app using the command mentioned. (spctl --assess --verbose /Applications/Xcode.app) The program ran for a while and exited with a "/Applications/Xcode.app: a sealed resource is missing or invalid" message.
The article says "Any result other than ‘accepted’ or any source other than ‘Mac App Store’, ‘Apple System’ or ‘Apple’ indicates that the application signature is not valid for Xcode." However, I'm actually pretty sure my Xcode copy is legitimate (downloaded and updated via App Store with Gatekeeper enabled) so I thought maybe there could be another problem preventing it to validate as it should.
Do you have any ideas what this error message actually means? Do you think I need to reinstall Xcode just in case?
Thanks in advance for your help.
The false positive validation issue appears to be caused by containing previous iOS SDKs in order to be backwards compatible.
A clean install will completely wipe the SDK directories. When you run the validation test after a clean install it will pass. Once you copy previous iOS versions, which, for us, is iOS 8 for iPhone, the validation will fail.
This scenario was tested after updating to XCode 7.0.1 (7A1001) which was released earlier this afternoon.
In order to avoid a clean install, you can temporarily remove the previous SDK version from their respective location, and run the validation. Then, once the validation passes, copy the files back where they belong.
I was getting the same message "a sealed resource is missing or invalid". However i was able to rectify the issue by going into the App Store and downloading the latest version of Xcode - Version 7.0 (7A220), and this seems to have rectified the issue.
Although i did first try updating Xcode through the updates section on the App Store, but for some reason this didn't work. So i would recommend going into the App Store > Search for Xcode > Then install the latest version available to you.
Depending upon gatekeeper settings.please check gatekeeper settings to allow anywhere and revalidate Xcode.