Android™

SFTP Debug Log File Path

See more SFTP Examples

Demonstrates how to use the DebugLogFilePath property to get information if a Chilkat method crashes or hangs. Android™

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    boolean success = false;

    CkSFtp sftp = new CkSFtp();

    // Insert this code just before the method call that crashes or hangs.
    sftp.put_VerboseLogging(true);
    sftp.put_DebugLogFilePath("/some/file/path/sftp_debug_log.txt");

    // Make the call that crashes or hangs,
    // for example, if the method is DownloadFileByName:

    String remoteFilePath = "...";
    String localFilePath = "...";
    success = sftp.DownloadFileByName(remoteFilePath,localFilePath);

    // Note: If the method returns control to your application code, then it did not crash within Chilkat.
    // The DebugLogFilePath property causes all information that would be recorded in the LastErrorText to be emitted to the
    // log file (with immediate file write flushing, i.e. no buffering).  Thus, in a crash situation,
    // the log file will contain information up to the point of the crash.

    if (success == false) {
        Log.i(TAG, sftp.lastErrorText());
        return;
        }


  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}