General Known Issues

Product version: AppBuilder 3.7.2

Released: April 24, 2017

AppBuilder is known to have the following common issues.

Check frequently for updates and additions to this list.

If you identify an issue that is not on the list, use our forums to report it. You can also browse the community to check for other issues that might not have made it into this list.

Apps

AppBuilder is known to have the following issues with apps and solutions from earlier releases.

  • In the in-browser client, if you rename your solution and click the Back button in the browser, a server error is added to the log and an error message is shown.
    After you rename your solution, its URL is updated with the new name and the solution is reloaded. If you click the Back button, the in-browser client attempts to access your solution via its previous URL. This causes an internal server error and the in-browser client cannot load your solution.
    Workaround: Click Forward in the browser to return to your renamed solution. Alternatively, navigate to https://platform.telerik.com, log in, if needed and open your renamed solution from the Dashboard.

  • When you pull from a remote repository that already contains another app, this creates two apps in the solution.
    When changing the repository remote URL, Git pulls everything from the new remote and attempts to merge it.
    Workaround: None. Avoid changing your repository remote URL to an app different from the one you are currently working on.

Files and Folders

AppBuilder is known to have the following issues with files and folders from earlier releases.

  • Long file and folder names might cause exceptions.

  • When you import files from an archive created on a macOS system, AppBuilder also imports any system files and folders such as __MACOSX and .DS_Store. This might prevent AppBuilder from building your app.
    By default, all archives created on a macOS system contain system files and folders such as __MACOSX and .DS_Store. When you import files from an archive created on a macOS system, AppBuilder also imports any Mac-specific system files and folders. When you import a custom plugin from such an archive, system folders such as __MACOSX are also added in the Plugins folder of your app. Plugman might identify such folders as separate custom plugins and in this case, searches the folder for a valid plugin.xml file. When Plugman cannot locate a valid plugin.xml file, it cannot complete the plugin installation and AppBuilder cannot complete the build for your app.
    Workaround: After you import files from an archive created on a macOS system, make sure to remove any Mac-specific system files and folders from your app. For example, delete __MACOSX and .DS_Store.

  • You cannot revert the addition of empty folders. Unexpected results occur when using the Revert command on Folders.
    The Git Version Control system works with files only.
    Workaround: None.
    This issue might cause problems such as:

    • Reverting a folder fails when trying to Revert a new or renamed folder.
    • Reverting a folder that was moved fails, the folder created during the move cannot be deleted.
    • Reverting Rename of a folder that contains files creates two folders.
    • Reverting files in a renamed folder causes the files to be duplicated and both the original and the renamed files are kept - in this case you have to delete manually the files you do not need.

See Also

Start a free trial Request a demo
Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.