I try to debug with Zerobrane , code for Corona SDK, but when I press the button to start the debug, popups all the time a window saying that main.lua is used from other programs. There is no other program using the main.lua
When i press the button then the corona simulator starts and this is using the main.lua . When I kill the corona simulator the popup windows disappear.
Any other experienced this?
Thanks in advance
There was a fix for the files not closed, which may be related to this issue. You can try with the current master branch version to see if it fixes the problem.
Related
When enabling "Debugging" in the ios simulator and open chrome for debugging.
The first time works perfectly but when change code and refresh automatically.
After that Debugging points somewhere else. I understand there is a mapping issue while debugging.
Any solution for this?
Debugging mapping attached to the project when we start project or reload but at the time of hot reloading (auto refresh) will not update that mapping correctly.
For update the mapping correctly you have to reload it.
In physical devices: Shake the device it will open a window choose 'reload' option.
For simulator: by pressing command+R or command+control+z and choose 'reload' option.
For emulator mac OS: by pressing r+r (2 times).
In chrome developer tools, try switching to network tab, and check "Disable cache". It might help
Im currently tring to automate ipa builds with iPhone Simulator. As I use sikuli for my automation, I need the simulator window to be 'on top' for the script to run. But when I useApp.focus(iOS Simulator) , it doesn't bring the simulator window on top, rather gives an error as
[log] App.focus ios simulator(0) #0
[log] openApp: "ios simulator"
[error] App.focus failed: ios simulator not found
But the same works if I use it to focus either the Terminal or iTunes!
Can you advice as how to proceed..
If I recall right, App.focus() takes a string for its parameter. So, it should be App.focus("iOS Simulator") (with quotes) Also, sikuli has issues with focusing on minimized windows, so you should make sure it's not minimized...
edit:
I'm noticing too, that your log entry just before says you opened the app. Have you double checked that the proper app is actually opening?
Is there a way of activating the Breakpoints in Xcode Instruments Automation after writing several scripts because it would seem that there are there but just inactive. I was wondering if I could debug my JS code from the Automation instruments without having the Application code in Xcode?
Thanks
The reason you see the breakpoint options when you right click in the gutter of the UI Automation script editor is because the whole editor pane is the code editor reused from Xcode. It's unfortunately confusing, as you've found out, but apparently that was a convenient way for them to do syntax highlighting and all that inside Instruments.
Instruments works independently of Xcode, even if started from Xcode. If you run the Automation tool from Xcode, you will see that it starts you app and issues UI commands to it, without Xcode knowing about this: In XCode, the run button is still enabled.
This means that Xcode is not active, and breakpoints are not enabled. Thus, you cannot issue UI commands from Automation to you app so that it will stop at a breakpoint.
My kids want to learn to write apps on their MacBook which currently runs OS version 10.5.8.
I have downloaded Xcode 3.1.4 but it doesn't seem to have the iPhone Simulator.
Does anyone know where I can find this?
(And are their better tags I should use for this question?)
Thanks.
(UPDATE: I down loaded the " xcode 3.2.6 & ios sdk 4.3" dmg file from Apple in the hopes of accessing just the "iPhone simulator" but repeated attempts to open the .dmg file on my OS10.5.8 Macbook result in a complete, "blackscreen" crash.)
I am really very sorry because this is not straight to your question. But if I were you, I'd like to encourage them to start with Android. To me, an open-platform is more preferred. Beside that, Java is a strong/ dynamic language when comparing to C/C++.
Android developer site
Eclipse IDE
Android SDK
ADT plugin for Eclipse
API guides
Training videos
Hope they will like :-)
Are you sure the simulator was not included? One thing to remember is it won't be shown with xcode in your applications folder.
To use the simulator you have to launch it from xcode by pressing the play button in the top left corner of the interface. If you have already used xcode with an iPhone/iPod/iPad make sure you select simulator from the drop down next the play and stop buttons(press and hold to change what is selected).
If you want to make sure you can access the simulator without xcode, launch the simulator as described above and then right click(or ctrl click) the icon for the simulator and select keep in dock from the options menu.
Hopefully the above helps you with your problem. If xcode truly did not come with the simulator your best option is to uninstall xcode(after backing up any projects) and trying a fresh install. Also try checking Apples dev center (https://developer.apple.com/devcenter/ios/index.action) for information about xcode and the simulator.
Recently I updated my project settings as Xcode recommended. I just pressed a button and they did "everything". However now when I try to run my app on my device it freezes on the loading bar at about 75% and then after 15 seconds it says "build succeeded" but does not run on my device and everything stops as if I had pressed the stop button. I am getting no errors but I am getting the following warnings. It works on the simulator just fine.
For the record I have looked this up and everyone says to add "armv6 or armv7" and I already have this done. I am running deployment target iOS 3.0+
If anyone can help me, it would be appreciated. Thank you!
EDIT
Works on my device when I run leaks in instruments... but won't without instruments
Well, I can't really say much specific here, but if all else fails, I'd try making a new project and copying the content of this project to the new one. This could fix some underlying problems that may have developed in the build settings etc.