I've been searching for a solution to help me clean up Detox test automation's output, as currently the output is quite messy..
The biggest culprit of the ugliness seems to exist within GREYElementInteraction.m which is seen within the Detox repo, but I'm not sure how to go about tweaking this file. It doesn't exist within the installed Node Modules on the native app, so I'm assuming that this is compiled and used by the javascript files within the detox node modules folder.
Any ideas?
Explanation added here:https://github.com/google/EarlGrey/issues/762
It looks like Detox calls into EarlGrey and it does not look as though there is any way to pass in an error to EarlGrey which will turn off the exception from being thrown - thereby preventing the hierarchy / log dump.
If this is passed in, then you should be able to get the required disabling of logs.
Related
When I run tsc --watch the terminal clears and I see:
[15:43:52] Starting compilation in watch mode...
[15:44:14] Found 0 errors. Watching for file changes.
I'm working within a monorepo that has multiple packages and hence multiple watch tasks. It gets confusing as to which one's which. Currenly I have to manually label terminal sessions.
I'd like to add some indication as to what path is currently being watched to this message. Is that possible?
--listEmittedFiles is the one, as pointed in the direction of above by #jonrsharpe. Thanks!
I've found countless threads on how to add the Carthage Run script, but I would like to know why is this script needed?
When adding other .frameworks to Embedded Binaries or Linked Frameworks, there's no extra step that's needed that I'm aware of. So why are frameworks build by Carthage different?
Looking at the documentation, it talks about debug information being copied into the built products directory. So is this Run script needed to allow desymbolication of crash logs or it's for something else?
Run scripts works around an App Store submission bug triggered by universal binaries and ensures that necessary bitcode-related files and dSYMs are copied when archiving.
I'm currently attempting to fix build issues which occured once i tried to update some component. they told me i need to update some references. Oddly enough i now get these issues:
Now i'll just add some text so someone comming from google can find the potential answer as well:
error reading xamarin android.support embedded jar error in opening zip file.
Does anyone know how to fix this? I've tried:
Deleting and restoring nugetpackages, in hopes the nuget install script supplied these files,
Uninstall+Install Support Package in Android SDK Manager
Deleting files, in hope they are just temporary references and are pulled by xamarin if they are missing.
Neither one of those attempts worked out sadly.
Any ideas?
Turns out the reason of this issue was actually my own impatience. At some point after package updates i must have canceled the build process assuming that it got stuck, because it just wouldn't deploy. That resulted in incomplete jar files.
I fixed the issue by deleting the folders in AppData/Local/Xamarin which raised errors and that in turn made sure the build process redownloads the required files properly.
I'm getting this PBXCp error saying there is no such file or directory even though i checked and the file is there. Tried going into targets and Copy Bundle Resources deleted the file in question from there and adding it again did not solve the issue. Any help is appreciated.
PBXCp is a build utility; it copies files.
Your error is caused by it trying to copy a file, and not being able to put the file at the indicated place.
For instance: I'm getting this error as I try to build an extension for an App that is not building; my issue was that PBXCp is trying to install the extension, which did build properly, into an app bundle (essentially, a directory) that doesn't exist, which fails.
Since you're using CocoaPods, check to see whether anything needs updating or reinstalling. You could also be getting this error if you are using multiple schemes, and the results of one build are needed by a later step. If the first build fails, this error will occur in the later build step.
I had the same issue, just find unnecessary files (they have red title name color)
I had similar issue after I added some extra files in my project by copy pasting them from another. Like suggested by many others, I tried to find the faulty file by checking in Project settings- Building Phases. Dint work. While copying, I also had copied a view controller in my storyboard. I reverted my change and re did it. Worked. May be I made some mistake while changing identifier name or something. Don't know. But if nothing works and u can't figure out what's wrong, undo and redo the copying again step by step. Hope it helps someone.
Opps: This is the same as: Is there a way to reset the error badges in Netbeans? but I don't know how to mark it as such ...
My version of NetBeans 6.9.1 is currently showing a large number of syntax errors in many files, in many projects.
But, if I look at the errors, they are invalid. For example, one error says that an import is referencing a non-existent file. However, that file exists and has no syntax errors.
More importantly, despite all of the errors, the code compiles cleanly and runs correctly.
My guess is that NetBeans is caching some data (OSGi?) that is out of date or has been corrupted. This has happened before, but in the past it wasn't this bad and it magically cleared itself.
I've tried starting and stopping NetBeans, but that doesn't do it. If, as in the above case, I use NetBeans to resave the imported file, it goes away after a minute, but for large projects this is very time-consuming. (Note that I am using jVi, and saving with that embedded editor doesn't not fix the problem, it has to be the NetBeans save command).
I'd really like to find a simple way just to force the whole internal state to refresh itself. Does anybody have any ideas?
To clear this error you need to shut netbeans, go to the .netbeans folder in your home directory C:\users\.netbeans for Win 7,
in there you will see a folder for the version you are using.
in there is a folder called var
delete this folder then re-run netbeans.
This clears the cache in Netbeans allowing it to re scan the folders correctly.
I found a useful plugin you can use called Cache Eraser.