OS X 10.9.4
X-Code 5.1.1
I don't have Mac Developer Program account.
I created app for OS X, builded unsigned .app. It runs perfectly and works on my Mac. When I copy application to another Mac with the same version of OS X, try to run but nothing leads. Application icon starts appear in Dock and immediately disappears without any message. Running in the console gives an error "LSOpenURLsWithRole () failed with error -10810", unfortunately -10,810 is an unknown error.
I tried the same thing with a empty application "HelloWorld", it did not run too. Install and run applications from unknown developers in security setting is turned on.
I tried build LASlider example-project (https://github.com/Doshipak/LADSlider), that I use in my project. When I run it on another mac, app crashes like HelloWorld & my project..
Does someone has similar problems?
What had happened: Safari download invalid *.app from Dropbox with empty app body, same thing happens if you try to transfer *.app with TeamViewer. But result file looks normal.
Decision: always pack *.app in archive.
Related
Just updated my Mac to the official release of Ventura, and I cannot launch my application via react-native run-ios.
Expected behavior:
running react-native run-ios will launch an Xcode simulator and a terminal window with Metro running.
Current behavior:
Xcode simulator opens, main terminal says app was built successfully, but an error is thrown instead of the metro terminal opening:
“launchPackager.command” can’t be opened because (null) is not allowed to open documents in Terminal.
The simulator just shows a white screen and can't be interacted with.
What I've tried:
manually opening node_modules/react-native/scripts/launchPackager.command
opens Metro terminal but is not connected to the app
warn No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB.
info Reloading app...
giving Terminal full disk access (no change)
This happened to me after upgrading to macOS Ventura. I happen to use iTerm as my main terminal, not the built-in Terminal.app so the following fix only applies to that scenario:
Set iTerm as the Default Handler for *.command Files
Open node_modules/react-native/scripts/ in Finder (open node_modules/react-native/scripts/)
Right-Click on launchPackager.command and click Open With then choose Other...
In your Applications directory, select iTerm and click Always Open With
After this, you might need to run npm run ios again from this terminal window. However, from now on, Metro will open in a new iTerm tab instead of trying to open the command in a new Terminal window.
For me, this was the desired behaviour and it removed this warning.
Note In future, any *.command files will now open with iTerm instead of Terminal.
I encountered the same problem as you, I installed another terminal (iTerm2), then randomly found a .command file, and in the display introduction, changed the default opening method to iTerm2enter image description here
I'm having this issue after upgrading my MacOS to Ventura 13.1.
If you don't want to use iTerm as the accepted answer suggest, the workaround I found was to look for the launchPackager.command file inside node-modules/react-native/scripts/ and open this file manually every time you run your app for the first time (specifically when the error pop-up appears). This will open the terminal with metro running already.
I know that manually processes are not the best, but I don't want to use iTerm :)
Using Intel version of apps (Webstorm, Android Studio, other IDE etc...) fixed my problems. I encountered the same issue and thanks to Intel version of Webstorm and Xcode on Rosetta I can able to pod install and other operations.
Note: I'm using Intel version of Android Studio, WebStorm. Also Xcode uses Rosetta 2. No problem detected and everything works perfect. I can able to develop React-Native & Native Android & iOS and Flutter apps without problem. Before that I was using Silicon version of WebStorm and almost no function worked.
Config: MacBook Air, macOS Ventura 13.2 on Apple M1 processor.
For Most of the case you just have to delete node_modules and install modules again (npm i). This happens when project was copied from old mac which had node_modules folder created by the old user, or if the system thinks so
This happened to me after i configured my terminal for the look and feel - but with iterm2, oh my zsh, and powerlevel10k
I have an OSX app that is constantly crashing on one device.
I have setup the project build setting to never strip symbols (debug or release):
When I build the app, I copy both it and the .DSYM files to a local folder. I then copy the app to the testing computer, where I launch it. After it crashes, I copy the generated .crash file (found via the Console app), to my local folder which also contains the app and .DSYM file.
In XCode, I switch to the Organizer window, choose import and select my .crash file.
Nothing happens. My understanding is that this should symbolicate my crash report, so that I can understand it better.
Any suggestions as to that i'm doing wrong? (Or if I don't have a proper understanding of how to symbolicate a crash log)?
I may have found the answer:
How do I symbolicate a crash report of a Mac OS X app that a user emailed to me?
That basically, XCode does not support symbolicating osx crash reports.
The emulator used to run fine, but as of late whenever i try to launch it, whether directly from the programs list or by running code in Visual Studio, the emulator will launch, stop responding and crash, then when I hit "close program" it will launch itself again, stop responding and crash again. I've looked everywhere and cannot get an answer to this issue.
Thanks
The only way i think is by reinstalling the product.
Just so you know, make sure that you're using the right version of the SDK for your OS (on PC) and using just the right emulator supported by your OS (pc).
Like for SDK 8.0, if you're developing Win8 app, use 'Device' for direct app deployment onto your phone or "Emulator WVGA 512MB" for optimized, memory-constrained output on your PC itself.
i ve developed an iphone application.i was able to install the application and was working properly.in the past two hours i m getting error while installing the application in the device.i tried restarting my device and mac but its in vain..could u guys help me out.
below is the error
Couldn't register com.upspl.bigbapp with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.(lldb)
Did you try to restart your Mac or kill the Debugger? You can also try to press cmd+. to stop the process.
For other references, take a look at similar posts:
iPhone - strange error when testing on simulator
Couldn't register […] with the bootstrap server
You can try: delete your application from device and iTunes, restart your device, and then relaunch it.
I've got an Xcode project that I've been working on over the past few weeks.
I just made some changes to an embedded framework that I'm working on (recompiled, to be specific) now, however, I am unable to launch the application in the simulator.
The app hangs on "Attaching to [app name]," if I have a debugger on. If I don't have a debugger on, Xcode just says the app has finished running.
There is no icon installed on the device.
Here's what I've done so far:
Restarted
Reset simulator
Clean and build
Deleted derrived data
I cannot install onto a device either, but then I get an error:
Error launching remote program: No such file or directory (/Users/peter/Library/Developer/Xcode/DerivedData/x-gtwuuwmavjonyrcxjmpcletdpyjw/Build/Products/Debug-iphoneos/x.app/x).
Oddly enough, what worked was installing another app in the sim (just launched another project and ran it) and then launching the other app in the sim.
I'm not sure what the issue was, but I tried it on two computers and it was hanging on each, so it was related to the project rather than the simulator. There's an issue to think about...