Maybe i'm just being stupid, or perhaps Titanium has moved on, but i'm trying to run your command in Terminal and i get an error:
python: can't open file 'build.py': [Errno 2] No such file or directory
The file I download have this name: masuidrive-TiAdMob4iPhone-2a6fe97.zip
I cant find 'jp.masuidrive.ti.admob-0.1.zip' anywhere
I trie to rename it and put it on module folder but nothing happens.
any help
Thanks
With Titanium its always worth restarting everything, deleting your build folder and any other voodoo you can think of before giving up, esp when messing with modules. That error looks somewhat familiar.
Related
After creating the project with react-native init, i found this issue in terminal as well as in xcode. After digging deep, i found that this particular file is showing missing in project node modules.
Here are example of error codes showing in xcode & terminal-
Error: ENOENT: no such file or directory,
/ios/Pods/../../node_modules/react-native/React/FBReactNativeSpec/../../Libraries/Vibration/NativeVibration.js
I've learned the hard way when programming in react native (for cross platform/hybrid application development), many unknown issues will be caused if you deviate from native OS clustering. Make sure you don't make the same mistakes as I have.
I have more specific help for you, apart from the obi wan style in my previously semi-answer.
Another guy had an issue with this a few years back, he asked and was answered,"delete your node_modules and app from simulator. Then re-install everything back, clear cache and see if it start bundler from root directory.
Before doing that, you can try 'react-native start' from your root directory.
I have seen that error message a lot, specifically with jest. But that's a different fix. I realize you are not using jest to test your reactjs, but it is jest tests runner that is the problem that causes the same outcome as you have come to- solution there is to disable the jest runner from running in the background while installing new packages.
I wonder if there isn't a similar solution here - only applicable to xcode - although you see it in terminal, that's probably just the cmdline not recognizing the path to the directory or at least that file.
Should be easy to figure out with terminal--
Go to $HOME~ type dir or ls, to see your directory folders, if you see the project listed, cd into it or, just search for the directory apt-get search [package] or apt, pkg, pip, pacman, snap etc etc whatever your flavor if OS terminal is, or search for the file-- $find / -iname [query] or even search for all paths containing the phrase: $locate [query]... If you created it, it exists. Just because xcode can't find it, and initial attempts in term produced nada, don't believe it is not in your system. just a matter of where, what, and why a process or dependancy is missing or malfunctioning in attempt to retrieve the file & open it.
You can definitely find it - i don't know jack about xcode, but terminal -- I can get anything from anywhere on cmdline-- you can too. I have to go, but I'm curious if you have figured it out. Let us know yeah? Best of luck to you. Cheers QwaziRidwanhasib.
-Cujo
I'm working on a website that has gulp set up to compile scss and launch a dev server. I didn't set up the project and the person who did is unavailable to ask directly.
It worked fine previously but now when I run the gulp command in the terminal, it gives me this error:
Error in plugin "sass"
Message:
sass/projectName.styles.scss
Error: File to import not found or unreadable: breakpoint.
on line 4 of sass/projectName.styles.scss
>> #import "breakpoint";
So it seems the fairly obvious, however my attempts to fix it don't seem to make any difference.
I have changed the includedPaths to point to the breakpoint module in my node_modules folder, but what really confuses me is that even if I comment out the "#import breakpoint" line in projectName.styles.scss, it still gives me the same error message. Which makes me think gulp not reading the changes to my gulpfile, but I'm not sure why.
I'm assuming it's something simple, but as far as I'm aware gulp doesn't have a cache or need to be cleaned after changes to the gulpfile, so again, I'm not sure why it's doing this.
Here's the include paths section of my gulp file.
var sass_config = {
importer: importer,
includePaths: [
'node_modules/breakpoint-sass/stylesheets/',
'node_modules/singularitygs/stylesheets/',
'node_modules/compass-mixins/lib/',
]
};
Any insight or ideas on what I can try would be helpful.
Thanks.
OK, so I figured out the problem and thought I'd answer my own question for prosperity.
What happened was, earlier I had deleted the project repo while I still had the project open in Sublime. I did not close the project in Sublime (though I did close Sublime itself, there is a slight difference) and cloned the repo again.
When I went to started working on it today, I continued in the window which was open in Sublime.
I'm not an expert in how the text editor works but I guess there was a copy or reference to the deleted project repo files in memory or something, so the files I was editing, i.e gulpfile.js, weren't actually the files I was interacting with in the terminal using gulp.
I figured it out when I did git status and the files I was editing were unchanged. Closing the project window and opening the project in Sublime again solved my problem.
So a bit of a silly mistake on my part, but at least we learned something ae!
Just downloaded the stenohide zip file, and copied the given .dll files onto windows\system32
However when I try to run stenohide.exe, it does not work at all.
Could you please help, thanks.
Error message- I put the exe on my desktop and tried to run it, and error message said:
The program can't start because cygwin1.dll is missing from your computer. Try reinstalling...
I have cygwin1 in my system32 directory.
I've got a project that debugging was working just fine about an hour ago, and now after the latest rebuild I can't get it to load the symbol files, so I cannot hit my breakpoints.
I've tried everything suggested here on Fixing “The breakpoint will not currently be hit. No symbols have been loaded for this document.” and cannot get it to load my PDB. There are a ton of questions on .PDB files not loading here on SO and I've spent the last hour going through as many of them as I can and trying everything suggested, but to no avail.
I've tried Build>Rebuild Solution, Build>Clean+ Build>Build Solution, Build>Clean + Build>Rebuild Solution, manually deleting all files from the BIN output folder + Build Solution and/or Rebuild Solution. The same thing happens in each case; the compiler creates a brand spanking new .DLL and .PDB file, yet the .PDB refuses to load at runtime.
I've even tried Debug>Windows>Modules>[Right-Click on offending symbol library]>Load Symbols and I manually browsed to the correct .PDB file, but when I hit Open it just tells me "A matching symbol file was not found in this folder".
Using Debug>Windows>Modules>[Right click...]>Load Symbol Information gives me:
C:\Windows\ssoederPDMupgrade.pdb: Cannot find or open the PDB file.
C:\VS_TestFolder\EPDMAddIns\ssoederPDMupgrade\bin\Debug\ssoederPDMupgrade.pdb:
PDB does not match image.
C:\VS_TestFolder\EPDMAddIns\ssoederPDMupgrade\obj\Debug\ssoederPDMupgrade.pdb:
PDB does not match image. C:\Windows\ssoederPDMupgrade.pdb: Cannot
find or open the PDB file.
C:\Windows\symbols\dll\ssoederPDMupgrade.pdb: Cannot find or open the
PDB file. C:\Windows\dll\ssoederPDMupgrade.pdb: Cannot find or open
the PDB file.
C:\Users\ssoeder\AppData\Local\Temp\SymbolCache\ssoederPDMupgrade.pdb\afe14027e9c6490883d12f2f139cb5911\ssoederPDMupgrade.pdb:
Cannot find or open the PDB file.
C:\Users\ssoeder\AppData\Local\Temp\SymbolCache\MicrosoftPublicSymbols\ssoederPDMupgrade.pdb\afe14027e9c6490883d12f2f139cb5911\ssoederPDMupgrade.pdb:
Cannot find or open the PDB file.
C:\VS_TestFolder\EPDMAddIns\ssoederPDMupgrade\obj\Debug\ssoederPDMupgrade.pdb:
PDB does not match image. SYMSRV:
C:\Users\ssoeder\AppData\Local\Temp\SymbolCache\ssoederPDMupgrade.pdb\AFE14027E9C6490883D12F2F139CB5911\ssoederPDMupgrade.pdb
not found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ssoederPDMupgrade.pdb/AFE14027E9C6490883D12F2F139CB5911/ssoederPDMupgrade.pdb
not found
http://msdl.microsoft.com/download/symbols: Symbols not found on
symbol server.
Not much of an answer but...
I think something became corrupt in VS Express 2013. I have no idea how or why - and I may be totally wrong here, but the simple matter is what got my breakpoints working was installing VS Community 2015.
After installing VS Community 2015 (VSC 2015) the symbol file loads without problem, and all breakpoints are hit. This also got everything working in my existing VS Express 2013 (VSC 2013) installation, so I can work in either one now without problem.
Event timeline:
I've been working in VSE 2013 on this same project for a month or two now. Writing a class library, debugging using Debug>Attach to process.
I made some changes yesterday to code within a single class module (no other changes) and used Build>Rebuild Solution to clean and re-generate the current configuration (DEBUG) output files.
Event horizon: I went to debug using Attach to process as usual, and my break point appeared hollow with the message it would not be hit because no symbols had been loaded.
I spent quite a bit of time trying to work this out before posting here (see my original question for details on what was tried).
Received suggestion from #HansPassant regarding use of Symchk from command line. Tried to follow instructions linked to and was unable to get it working - command line didn't recognize Symchk or Symchk.exe as valid commands/processes/etc.
I downloaded WDK 8.1 update and installed.
Opened VSE 2013, received an error message regarding a driver failing to load, application froze before loading up. Actually, after trying multiple times I found it would sometimes get to the welcome screen - but remained unresponsive even then.
Went on M$ VS site to download latest copy of VSE 2013 installation files to do a repair-install, and I noticed there was a newer version: VSC 2015.
Downloaded and installed VSC 2015.
Opened project, started debugging by using Debug>Attach to process and it worked - all symbols loaded and my breakpoints worked. NOTE: I changed nothing with the project * - just opened it and ran.
* unless some changes are made by the IDE unbeknownst to me just by opening the project.
This seemed to repair whatever driver was corrupted in the VS2013 install as well, as I went back to VSE 2013 and it opened without error AND I was able to open the same project and do Attach to process and all symbols loaded and breakpoints are working again.
I had the same problem with VS2013 Ultimate. I did a clean and build of the assembly several times, and I deleted all temporary files from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files.
I also verified that in "Debug -> Options and Settings -> Symbols", there were no modules excluded... in the end, I found a reference that was different from that deployed into the GAC.
I'm glad you got it to work CBRF23! I had this problem when trying to compile a DirectX effect file in DevC++. The easiest way I found of downloading pdbs is to first download WinDBG here:
http://go.microsoft.com/fwlink/p/?LinkId=536682
Then as an example, say you want to download d3dx9d.pdb. copy d3dx9d.dll from C:\windows\system32 and paste another copy into your (debugger) windbg symchk.exe folder, then connect to your internet server, go to the windows start menu, Run: [then type] cmd [press enter], next go to the windbg debugger folder by going to the Command Prompt (MS-DOS Window)
(if it's in the C:\windbg_6p12p0002p633\debugger_x86 folder for example, then type):
cd windbg_6p12p0002p633[enter]
cd debugger_x86
[and finally type the following but change the double asterisk** to one asterisk *:]
symchk /if d3dx9d.dll srv**c:\symbols*\mainserver\symbols*https://msdl.microsoft.com/download/symbols
Please note again, that there is only supposed to be one asterisk after srv (the post would interpret an asterisk as italic or bold), not two then it will open symchk.exe and download the pdb symbol file associated with the inputted dll into the created C:\symbols\ folder automatically!
Did you try these steps?
1- delete the .SUO file
2- make a CLEAN BUILD.
3- make a BUILD PROJECT
IntelliJ was working fine on my machine and suddenly it started to give me these errors when I compile
"failed to copy from temporary location to output directory: path-of-the-temporary-compiled class-in-the-user-temp-directory"
If I remove the module from the project and add it again and compile the file, it works fine for sometime and then starts giving this error.
Tried cleaning up the user dir, shutdown and restart, etc. No luck
IntelliJ IDEA 11.1.3 on Windows 7. Also on IntelliJ IDEA 12.0.1 on Windows 7.
I got the exact error.
I fixed this problem by Rebuilding the project.
Click on Build -> Rebuild Project..
This will resolve the problem. Thanks.
I got the same error but did not see any answer to this question so thought of posting my solution(workaround) for this:
As the error mentioned failure to copy from temporary location which was point to Temp folder so I tried cleaning up the Temporary files etc. using Disk Cleanup of C:\ and that resolved the error for me.
NOTE: This is just a temporary workaround, I would love to get a real solution to this. I am using IntelliJ IDEA 12.0.1.
I got the same error and restarted the IntelliJ IDEA which fixed the problem. I think when I restarted, the process was killed and associated files in temp files were delete..
Next time when I get it I will compare the no of files in temp folder before and after restart.
It's works by set resources config in the pom file