Real-Machine debugging and "Could not find Developer Disk Image" problem solution

Source: Internet
Author: User

Real-machine test steps

1. Run Xcode,xcode Open, point to the top left menu ' Xcode ', point ' Preferences '.

2. In the open window, click ' Accounts ', switch to the Account page, then click the ' + ' sign below, and in the pop-up menu, tap ' Add Apple ID '.

3. In the popup dialog, fill in your AppleID and password (do not need the account of the pin, as long as you can log in AppStore download the application of the ordinary account on the line). After filling out, click ' Add '.

4. If the account password is correct, Xcode will add the account number to the Account list, click on the left side of the account, you can list the development authorization of the account, agent said that the account is a paid account, free is not paid but can be freely debugged.

We double-click it.

5. Here the certificate and authorization file is blank, point the middle of the ' + ' sign, select ' IOS development ' in the popup item.

6. Wait a moment, the certificate is automatically generated, is named after your account.

7. And the following provisioning profiles is blank, because we have not submitted ID and device Udid, here must be blank. Click ' Done ' to turn it off.

8. Continue, this window does not care about it, we click ' Window '--' Devices '. At the same time, the real machine is connected to the computer.

9. After identifying the device, wait for Xcode to automatically open the debug mode for you, if the long time stuck here, please unlock the real machine, and in the real machine pop-up dialog box "Trust."

After the machine is ready, you can turn off the window.

Note: When the system version is too high or too low, it will appear: "Could not find Developer Disk Image" error, Solution:

The devices supported by Xcode are listed in the folder "/applications/xcode.app/contents/developer/platforms/iphoneos.platform/devicesupport".

Solution 1: Copy this file (http://download.csdn.net/detail/cvbtvbwu/9340467) to/applications/xcode.app/contents/developer/ Platforms/iphoneos.platform/devicesupport, and then restart Xcode (full exit).

Solution 2: Update Xcode to version 7.2.

10.PP files must be generated by Apple, so let's use Xcode to generate one for us. Click ' File ', ' new ', ' project ' to create a new Xcode project.

11. Select the iOS type and choose a model, ' Next '.

12. Fill in the name of the project, AppID will be automatically generated based on this. Devices if you are an iphone then choose iphone. ' Next '.

13. Select location to save, I was placed on the desktop, so point to the desktop, and then in the blank place right, ' new folder ', create a new folder to put this project.

14. Double-click to enter the new folder.

15. Click ' Create ' to save.

16. Choose the save location, immediately into the project, because Xcode7 comes with iOS9, and our equipment is only 8.3, download the SDK is 8.3, so first reduce the version, here first select 8.3.

17. Click here to select our equipment. (The device type in ' Devices ' will automatically read the settings when the new project is created, and if it is not correct, you need to select the correct type)

18. Select the device you connected to your Mac, and if you can't select it here, you'll have to go back to the 16th step to lower the version.

19. Then click ' Team ' here.

20.Xcode will automatically read out the account we added earlier and select it.

21. Then point to ' Fix IsSue ' and let Apple generate provisioning profiles for us.

22. This process is full (do not need us to fill out this form) from (fill the table) moving (also to prove your mother is your mother) ...

23. If you can see all of these options, it means that the file has been created in the distant side. We're going to download it back.

24. Click the menu ' Xcode ', ' Preferences '.

25. Double-click Open.

26. Click on the ' Refresh ' in the lower left corner, wait a moment, and Xcode will download the PP file that is far away from the other side. In the brush out of the PP file point ' right ', select ' Show in Finder '.

27. Double-click it to automatically install it on the real machine. (If your device must be attached to a Mac)

28. The window flashed and flashed back to the place just now, indicating that it has been installed. Let's check it out.

29. Point Menu ' Window ', ' Devices '.

30. In ' Devices ', right click on our real machine and choose ' Show Provisioning Profiles '.

31. Well, already seen, we click ' Done ' to turn it off.

The ' Devices ' window is also turned off.

The ' Accounts ' window is also turned off.

34. Minimize the project of Xcode because we need to use it. We're going to open paserver.

35. Click on the desktop blank and go back to the desktop and click ' Go ' to ' apps '.

36. Running Paserver 16.0

37. Running, in good condition.

38. Go back to Windows and add the iOS SDK to XE8, which is not detailed here, you can look at the old article. Once configured, we open a project where we choose a demo that comes with your own, choosing a compilation type and device.

39. Click ' Project ' and ' Options ' to configure the certificate.

40. After opening the options, select ' Version Info ' and in Cfbundleidentifier, fill in the bundle Identifier generated by the project we built in Xcode. The following version defaults to 7.1, do not change. (2015.11 in particular, this does not refer to the minimum iOS version of the app installed, which means to tell the compiler to generate info.plist in the 7.1 version, because the SDK differs greatly from one time to the other, such as xcode4.x when the value is 6.0)

41.Bundle identifier fill in the bottom left corner of the ' proisioning ', ' Target ' select ' Debug ' on ' IOS device-32bit '.

42. In ' Build Type ', select ' IOS device-32bit-development '.

"Provision profile", select your pp file, if no accident, XE8 can be correctly obtained.

"Developer Certificate", select our certificate, if no accident, XE8 can be correctly obtained.

45. All right, here is actually the same as the paid account operation, is to compile the app.

46. Running the project will soon be able to see the firemonkey icon on our real machine. See the information below to indicate that the app on the real machine is already running.

47. Attached to the app (IPad Mini2, iOS8.3)

To this, Xe8+xcode7 's real-machine debugging is complete.

Real-Machine debugging and "Could not find Developer Disk Image" problem solution

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.