Maximo Anywhere iOS build Error Archive Failed due to certificate issue

During the iOS Build after resolving the Build System issue we were getting below error causing Archive Failed error.


[INFO]  2021-4-15 12:59:23   note: Planning build

note: Constructing build description

  [INFO]  2021-4-15 12:59:25   note: Constructing build description

error: No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "XXXXXXXCSG" with a private key was found. (in target 'AssetManager' from project 'AssetManager')

  [INFO]  2021-4-15 12:59:27   error: No signing certificate "iOS Development" found: No "iOS Development" signing certificate matching team ID "XXXXXXXCSG" with a private key was found. (in target 'AssetManager' from project 'AssetManager')



  [INFO]  2021-4-15 12:59:27   

  [ERROR]  2021-4-15 12:59:27   ** ARCHIVE FAILED **


  [ERROR]  2021-4-15 12:59:27   xcodebuild: Command failed with exit code 65

  [ERROR]  2021-4-15 12:59:27   Command failed: /Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/node_modules/cordova/bin/cordova build ios  --device --release --packageType=enterprise --codeSignIdentity="iPhone Developer" --provisioningProfile=adff6abe-b00b-4137-bbf0-xhsld9d04631d --developmentTeam=XXXXXXXCSG--buildFlag='VALID_ARCHS=arm64 CURRENT_ARCH=arm64 ONLY_ACTIVE_ARCH=YES'
verb mfp-before-prepare Performing MFP before prepare hook.
verb mfp-before-prepare Invoking platform specific hooks.
verb mfp-config-xml Initializing get, set, and delete methods.
verb mfp-after-prepare Preforming MFP after prepare hook.
verb mfp-after-prepare Adding MFP platform version to config.
verb mfp-after-prepare Invoking platform specific hooks.
verb mfp-config-xml Initializing get, set, and delete methods.
verb ios-after-prepare Performing iOS after prepare hook.
verb ios-after-prepare Adding SDK checksum to configuration.
verb after-prepare Parsing config.xml for update tags.
verb after-prepare Updating files based on config.xml update tags.
verb after-prepare Creating checksum file.
verb ios-after-prepare Updating /Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/output/AssetDataManager/platforms/ios/AssetManager/Resources/mfpclient.plist with properties.
verb after-prepare Parsing server information.
verb ios-after-prepare Adding the MFP Frameworks to the Embedded Binaries section of the project
verb ios-after-prepare Building platform specific static app properties.
verb after-prepare Determining MFP client custom init value.
verb mfp-after-prepare Preforming MFP after prepare hook.
verb mfp-after-prepare Invoking platform specific hooks.
verb mfp-config-xml Initializing get, set, and delete methods.
verb ios-after-prepare Performing iOS after prepare hook.
verb ios-after-prepare Removing non-embedded frameworks from embedded frameworks section since they automatically get added
verb Performing MFP before compile hook.
verb No web resource encryption requested
** ARCHIVE FAILED **

xcodebuild: Command failed with exit code 65


Apparently XCode was not able to verify the certificate from the provisioning profile. If we Opened the XCode Project and navigate to Signing & Capabilities section we can see an error message that Doesn't include signing certificate "Apple Development"


This error was coming even though all the provisioning profiles were already present in the /IBM/Anywhere/MaximoAnywhereAppCntr/signing folder.

Also the signing certificate was installed in MaxOS Key Chain Access.

If we import the same Provisioning profile file again using the drop down menu the error disappears as you can see below.

After this we cannot run the ./build.sh command from terminal as the project workspace gets purged during the build process. Therefore we need to use the Product->Archive option from XCode and run the build directly from XCode.

or we can also run the command that failed during previous build from Terminal. e.g.

Go to workspace folder and run the below command which had failed, previously. Copy the command from the error log directly.

cd /Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/output/AssetDataManager/platforms/ios/

