Known Issues with Mobile Devices and Platforms

Product version: AppBuilder 3.7.2

Released: April 24, 2017

AppBuilder is known to have the following issues with mobile devices and platforms.

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.

General

AppBuilder is known to have the following issues with devices from earlier releases.

  • You cannot debug your NativeScript project on multiple connected devices simultaneously.
    Workaround: Debug on one device or emulator at a time.

  • You cannot run your app on a connected device, if the device is also connected to a wireless hosted network that does not have Internet access.
    When you build and deploy your app on a connected device that is also connected to a wireless hosted network with no Internet access, the app does not run properly. On Android devices, an application error pops up. On iOS devices, the splash screen loading cannot complete and the application never loads and runs.
    Workaround: Disconnect the device from the hosted network or disable wi-fi and re-deploy the app.

  • Sometimes the AppBuilder clients do not show one or more connected devices.
    Workaround: Disconnect the device and plug it back in.

iOS

AppBuilder is known to have the following issues with iOS from earlier releases.

  • On iOS 8.x devices in the Platform companion app, tapping a button might not work at first.
    The Platform companion app is based on Kendo UI. A known issue in Kendo UI prevents button events from triggering as expected on iOS 8.x devices.
    Workaround: Tap the button until the button event fires and the app works as expected.

  • On iOS devices, sometimes you cannot LiveSync your changes over the air or via cable to the NativeScript developer app.
    When you attempt to perform a LiveSync operation, the NativeScript developer app needs to restart. To complete this, the developer app relies on Safari or the Cordova developer app, if installed. If the Cordova developer app is not installed on your device, sometimes the NativeScript developer app might not be able to restart using Safari.
    Workaround: Install the Cordova developer app on your device.

  • On iOS devices, sometimes you cannot LiveSync your changes over the air or via cable to NativeScript apps.
    When you attempt to perform a LiveSync operation, your NativeScript app needs to restart. To complete this, NativeScript relies on Safari or the Cordova developer app, if installed. If the Cordova developer app is not installed on your device, sometimes your NativeScript app might not be able to restart using Safari.
    Workaround: Install the Cordova developer app on your device.

  • On iOS devices, you cannot capture and send screen shots for external views with the Telerik AppFeedback plugin.
    Workaround: None.

  • If your project contains a shell script (for example, a Python script) which begins with #!, you cannot publish it to iTunes Connect from AppBuilder.
    Apple requires that shell scripts which begin with #! inside your application package are code signed. AppBuilder does not code sign such files automatically.
    Workaround: If you do not need these files for your project, remove them. If you need these files during development, add them yo your .abignore file and publish your app from the command-line interface.

  • Sometimes when you debug your NativeScript project on an iOS device, the app might exit on device and the debug session might end.
    Workaround: Restart the app and try again.

  • When you debug on iOS 7.x devices, you cannot view and examine the network requests for your app. The Network pane remains blank.
    Workaround: None.

  • When you deploy different apps with the same application identifier via QR code, the app installs successfully but when launched, shows the contents of the previously installed app.
    Workaround: Use the three-finger refresh gesture to refresh the contents of the app.

  • Sometimes an error might be logged when working with connected iOS devices.
    Workaround: If LiveSync stops working, disconnect the device and plug it back in.

  • On iOS 7 devices and in the device simulator, the Kendo UI mobile app with data visualization sample app might not render properly. The header might be too large and the footer might be truncated.
    By default, the StatusBar plugin is disabled for the Kendo UI project templates and sample apps. This might cause styling issues on iOS 7 devices and in the device simulator.
    Workaround: Initialize your Kendo UI application with the black translucent status bar style. For example:

    app.application = new kendo.mobile.Application(document.body, { layout: "tabstrip-layout", statusBarStyle: "black-translucent" });
      }, false);`
    
  • When you deploy multiple apps signed with one Ad Hoc provisioning profile and app ID on the same device, you might not be able to run the apps properly.
    If you build and deploy an app on device where another app built with the same provisioning profile and app ID is already installed, the app that was installed earlier is loaded on first run.
    Workaround: Use the three-finger refresh gesture to get the correct app.

  • In iOS, file paths are case-sensitive. Keep this in mind when adding references.

  • After adding your application package to iTunes manually, iTunes shows the default iTunes application icon for your app instead of any of the iOS application icons set in AppBuilder.
    For Ad Hoc distribution, application packages are recommended to contain iTunes-specific artwork. Without this artwork, iTunes displays the default iTunes application icon for the app. AppBuilder does not let you configure the iTunes-specific artwork for applications built with an Ad Hoc provisioning profile.
    Workaround: Configure the artwork manually.

    1. On your local file system, create an empty folder named App_Resources.
    2. In the newly created folder, create an empty folder named iOS.
    3. In the iOS folder, create the following two image files.
      File Name Image Dimensions File Type
      iTunesArtwork 512x512 pixels PNG
      iTunesArtwork@2x 1024x1024 pixels PNG
    4. Remove the file extensions for the image files.
    5. Run AppBuilder and open your project.
    6. If your are running the classic Windows desktop client or the in-browser client, perform the following steps.

      1. On your local file system, zip the App_Resources folder and its contents.
      2. In AppBuilder, in the Project Navigator, right-click the project node, select AddFrom Archive and upload the zipped archive.
      3. In the Project Navigator, right-click the project node and select Edit ConfigurationiOS Info.plist.
      4. In the code, locate the <string>icon-76@2x.png</string> line.
      5. Insert the following lines after the </string> tag.

        <string>iTunesArtwork</string>
        <string>iTunesArtwork@2x</string>
        
      6. Save your changes.
    7. If you are running the extension for Visual Studio, perform the following steps.

      1. From your local file system drag the App_Resources folder and drop it on the project node in the Solution Explorer.
      2. If you cannot drag and drop files and folders in the Solution Explorer, copy the item from the file explorer and paste it on the project node in the Solution Explorer.
      3. If prompted, confirm that you want to replace files.
      4. In the Solution Explorer, right-click the project node and select Edit ConfigurationiOS Info.plist.
      5. In the code, locate the <string>icon-76@2x.png</string> line.
      6. Insert the following lines after the ` tag.

        <string>iTunesArtwork</string>
        <string>iTunesArtwork@2x</string>
        
      7. Save your changes.

      If you later decide to distribute your app in the App Store, you need to remove the iTunes-specific artwork. Remove all references to it from Info.plist and remove it from the App_Resources folder. If you are running the classic Windows desktop client or the in-browser client, you need to export your project, remove the iTunes-specific files from the archive, zip it again and recreate your project from archive.

