Xcode가 하드웨어에서 프로젝트 실행을 갑자기 중단했습니다.“xxx.app을 시작할 수 없습니다 : .. 해당 파일이 없습니다.”
Xcode가 내 앱을 실행할 수 없게되었고 장치에서 앱을 삭제 한 후 바로 시작하여 Xcode에서 다시 실행하여 다시 설치하려고 시도했습니다 (수백 번 전에 수행 한 작업).
그것은 말한다
"XXX.app을 (를) 시작할 수 없습니다"
"이러한 파일이나 디렉토리가 없습니다 (/Users/Mylaptop/Library/Developer/Xcode/DerivedData/MyApp-ekxcbebfpzkahtfkujyqkcwprzia/Build/Products/Debug-iphoneos/MyApps.app/MyApp)."
전화를 재부팅하고 Xcode를 다시 시작하고 모든 것을 청소하고 모든 것을 다시 작성했습니다. 이 오류 메시지는 사라지지 않습니다.
이것은 Xcode 4.5에서 사용할 수있게되었으므로 사용했습니다. 4.3.2로 되 돌리면 Xcode에 "Finished running app"이 표시되지만 실제로는 아무것도하지 않습니다. 앱이 설치되거나 실행되지 않습니다.
나는 완전히 붙어있어 더 이상 장치에서 아무것도 실행할 수 없습니다.
어떤 제안?
정말 성가신 일입니다. 이 오류는 여러 가지 다른 상황에서 발생합니다. 때때로 Xcode를 다시 시작하면 문제가 해결됩니다. 그렇지 않은 경우 다음 단계를 수행하십시오.
장치를 분리하십시오.
기기에서 앱을 삭제합니다.
Xcode를 종료하십시오 (단지 창을 닫고 종료하지 마십시오)
파생 데이터 폴더 삭제 ( ~/Library/Developer/Xcode/DerivedData/-gbrvhlvwmpiobxdujegtghggrffp또는 이와 유사한 것)
이제 Xcode를 다시 시작하고 장치를 연결하고 프로젝트를 실행하십시오. 잘 작동합니다.
DhilipSiva 블로그에서
-Info.plist 파일에서 "필수 장치 기능"을 삭제하십시오.
3G에서는 armv7을 요구할 수 없으며 최신 장치에서는 armv6을 요구할 수 없으므로이 속성을 완전히 삭제하면됩니다.
답을 찾았습니다. iOS 배포 대상 버전이 기기의 OS 버전과 다릅니다.
먼저 info.plists를 사용하여 위의 일부를 시도하고 파생 데이터를 삭제하거나 정리하는 등
내 해결책 : XCode를 종료하고 프로젝트를 다시여십시오. Finder에서 파생 된 데이터로 이동하십시오. 모든 프로젝트의 데이터를 삭제했습니다 (모두 휴지통에 넣을 수 있었지만 문제가있는 프로젝트 데이터를 먼저 삭제하려고합니다). 그리고 다시 작동했습니다. XCode에서 파생 데이터를 삭제하지 못했습니다.
다음은 내 문제를 해결했습니다 ... 내 응용 프로그램이 디버그 / 릴리스에서 나를 위해 일한 다음 몇 가지 임시 아카이브를 빌드하고 디버그 / 릴리스 빌드가 작동을 멈췄습니다.
조짐:
- Xcode에서 장치로 시작할 때 잘못된 권한 오류 (권한으로 재생 ...)
- 시뮬레이터를 실행할 때 오류가없는 즉시 중단 (완료된 실행)
- Xcode에서 장치로 실행할 때 ... blabla ... / build / product / debug-iphoneos / ... 디렉토리를 시작할 수 없습니다.
결국 대상 [AppName]에서 찾은 다른 사람의 고통으로부터 혜택을 얻으려고 시도한 후 :
Build Settings
Build Locations
Build Products Path build
해야한다
Build Products Path build/Products
이것이 어떻게 잘못 설정되었는지 모릅니다. '제품'이 Xcode와 장치 콘솔 모두에 나타나기 때문에 Xcode / Springboard 어딘가에 하드 코딩되어야합니다. 이것은 Xcode 4.5.1입니다.
나는이 문제를 해결했다.
내 XCode 프로젝트 위의 디렉토리 이름 바꾸기
프로젝트 이름을 변경하면 XCode나를 위해 고정되었습니다.
에서이
XCode프로젝트 네비게이터에서 프로젝트 이름을 클릭하고 방금 파인더에서 파일과 같은 이름을 바꿀 수 있도록해야한다. 파생 된 데이터를 삭제해도 도움이되지 않았습니다.
CMake를 사용하여 XCode 프로젝트를 빌드했으며 어떻게 든 info.plist에서 "Executable file"속성을 삭제하거나 비 웠습니다. 다시 $ {EXECUTABLE_NAME} (으)로 설정 한 후 다시 작동했습니다.
마침내 그 문제를 발견 할 때까지 모든 제안과 수정을 통해 많은 시간을 보냈습니다.
이것이 동일한 문제로 어려움을 겪고있는 사람을 도울 수 있기를 바랍니다.
편집하다:
CMake가 plist 파일을 엉망으로 만들었습니다. 내 Info.plist를 만들어 다음과 같이 사용했습니다.
SET_TARGET_PROPERTIES( MyApp PROPERTIES MACOSX_BUNDLE_INFO_PLIST ${CMAKE_CURRENT_LIST_DIR}/MyApp.plist )
내 plist 안에 다음과 같은 항목이 있습니다.
<key>CFBundleExecutable</key> <string>${EXECUTABLE_NAME}</string>
Unfortunately CMake still seems to parse that file and replaced ${EXECUTABLE_NAME} with an empty string since its the CMake variable syntax. My quick work around is the following:
SET( EXECUTABLE_NAME "\${EXECUTABLE_NAME}" )
Now it works like a charm.
I am probably alone with exactly this problem, but who knows.
I had the same problem, but in my case I had a wrong requirement in my info.plist (require gyroscope for an iPhone 3Gs)
I tried to run my project on a different system other than that on which it was developed. I was getting “Could not launch xxx.app: .. No such file..”.
Removed the app from the device and then deleted the derived data from organizer in xcode for the app. Organizer-->Projects-->Derived DAta-->Delete
My problem was resolved.
You need to set the deployment target LOWER than your device's version
For me, the solution was just to use the correct (non-distribution) provisioning profile.
I was defaulting to always using my ad hoc provisioning profile, but then I changed to using my developer profile (team profile) and that solved things. I went ahead and cleaned out the Derived Data directory to be safe but I don't know for certain if it is required.
XCode used to have a warning that told you to use the correct provisioning profile but that error message seems to have gone away in XCode 4.5.
I've had this problem by a very strange solution.
My problem was slightly different as I have 2 Developer certificates in Keychain. We have two developer accounts (lets say AD and BD).
1) I did change Bundle identifier from com.BD.game to com.AD.game 2) Device on which I had problems was only signed in AD provisioning profiles. 3) I was unable to debug the game on iPad - although the device had valid provisioning profiles, I had valid certificates, I restarted Mac, device, reinstalled Xcode ... nothing helped.
Do what i did today was examining the project.pbxproj file for any strange entries.
What I found was that Xcode was using proper provisioning profile, but signed the ipa/app with wrong certificate.
"CODE_SIGN_IDENTITY[sdk=iphoneos*]" = "iPhone Developer: **BD** (XX******)";
After I manualy corrected the name and id; everything works like charm.
I got the same error. In my case I was set deployment target as 6.1 and trying to run an iOS 5.1 iPad. When I changed my deployment target to 4.3, issue solved.
Still having the problem . Try this Disconnect your device. Delete the app from your device. Quit xcode. Now start Xcode, connect device and run the project. It should work fine.
For me (using IOS 7 and Xcode 5), the error went away right after I did "Add to Member Center" with my device in the Organizer.
I would like to mention that the easiest way to open the DerivedData folder in Finder is the following:
- Open the Organizer.
- Click on "Projects".
- Select your problematic project.
- Next to the path of the DerivedData, click on the little right-arrow button.
Deleting the contents of the DerivedData folder worked for me. Instead of using the "Delete..." button, you should have more success deleting the files manually through Finder.
Go to: your project Target - > Info and from CustoM iOS Target Properties remove the Required Device Capabilities. In my case that were armv7 and armv7s.
After that the app was built successfully on my iPhone 4.
This is how it looks after i removed both of requirements
For me, I forgot that I had "telephony" in the "Required device capabilities" in the info.plist. Removed that, and it finally worked on my iPad.
For me restarting of Xcode, cleaning DerivedData and restaring device wasn't enough in most cases, until I had figured out that iTunes was also running, and after quitting iTunes everything worked fine!
So my steps now are simple:
1. Quit Xcode.
2. If iTunes is running, quit iTunes.
3. Reopen project.
No need to remove app from the device, clean project or restart/disconnect device. I think that's because Xcode and iTunes use some common libraries (as you know, Xcode Installer always asks to quit iTunes on installing iOS SDK).
I had this problem and tried a number of the suggestions which didn't work for me - then I found the one about removing the "Required device capabilities" in the -Info.plist file (which for me included location-services & gps) That worked! I then re-added them and it still worked.. go figure. This was xCode 4.6.1 & my app is developer with Phonegap/Cordova
I tried all the above and yet it still wouldn't run. I fixed the problem by changing the derived build location. File>Project settings>"derived data location" change to project-relative. Or you could just make sure the default path has permission to read/write.
My issue seemed to be picking picking Portrait (top home button) as Item 0 in Supported Interface orientations in my plist. Removing that or moving it down seemed to fix my problem. Go figure.
I had this problem too for a Universal app with Xcode 4.5 on my iPhone ONLY, where I had two debug devices:
iPhone 4 iOS 5.1.1
iPad 1 iOS 5.1.1
The Info.plist had an empty entry under "Required device capabilities" I know that I did not enter this empty 'Item 0'. The app loads on the iPhone since I removed the empty item. I did not encounter this problem on any of several earlier versions of Xcode, This means that Xcode 4.5 handles this 'inserted' item differently for the two devices I use. I have been wrong before, but this does seem like a bug in Xcode 4.5.
This may seem obvious but you must also set your deployment target to the operating system that your device is running.
So if you upgrade to iOS 6, it will set your deployment target to iOS 6. You'll need to deploy to 5.1 if the device you are testing on still runs 5.1.
My issue finally got resolved by checking to make sure that the productName attribute in the /* Begin PBXNativeTarget section */ section of my project.pbxproj file matched the name attribute.
Once editing it so that they were the same, Xcode finally runs the app on my device correctly!
Thanks to Max Weisel for helping me! :D
Deleting the derived data folder did not help for me. Using Xcode 4.4.2 the only solution was to open Organizer and delete old expired and extraneous provisioning profiles on the iDevice. Then everything worked perfectly again.
This may be a red herring, but I experienced these problems when I added custom launch images before deleting the default ones. Deleting the default launch and custom images and then adding back in the custom ones fixed it for me. I'm working with iOS 6 and Xcode 4.5.2
There seems to be a few different things that can cause this very helpful error message.
For me, it was down to an incorrect "Required device capabilities" in the Info.plist. I had added a blank array item by mistake (on top of the the architecture, armv7). Deleted the blank array item and now everything is fine!
I had this problem and nothing really helped except: My problem started after changing the contents of my info.plist and no reverting had helped.
What solved it for me was:
- Create a vanilla info.plist in a brand new project
- replace the old info.plist with the new
- renaming it (like app_info.plist)
- Set Build Settings/Packaging/INFOPLIST_FILE to be the new one.
- Make all the changes you need for your project
Hope that helps. I tried everything else suggested here and this was the only solution for me.
같은 문제에 직면했지만 이제 문제가 해결되었습니다 Executable file.info.plist를 삭제했습니다 . 다시 $ {EXECUTABLE_NAME} (으)로 설정했으며 다시 작동했습니다 .. :)
내 경우에는 모든 파일의 xxx.app 폴더에 777 권한을 직접 설정하고 작동합니다!
'Programing' 카테고리의 다른 글
| 암호를 묻지 않고 PowerShell 자격 증명 사용 (0) | 2020.06.21 |
|---|---|
| TTY를 무시하지 않고 암호를 su / sudo / ssh에 전달하는 방법은 무엇입니까? (0) | 2020.06.21 |
| Jquery 라디오 버튼이 선택된 경우 (0) | 2020.06.21 |
| IN 값 목록으로 주문 (0) | 2020.06.21 |
| 정규식 일치 배열 만들기 (0) | 2020.06.21 |