Scan considerations

This topic describes restrictions and considerations that may affect your scans.

To learn about considerations that are specific to scanning IBM® MobileFirst Platform projects, see Scanning an IBM MobileFirst Platform project. To learn about considerations that are specific to scanning Xcode projects, see Scanning an Xcode project (iOS projects only).

Windows

Attempts to run some actions in AppScan Source for Development (Eclipse plug-in) (for example, launching a scan or starting actions that require a login) can result in this error message (or one that is similar to it):

Unable to link native library shared-win32-x64.dll. 
You may need to install an appropriate Microsoft Visual C++ 
2010 Redistributable Package for your system.

When running on a 64-bit Java™ Runtime Environment, this typically indicates that the 64-bit Microsoft™ Visual C++ runtime library is unavailable. To resolve this problem, install the Microsoft Visual C++ 2010 Redistributable Package, available at http://www.microsoft.com/en-ca/download/details.aspx?id=14632.

Linux

On Linux™, Eclipse requires the installation of a third-party component in order to render browser-based content. Without this component, AppScan Source for Development may exhibit symptoms such as a hang after login or a fail during product use. See Enabling browser-based content on Linux for AppScan Source for Development installed to Eclipse Version 3.7 or later for more information.

macOS

In order to scan Xcode projects that have dependencies, the project must be built a single time in Xcode in order to create the dependencies needed by the AppScan Source scanner. For example, if you have an IBM MobileFirst Platform-generated Xcode project, in order to scan the iPhone or iPad environment, or any Xcode project beneath one of those environments, you must build the project for the iOS device in Xcode. This can be accomplished from the command line by executing:

xcodebuild -project <project_dir_name>.xcodeproj -configuration Release

Where <project_dir_name> is the Xcode project path and filename.

If the Xcode project has not been built first, the following types of errors may appear during a scan:

01/11/14 07:33:03 - Scanning /Users/smith/MobileFirst_Apps/
  wl_newapps/BasicHybridApp/apps/HybridApp/iphone/native/
  Classes/CDVMainViewController.m (1 of 3)
01/11/14 07:33:05 - In file included from /Users/smith/MobileFirst_Apps/
  wl_newapps/BasicHybridApp/apps/HybridApp/iphone/native/Classes/
  CDVMainViewController.m:14:
In file included from /Users/smith/MobileFirst_Apps/wl_newapps/
  BasicHybridApp/apps/HybridApp/iphone/native/Classes/
  CDVMainViewController.h:15:
 /Users/smith/MobileFirst_Apps/wl_newapps/BasicHybridApp/apps/HybridApp/
  iphone/native/MobileFirstSDK/include/MainViewController.h:35:9: 
  fatal error: 'Cordova/CDVViewController.h' file not found
#import <Cordova/CDVViewController.h>

2/06/14 15:19:43 - Scanning /Users/smith/MobileFirst_Apps/
  xcodeapps/WLMarkupTest-1.0-iphone/Classes/
  CDVMainViewController.m (1 of 3)
02/06/14 15:19:45 - In file included from /Users/smith/MobileFirst_Apps/
  xcodeapps/WLMarkupTest-1.0-iphone/Classes/CDVMainViewController.m:14:
In file included from /Users/smith/MobileFirst_Apps/xcodeapps/
  WLMarkupTest-1.0-iphone/Classes/CDVMainViewController.h:15:
/Users/smith/MobileFirst_Apps/xcodeapps/WLMarkupTest-1.0-iphone/
  MobileFirstSDK/include/MainViewController.h:41:63: error: expected ':'
- (BOOL) execute:(CDVInvokedUrlCommand*)command CDV_DEPRECATED
  (2.2, "Use direct method calls instead, this is now a no-op");

Java

Tip: If you are scanning Java and there are missing dependencies in your Java project, AppScan Source will compile your Java files by synthesizing the pieces that the dependencies would have provided. In this case, you can improve the accuracy of findings by specifying missing dependencies, as follows:

After scanning, open <data_dir>\logs\scanner_exceptions.log (where <data_dir> is the location of your AppScan Source program data, as described in Installation and user data file locations) to see if AppScan Source has reported missing dependencies.
Modify the project properties to include the dependencies.
Re-scan the project.