Android

AppBuilder is known to have the following issues with Android from earlier releases.

  • On some Android devices, apps with enabled Telerik AppFeedback plugin might stop responding and might need to close when you invoke the Telerik AppFeedback wizard.
    Workaround: None.

  • In the extension for Visual Studio, you cannot use the built-in AppBuilder debug tools to debug Angular 2-based NativeScript apps on connected Android devices. When you attempt to debug the app, it becomes unresponsive on the device and needs to close.
    Workaround: Use the Microsoft Visual Studio debug tools instead.

  • After you build your app for Android, the version code for the application package differs from the version code you specified in the Properties dialog or with the appbuilder prop set command. The final version code has an additional digit appended at the back—2.
    Apache Cordova automatically appends a specific number to the version code based on the target Android SDK and architecture. This is not controlled by AppBuilder and is an implementation decision made entirely by the Apache Cordova team. For more information, see https://issues.apache.org/jira/browse/CB-8976.
    Workaround: None.

  • If the config.xml file of your app contains comments with dashes, your builds cannot complete.
    Workaround: Remove any dashes placed inside comments.

  • If a plugin for NativeScript contains .gz files, you cannot build for Android.
    Workaround: Remove the plugin or migrate it to a version which does not contain .gz files and try again.

  • The Cordova developer app for Android becomes unresponsive and closes when you test QR code encoding.
    Workaround: To test QR code encoding, build and deploy your project as an application package.

  • In the Cordova developer app for Android, you cannot share images to Facebook with the SocialSharing plugin.
    Workaround: None.

  • On Android 5.1 devices, when you restore a minimized app developed with NativeScript, the app becomes unresponsive and closes.
    Workaround: Restart the app.

  • When you build your app with the Release build configuration, it might stop working as expected.
    By default, when you create a new project in AppBuilder, all Android permissions are disabled. When you build with the Debug build configuration, AppBuilder enables LiveSync which enables the INTERNET Android permission. When you build with the Release build configuration, AppBuilder disables LiveSync which removes the INTERNET Android permission, if you have not already enabled it manually for your project.
    The INTERNET Android permissions is required for Android hybrid apps to work properly. Disabling this permissions causes hybrid apps to stop working.
    Workaround: Enable the INTERNET Android permission manually. For more information, see Configure Your Project and Android Project Properties.

  • You cannot debug your NativeScript projects on Android devices and emulators in the command-line interface.
    Workaround: Debug your project in the classic Windows desktop client or the extension for Visual Studio.

  • After you add files and folders to your Android sub-directory in the App_Resources directory, AppBuilder can no longer build your project.
    This issue might be caused by one of the following Android limitations:

    • The names of resource files and folders must be lowercase.
      If the name of your file or folder contains an uppercase character, AppBuilder cannot build your project.
    • During the build process, all resources from App_ResourcesAndroid are copied to the res directory in the application package.
      If your project contains another res directory, this affects the build operation and it cannot complete.
      Workaround: Make sure that App_ResourcesAndroid contains only files and folders with lowercase names and that your project does not contain any res folders.
  • On Android 5.0 devices with multiple users, LiveSync via cable connection works only for the administrator user.
    Workaround: When you need to LiveSync your changes via cable connection, switch to the administrator user. Alternatively, LiveSync your changes with the three-finger refresh gesture.

  • On connected Android devices with disabled logcat, you cannot LiveSync changes.
    Some custom Android ROMs might disable logcat by default. When logcat is disabled, you cannot LiveSync changes on Save via cable connection to Android devices.
    Workaround: Disconnect the device, enable logcat, reboot the device and reconnect it to your system. For more information, see Enabling Logcat in Custom Android Roms and logcat not showing the log for my app.

  • On connected Android devices with disabled logcat, the device log is always empty.
    Some custom Android ROMs might disable logcat by default. When logcat is disabled, you cannot track your application activity in the device log.
    Workaround: Disconnect the device, enable logcat, reboot the device and reconnect it to your system. For more information, see Enabling Logcat in Custom Android Roms and logcat not showing the log for my app.

  • When you are running the Kendo UI mobile app with data visualization sample app on Android devices, you cannot view chart values. You can tap the chart to select the value, but the label for the value does not appear.

  • If you are running tools for management of Android mobile devices on your system (for example, Samsung Kies, HTC Sync, Sony Ericsson PC Suite), you might experience various issues when working with connected Android devices.
    Both AppBuilder and tools for management of Android devices install and launch adb.exe on your system and conflicts might arise between the adb.exe instances launched by AppBuilder and the tools. When you attempt to work with Android devices from AppBuilder, these conflicts might cause a number of issues, including but not limited to the following.

    • When you disconnect a device from your system, AppBuilder might continue to recognize the device as connected.
    • When multiple Android devices are connected, AppBuilder might not deploy your app on all connected devices.
    • When you connect multiple device, AppBuilder might not recognize one or more devices as connected.
    • LiveSync might stop working properly.

    Workaround: Before running AppBuilder, verify that you have closed all programs that run or might need to launch their own instance of adb.exe.