xcodebuild -workspace "Asset Manager.xcworkspace" -scheme "Asset Manager" -configuration Release -destination generic/platform=iOS -archivePath "AssetManager.xcarchive" archive CONFIGURATION_BUILD_DIR=/Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/output/AssetDataManager/platforms/ios/build/device SHARED_PRECOMPS_DIR=/Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/output/AssetDataManager/platforms/ios/build/sharedpch "VALID_ARCHS=arm64 CURRENT_ARCH=arm64 ONLY_ACTIVE_ARCH=YES"

This time the build was successful and we can see the Archive file generated at the below location

/Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/output/AssetDataManager/platforms/ios/AssetManager.xcarchive

This Archive file can be used to generate the IPA file which in our case we needed to distribute using the MDM solution.


 










Comments

Post a Comment

Popular posts from this blog

BMXAA6713E - The record could not be retrieved from the database. Error

Getting below error in Maximo System Logs [ERROR] [MAXIMO] [] BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 17006. The record could not be retrieved from the database. See the log file for more details about the error. java.sql.SQLException : Invalid column name at oracle.jdbc.driver.OracleStatement.getColumnIndexPrimitive(OracleStatement.java : 3810 ) at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java : 3777 ) at oracle.jdbc.driver.InsensitiveScrollableResultSet.findColumn(InsensitiveScrollableResultSet.java : 268 ) at oracle.jdbc.driver.GeneratedResultSet.getObject(GeneratedResultSet.java : 570 ) at psdi.mbo.MboSet.getNextRecordData(MboSet.java : 3457 ) at psdi.mbo.MboSet.fetchMbosActual(MboSet.java : 2941 ) at psdi.mbo.MboSet.fetchMbos(MboSet.java : 2898 ) at psdi.mbo.MboSet.getMbo(MboSet.java : 2114 ) at psdi.app.common.purchasing.FldPurContractRefNum.validate(FldPurContractRefNum.java : 86 ) at psdi.mbo.MboVa...
Read more

Rebuilding Maximo Text Indexes due to Query performance issues

Image
Sometimes it is necessary to rebuild text indexes after database move or copy from Prod to other instances. IBM does have an article for Rebuilding Oracle Text Indexes . Basically this process drops all the domain indexes and recreates them.  These are the steps are just walkthrough with the same process in detail. 1. Follow the steps in the above article to remove any DBMS jobs Remove any occurrences of DBMS_JOB Determine how many DBMS_JOBS are running by executing this from SQLPLUS logged in as the schema owner: select job, substr(what,1,80) from user_jobs; For each result where "what" contains maximo_ts_job, execute the following commands: begin dbms_job.remove(####); commit; end; / Substituting one of the job numbers from the select for the ####. 2. Change the job  Change to use DBMS_SCHEDULER Recreate the job submission procedure and run it: CREATE OR REPLACE PROCEDURE maximo_ts_job_call AS BEGIN   dbms_scheduler.create_job(   job_name => 'MAXIMOTSSYNC', ...
Read more

List of things checked by Maximo Integrity checker

Maximo Integrity checker is a pretty useful tool to identify issues in Maximo database  Below are some of the things checked by integrity checker and the sample errors returned. 1. Extra tables in database which are not part of Maximo BMXAA0442W -- Warning - BMXAA0475W -- The following tables should be removed from the database because they do not exist in the schema: Sun May 30 12:08:47 GST 2021    APPLICATIONAUTH_BKP    DOCLINKS_POBKP    ABC_MIGR_TEST 2. Missing Indexes BMXAA0443E -- Error - BMXAA0465E -- The following indexes are missing from the database. Use the Database Configuration application to remove the index definition. 3. Missing user groups, invalid users etc BMXAA0455E -- The following users should be removed because they are not authorized. To correct this error, run the Integrity Checker in repair mode. BMXAA0458E -- The following user groups were not found in the MAXGROUPS table. Run the Integrity Checker in repair mode. 4. Invalid M...
Read more