Maximo Anywhere iOS Build Archive error due to new build system

 During Maximo Anywhere App Container build for iOS I was getting the below error 

Reems-Air:ios sreeja$ xcodebuild -workspace AssetManager.xcworkspace -scheme AssetManager -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"
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace AssetManager.xcworkspace -scheme AssetManager -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"

User defaults from command line:
    IDEArchivePathOverride = /Users/sreeja/IBM/Anywhere/MaximoAnywhereAppCntr/output/AssetDataManager/platforms/ios/AssetManager.xcarchive

Build settings from command line:
    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

note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
error: Building for iOS, but the linked and embedded framework 'IBMMobileFirstPlatformFoundation.framework' was built for iOS + iOS Simulator. (in target 'AssetManager' from project 'AssetManager')

** ARCHIVE FAILED **

This error is caused due to XCode project using the new Build System instead of Legacy build system which the Maximo Anywhere supports.

To Fix the issue Open the XCode project from the path e.g. where the XCode project is created during the build command.

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

or whichever application you are building for. e.x. WorkExecution, Inspection etc.

From XCode window go to Files->Project Settings and select Legacy Build System


After that run the ./build.sh command from the same MaximoAnywhereAppCntr folder path from terminal or you can also run it from XCode using Product-> Archive option.





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