Troubleshooting

improve this page | report issue

Overview

Find answers for some of the problems you may encounter while using IBM Digital App Builder.

  • In case of any error, refer to:

    • log.log file for the respective platform folder path:

      • On mac OS: ~/Library/Logs/IBM Digital App Builder/log.log.

      • On Windows: %USERPROFILE%\AppData\Roaming\IBM Digital App Builder\log.log.

    • applog.log for your app related logs which can be found in <APP LOCATION>/ibm/applog.log.

  • Failure to create a Data set for a Microservice using a swagger file.

    For the first time users of the Builder, the microservice creation may fail due to network latency. To get rid of this, follow these steps:

    1. Open command prompt and go to the installed location of the app.
    2. cd ibm\adapterGenerator
    3. Run the following command windows> execute.bat . mac>./execute.sh .
    4. On successful execution of the above command, you can start using microservice (swagger file) from the Digital App Builder.
  • Failure to preview the app on Windows.

    In the Digital App Builder, go to Settings > Repair project and click Rebuild Dependencies and Rebuild Platforms buttons.

  • Android App does not work after adding the List component to the app.

    This is due to Android WebView version is less than 68.X.XXXX.XX. To resolve this, upgrade the Android WebView version to 68.X.XXXX.XX or above.

  • In MacOS, preview of the app on an Android simulator fails with app crashes. With the following error:

    java.lang.RuntimeException: Unable to create application com.ibm.MFPApplication: java.lang.RuntimeException: Client configuration file mfpclient.properties not found in application assets. Use the MFP CLI command 'mfpdev app register' to create the file.

    To resolve this, from the terminal navigate to the app ionic directory and run the following commands:

    ionic cordova plugin remove cordova-plugin-mfp ionic cordova plugin add cordova-plugin-mfp

    and preview from the Digital App Builder again.

  • Unable to generate the adapter when importing swagger json/yaml file.

    Error when importing swagger json/yaml file and the error is due to Maven dependency.

    Ideally all the Maven dependencies if does not exists are downloaded and installed behind the scene. But there are somecases where Maven fails because of multiple Maven versions in the system. To solve this issue follow these steps:

    a. Go to the Aa\pp location and open execute.sh / execute.bat file depending on the OS. (<APP_LOCATION>\ibm\adapterGenerator)

    b. Edit all the call %MAVEN_HOME% clean install to call %MAVEN_HOME% -U clean install.

      Adding `-U` will force maven to check any external dependencies that need to be updated based on the POM file.
    
  • Prerequisites Check fails for Android Studio even when it is installed.

    Make sure you have the android executable (<path to android sdk>/tools) in the path and check for the prerequisites.

  • App creation and preview issue on Windows 7

    You may get an error when trying to create a new app in a different disk drive location other than C:.

    Make sure you create your app project under the drive C://<your folder name/app name>.

  • Digital App Builder crashes with red screen.

    If you see a crash wiht red screen, check the logs at this location:

    • On MacOS- /Users/<username>/Library/Logs/IBM Digital App Builder/log.log
    • On Windows - C:\\Users\<username>\AppData\Roming\IBM Digital App Builder\log.log

    If the error is about a getPath from rendered.js, it is a known electron issue.

    This happens randomly.

    Please restart Digital App Builder and your scenario should work.

Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.
Last modified on February 12, 2020