Windows Phone

AppBuilder is known to have the following issues with Windows Phone from earlier releases.

  • After you re-deploy a Windows Phone 8.1 app via QR code, the contents of your app do not refresh.
    Workaround: Increase the version in the Project Properties, re-build and re-deploy the app.

  • If you have started development from a Kendo UI-based project template, your app might not look and behave properly on Windows Phone 8.1 devices.
    Workaround: Update Kendo UI to the latest stable official package. For more information about how to update Kendo UI in your project, see Update the Code Libraries in Your Project.

  • When you attempt to run your app on Windows Phone 8 device, the app becomes unresponsive and needs to close.
    AppBuilder lets you build an app with the Windows Phone 8.1 SDK. If you deploy such an app on a Windows Phone 8 device, the app cannot run. It immediately becomes unresponsive and needs to close.
    Workaround: If you want to test your app on a Windows Phone 8 device, verify that the target SDK is Windows Phone 8.0. For more information, see Configure Your Project and Project Properties for Windows Phone Devices.

  • In apps developed with Kendo UI, console.log does not produce output on Windows Phone devices.
    Workaround: In your deviceReady event, define console.log as an object and call it in your code. For example:

    window.APP.log = console.log;
    
  • When you build for Windows Phone, multiple warnings might appear in the AppBuilder output.
    Workaround: None. If the build completes successfully, you can continue your work.

  • On Windows Phone devices, the Kendo UI Core footer might be displaced and the icons might appear truncated at the bottom.
    When you run your Windows Phone app on device, the footer might render below the bottom of the screen and the icons might appear truncated.
    Workaround: Try changing the target Windows Phone SDK to 8.1 from the Project Properties. If you cannot change the target SDK, hide the status bar in your code.

    1. Verify that the core StatusBar plugin is enabled.
      For more information about managing the core plugins, see Enable and Disable the Core Plugins.
    2. In your deviceready event listener, add the following line: StatusBar.hide();.
    3. Re-build and re-deploy your app.
  • The built-in Kendo UI mobile app and Kendo UI mobile app with data visualization sample apps run in different color schemes in the Windows Phone device simulator and on a physical Windows Phone device.
    The built-in Kendo UI mobile app and Kendo UI mobile app with data visualization templates run in a light color scheme in the Windows Phone device simulator and in a dark color scheme on a physical Windows Phone device.
    Workaround: None.

  • When you reconnect a Windows Phone device, AppBuilder might not recognize it and might not list it in the devices list.
    Workaround: Restart your AppBuilder client.

  • You cannot connect multiple Windows Phone devices.
    The extension for Visual Studio and the classic Windows desktop client recognize only one connected Windows Phone device at a time.
    Workaround: None.

  • On macOS systems, on Windows Phone simulated devices, the device simulator always shows the splash screen in portrait mode even if the device is currently rotated to landscape. After the splash screen disappears, the device pane returns to its initial orientation.
    Workaround: None.

  • On macOS systems, if you are running your app in landscape mode and you change the simulated device to Windows Phone 8 or Windows Phone 8.1, the app does not render properly. The application runs in portrait mode but the device pane remains in landscape mode and a gap appears between the application view and the border of the screen.
    Workaround: Restart the device simulator.

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.