Ios – Apple Developer account error: Maximum number of certificates generated (development)

I had the same problem: I first downloaded my certificates to my small MacBook while on the run. When trying to install the certificates on my iMac... then I ran into the problems described on this page.

After spending hours pulling my hair out like many of you, I performed the following steps to fix it:

1. Close all your stuff except your webpage that should be logged into App Dev center.

2. Open Xcode. Click WINDOW > ORGANIZER. Then click the Devices tab and select "Provisioning Profiles" on the left. That should bring up your provisioning profiles. Highlight one by one (if more than 1), right click and delete profile. Yes, just do it! Delete them all! (I kept making a new one after a new one trying to make the thing work.)

3. From the first page you see after logging into the App Dev Center on the right side click "iOS PROVISIONING PORTAL" > (do not "launch assistant"). Instead click on the left side. Select CERTIFICATES. You will probably have just one line listed with your name/company - from there click on the right side REVOKE. Click OK to verify that's what you want to do.

4. On the same page click DEVICES. Click the box next to your device you are trying to provision and click REMOVE SELECTED. Again click OK to verify.

5. Wait about 2 minutes to let Apple do their thing.

6. Now click on "HOME" that is on the left side navigation.

7. Click "Launch Assistant"

8. create a new app ID - call it whatever you want. Just make sure it's unique enough to know that's the one you just created because the others you've been messing with all day will not be deleted from Apples Dev Center.

9. You should be able to follow the rest of the Assistant without troubles -- the main thing is you just had to delete your old provision profiles and start over.

Good Luck!

Here's what I'm doing:

1) In my framework CMakeLists.txt file, I have the following:

IF (APPLE)
       SET_TARGET_PROPERTIES( MyFramework PROPERTIES FRAMEWORK true)
       SET_TARGET_PROPERTIES( MyFramework PROPERTIES
           XCODE_ATTRIBUTE_INSTALL_PATH @executable_path/../Frameworks/  )
ENDIF (APPLE)

The second "set_target_properties" line configures the framework to always be looked for in the application bundle in the Frameworks sub-folder.

2) In my top-level CMakeLists.txt file, I add setup a unified binary output directory:

SET (CMAKE_LIBRARY_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin)
SET (CMAKE_RUNTIME_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin )
SET (CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${PROJECT_BINARY_DIR}/Bin )

3) Then, in my applications' CMakeLists.txt file, I have the following:

IF (APPLE)
       ADD_CUSTOM_COMMAND(
               TARGET MyApp
               POST_BUILD
               COMMAND ${PYTHON_EXECUTABLE}
               ARGS ${CMAKE_HOME_DIRECTORY}/CopyFramework.py
               --binary ${PROJECT_BINARY_DIR}/Bin
               --framework MyFramework.framework
               --app MyApp.app

    )
ENDIF (APPLE)

This calls out to my python script, which does the work of assembling the src and dest paths, and actually copying the Framework.

The final trick is that since this is a Mac only thing, I can rely on an Xcode environment variable within the Python script:

           config= os.environ["CONFIGURATION"]

This allows me to assemble the complete path to the actual binary locations of the framework and the app.

The one thing I wish was that there was a CMake variable that would expand to the current Config within the context of the ADD_CUSTOM_COMMAND... It'd be nice to not have to resort to using the Xcode environment variable.