Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Mobile build for Android hangs

SA-29857

Summary



Building a mobile app for Android hangs. It has been running for over 12 hours.


Error Messages



On the screen user sees the message Downloading Build for ever.



When we enable SSL debug through JVM flag  -Djavax.net.debug=all, we notice the following error in the application server log

2016-10-25 17:14:14,758 [.PegaWorkManager : 1] [  STANDARD] [                    ] [        SSL:01.01.01] (.ssl.CompositeX509TrustManager) DEBUG  Admin@GCS - certificate not trusted by TrustManager: com.ibm.jsse2.yc@6b3a0fe7
com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: 
    java.security.cert.CertPathValidatorException: The certificate issued by CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US is not trusted; internal cause is: 
    java.security.cert.CertPathValidatorException: Certificate chaining error​

...

Caused by: 
java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: 
....


com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
    at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_28ccb2185309b8c9c6d59a05ed51acae.step5_circum0(ra_action_pyinvokerestconnector_28ccb2185309b8c9c6d59a05ed51acae.java:1631)



Steps to Reproduce

  1. Log on to Pega.
  2. Open any application.
  3. Go to the Mobile Tab.
  4. Fill in the values for "Unique application identifier", "Description" and "Release version:" 
  5. Add and Select "Distribution P12 file" 
  6. Click Create Build button.
  7. Notice the Build finishes with 100% and displays downloading and it hangs there.


Root Cause



From September 2016 onwards, the build Server operates  via SSL only. Production Build Server uses certificate issued by Go Daddy - in order to establish connection with it, Java trust store (cacerts) on Pega server needs to contain entry for Go Daddy Root CA. CN = Go Daddy Root Certificate Authority - G2 O = GoDaddy.com, Inc. L = Scottsdale S = Arizona C = US


Resolution



Perform the following local-change: 

To delete the hanged mobile build, Create and run an activity that does Obj-Delete-By-Handle in order to remove a stuck mobile build. The handle would be  like this

DATA-MOBILE-BUILD RULE-APPLICATION <ApplicationName> <ApplicationVersion>!PRPC-HYBRID-<ANDROID/IOS>

For e.g.

ATA-MOBILE-BUILD RULE-APPLICATION MYAPP 01.01.01!PRPC-HYBRID-ANDROID)


Make sure to check the 'Immediate' checkbox with Obj-Delete-By-Handle.

In this case my application name is "MYAPP" and version is "01.01.01" . You can also view the column "PZINSKEY" of the Database table "PR_DATA_MOBILE_BUILD" for the handle


Run the activity To delete the hanged mobile build.

Next step is to import the Pega Mobile build server certificates.

Download the certificates from the Pega Mobile buildserver URL  https://mobilebuildserver.pega.com/buildserver



Import the certificates in the application server truststore and restart the application server.

Published November 4, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us