Hello,

I'm having this error when generating native app for IOS (for Android is OK):

...

remote: Compressing objects:  95% (19/20)            
remote: Compressing objects: 100% (20/20)            
remote: Compressing objects: 100% (20/20), done.        
remote: Total 27 (delta 16), reused 9 (delta 5), pack-reused 0        
From https://github.com/CocoaPods/Specs     
e3432ec1c9a..93b94ec45e2  master     -> origin/master
** ARCHIVE FAILED **
The following build commands failed:
Ld /Users/mabs04/Library/Developer/Xcode/DerivedData/CEP-dfzvzbwwxxlllverzmybgjzwrlzg/Build/Intermediates.noindex/ArchiveIntermediates/CEP/IntermediateBuildFilesPath/CEP.build/Release-iphoneos/CEP.build/Objects-normal/arm64/CEP normal arm64
(1 failure)
/tmp/build/source/platforms/ios/build/sharedpch,-UseModernBuildSystem=0

[2019-02-19T15:07:47.220Z] [ERROR] Build failed with the following error: An unexpected error has occurred while generating your application. Please try again. If the problem persists, contact OutSystems Support.
[2019-02-19T15:07:47.220Z] [INFO] Zipping application source...
[2019-02-19T15:08:01.371Z] [INFO] Application was not successfully generated!
[2019-02-19T15:08:01.391Z] [INFO] Execution time: 196215ms

Anyone has an idea what could be the reason?

Thanks.

Miguel Oliveira wrote:

Hello,

I'm having this error when generating native app for IOS (for Android is OK):

...

remote: Compressing objects:  95% (19/20)            
remote: Compressing objects: 100% (20/20)            
remote: Compressing objects: 100% (20/20), done.        
remote: Total 27 (delta 16), reused 9 (delta 5), pack-reused 0        
From https://github.com/CocoaPods/Specs     
e3432ec1c9a..93b94ec45e2  master     -> origin/master
** ARCHIVE FAILED **
The following build commands failed:
Ld /Users/mabs04/Library/Developer/Xcode/DerivedData/CEP-dfzvzbwwxxlllverzmybgjzwrlzg/Build/Intermediates.noindex/ArchiveIntermediates/CEP/IntermediateBuildFilesPath/CEP.build/Release-iphoneos/CEP.build/Objects-normal/arm64/CEP normal arm64
(1 failure)
/tmp/build/source/platforms/ios/build/sharedpch,-UseModernBuildSystem=0

[2019-02-19T15:07:47.220Z] [ERROR] Build failed with the following error: An unexpected error has occurred while generating your application. Please try again. If the problem persists, contact OutSystems Support.
[2019-02-19T15:07:47.220Z] [INFO] Zipping application source...
[2019-02-19T15:08:01.371Z] [INFO] Application was not successfully generated!
[2019-02-19T15:08:01.391Z] [INFO] Execution time: 196215ms

Anyone has an idea what could be the reason?

Thanks.

Hello Miguel,


Is it possible this app is not yet made compatible with mabs 4.0 ? 

https://success.outsystems.com/Support/Release_Notes/Mobile_Apps_Build_Service

https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Customize_Your_Mobile_App/Use_Custom_Splash_Screens#for-ios


That could explain the reason why it succesfully generates for android and not for IOS.


If your platform is up to date you can manually instruct MABS to use the older version. 

https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Generate_and_Distribute_Your_Mobile_App


Michael de Ruijter wrote:

Miguel Oliveira wrote:


From https://github.com/CocoaPods/Specs     
e3432ec1c9a..93b94ec45e2  master     -> origin/master
** ARCHIVE FAILED **

Is it possible this app is not yet made compatible with mabs 4.0 ? 

I think this is because Console Log plugin is not compatible with new build service (at least in older P10 versions), or there are some conflicting version numbers. As Michael said, choosing MABS version is possible, but only from Platform Server 10.0.1005.0 and onwards.

I created another thread to component support for this: https://www.outsystems.com/forums/discussion/45672/console-log-plugin-cocoapods-specs-archive-fail/

Quick workaround to get builds to succeed, is to remove this plugin (and of course, lose some of the debug features).

For mobile applications, javascript console.log can be hijacked in such manner that the log history can be preserved. Only problem with user-space javascript solution is that the load order matters and if not done correctly, there are probably some cases during page transitions where this approach would "skip a beat" (= not log everything). Native side approach for this thing is good because this Console Logs plugin seems to extend platform's native logging functionality, therefore reliably capturing all log entries.

br,

-Mikko(N)