I create React Native projects with react-native init and it outputs many lines in my console. Often there will be a bunch of warnings or errors that I want to work through one at a time, and would like to keep the logged output in a separate file.
What I've Tried:
I just copy-pasted the logged output into a file in VsCode. The problem is that it pastes as plain text by default, and doesn't have the informative colors that the console has (red for error, yellow for warning, etc).
What I Want To Know:
Is there a way I can format the text (ie. "Select Language Mode") in VsCode such that it have those informative colors? And is there a way I can automatically re-direct my console output to a file with this language mode preferences automatically set?
Related
I was working on a Vuejs project. So this morning when I opened the project it wasn't compiling anymore and it was reporting an error in one of the components. When opening the component, this message appeared in the VSCode editor "The file will not be displayed in the editor because it is either binary, very large or uses an unsupported text encoding." Clicking on open anyway appears a lot of code with strange symbols as shown in the image. When I try to open the file in another editor, the same problem also happens, but the symbols change. I would like to know what might have happened and if there is a way to recover my file?
Looks like your file is corrupt. Restore from a backup, or re-pull from git.
I've been trying to find if there is a way to make the PowerShell integrated console commands code the same color as the color theme in VS Code.
So far everything I've found has only been about the theme colors for code inside files but nothing about changing the integrated console code colors. I'm not even sure if this is possible inside the integrated PowerShell console.
I would have expected that you could change the colours using the Set-PSReadLineOption command as you can in the terminal but whilst Get-ReadLineOption returns results Set-PsReadLineOption does not change the colours so I expect that it is not possible
Also you won't be able to match the formatting exactly anyway as the colours available in Set-PsReadlineOption and the options are not compatible
This is the email:
Dear developer,
We have discovered one or more issues with your recent binary submission for "Bla". Before your app can be reviewed, the following issues must be corrected:
Corrupt Icon File - The icon file 72 x 72.png appears to be corrupt.
Once these issues have been corrected , go to the Version Details page and click Ready to Upload Binary. Continue through the submission process until the app status is Waiting for Upload and then use Application Loader to upload the corrected binary.
I have change the file and re-upload the app, but I got the email again.
As Michael Dautermanm says.
Make sure "compress png's" is turned off in the build settings.
thanks
Can you open the file in Preview, and choose 'Tools' -> 'Show Inspector'? The file may be using some PNG format features that Apple don't like. They want RGB, 8 bit depth, no alpha. See the Custom Icon and Image Creation Guidelines.
For comparison, here are screenshots of the Preview Inspector, showing properties of an icon for an app that was accepted. If you're unsure, post similar screenshots for the properties of your picture.
The "Pixels Per Meter" part may or may not appear. It wasn't there when I first opened some icon files five minutes ago, and now it appears for every PNG I open. Weird.
Edit: also check the icon entries in your 'Info.plist', or the 'Info' tab for your Target. (These are not the same thing, as I just spent several hours discovering. Settings in the 'Info' tab override your 'Info.plist'.) As of the iOS 5.1 SDK, these include Icon file (a string), Icon files (an array), and Icon files (iOS 5) (a dictionary containing at least one dictionary containing an array). XCode seems to add your launch images to this list too. Don't rely on it to keep the list tidy - I have sometimes found outdated filenames in mine.
For further comparison, here's what ended up in the Info.plist of a valid app. Your filenames may be different, as long as they match the resources in your project.
I'm the developer of the app Pillboxie. I have been having the same issue as you, but I believe I may have finally found a solution.
Before proceeding with my suggestion, make sure that your Info.plist and all icon filenames appear exactly as Apple requires. Keep checking the documentation to make sure you're up-to-date, but Dondragmer's recommendation looks correct to me.
I created all my image resources, including app icons, in Photoshop, exporting for web as PNG-24's. Because Pillboxie has numerous images, setting "Compress png's" to YES in the build settings helps me save several megabytes of space. I was getting the same error as you until I tried turning off this compression, as Evaristoyok suggests. However, my app jumped up several mb. I hoped to find a better way.
Tonight I found the following link: article. In it the author suggests to make sure that "Interlaced" is NOT selected in Photoshop when exporting images in the Save For Web & Devices dialog window. I re-exported all icon and launch images with this disabled, and it solved my issue. I was able to submit my app and still leave png compression enabled.
I have a msbuild script that includes creation of a few PDF's using PDF creator. It's the Convert2PDF.vbs that's being used, converting doc's to PDF's, and a while ago it stopped working and none seemed to take the time to fix it. So I looked into it and by debugging the script I found that it was in fact a document for which Word presented a dialog with information about contents being larger than the margins. This halted the entire thing since none could press this dialog during the auto-build.
So what I wonder is if there is a way to tell the PDF Creator script, via cmd line arguments or by altering the script, to suppress these kinds of warnings and just continue with conversion?
I solved this by creating a script in word that suppressed warnings if the given document resided within the build folder specified.
I don't remember where I heard about it, (I think I was searching up on how selectors worked and it ended up not being exactly the same as a callback function) and I can't confirm it. But more importantly than that, is there a way I could get a list of the function names from another application?
See class-dump.
You can sometimes see a list of the method names in an application. Find the .ipa file for the app (possibly in the Music->iTunes->Mobile Applications directory on a Mac). Make a copy of one of the ipa files and change it from .ipa to .zip. Unzip the file and in the Payload folder, there's a file with the same name as the app. Right click on it and "Show Package Contents". In there, you'll find another file with the same name as the app (with no extension). This is the executable file for the app. If you open it in a text editor like BBEdit, you'll sometimes be able to see some method names, as well as a list of the frameworks the app is built against. You can find the path name where things were kept too, often with the developer's name.
For example, looking into the Japanese dicitonary Daijirin, I can see these methods:
-[HMWebSupport openMONOKAKIDOSupportWithSafariForView:style:]
-[HistoryViewController viewWillAppear:]
I can also see that one of the developers was called Norihito, and he was using SVN: /Users/norihito/Developer/SVN/Mobile/DAIJIRIN/Other
Other applications (like Weightbot) don't show as much information. I don't know the reason it shows up some times and doesn't other times.