blinkid android
v6.12.0
Android SDK yang berkedip memungkinkan Anda membangun pengalaman onboarding yang fantastis di aplikasi Android Anda.
Dengan satu pemindaian cepat, pengguna Anda akan dapat mengekstrak informasi dari kartu identitas, paspor, lisensi pengemudi, dan hampir semua ID yang dikeluarkan pemerintah lainnya.
Blinkid adalah:
Untuk melihat semua fitur ini di tempat kerja, unduh aplikasi demo gratis kami:
Merasa siap untuk melanjutkan dengan integrasi? Pertama -tama pastikan kami mendukung jenis dokumen Anda ➡️ Daftar lengkap. Dan kemudian ikuti pedoman di bawah ini.
UISettings )RecognizerRunnerFragment )RecognizerRunnerViewString (Parsing)BlinkIdUISettings dan BlinkIdOverlayControllerDocumentUISettingsLegacyDocumentVerificationUISettingsRecognizerRunner dan RecognizerRunnerViewRecognizerBundle RecognizerRecognizerRecognizerBundleRecognizer antar kegiatanlibc++_shared.soYes . RecognizerRunnerFragment dan pengontrol overlay kamera bawaan dalam aktivitas Anda Di build.gradle Anda, tambahkan repositori maven blinkid ke daftar repositori
repositories {
maven { url 'https://maven.microblink.com' }
}
Tambahkan blinkid sebagai ketergantungan dan pastikan transitive diatur ke true
dependencies {
implementation('com.microblink:blinkid:6.12.0@aar') {
transitive = true
}
}
Android Studio harus secara otomatis mengimpor Javadoc dari ketergantungan Maven. Jika itu tidak terjadi, Anda dapat melakukannya secara manual dengan mengikuti langkah -langkah ini:
External Libraries (biasanya ini adalah entri terakhir dalam tampilan proyek)blinkid-6.12.0 , klik kanan di atasnya dan pilih Library Properties...Library Properties akan muncul+ kedua di sudut kiri bawah jendela (yang berisi + dengan globe kecil)https://blinkid.github.io/blinkid-android/OK Kunci lisensi yang valid diperlukan untuk menginisialisasi pemindaian. Anda dapat meminta kunci lisensi uji coba gratis, setelah Anda mendaftar, di Microblink Developer Hub. Lisensi terikat pada nama paket aplikasi Anda, jadi pastikan Anda memasukkan nama paket yang benar saat ditanya.
Unduh file lisensi Anda dan masukkan ke dalam folder aset aplikasi Anda. Pastikan untuk mengatur kunci lisensi sebelum menggunakan kelas lain dari SDK, jika tidak, Anda akan mendapatkan pengecualian runtime.
Kami menyarankan Anda memperluas kelas aplikasi Android dan menetapkan lisensi di callback onCreate seperti ini:
public class MyApplication extends Application {
@ Override
public void onCreate () {
MicroblinkSDK . setLicenseFile ( "path/to/license/file/within/assets/dir" , this );
}
} public class MyApplication : Application () {
override fun onCreate () {
MicroblinkSDK .setLicenseFile( " path/to/license/file/within/assets/dir " , this )
}
} Dalam aktivitas utama Anda, tentukan dan buat objek ActivityResultLauncher dengan mengesampingkan metode onActivityResult . Baik OneSideDocumentScan dan TwoSideDocumentScan dapat digunakan secara dipertukarkan tanpa perbedaan dalam implementasi. Satu -satunya perbedaan fungsional adalah bahwa OneSideDocumentScan dapat memindai hanya satu sisi dokumen dan bahwa TwoSideDocumentScan dapat memindai lebih dari satu sisi dokumen.
ActivityResultLauncher < Void > resultLauncher = registerForActivityResult (
new TwoSideDocumentScan (),
twoSideScanResult -> {
ResultStatus resultScanStatus = twoSideScanResult . getResultStatus ();
if ( resultScanStatus == ResultStatus . FINISHED ) {
// code after a successful scan
// use result.getResult() for fetching results, for example:
String firstName = twoSideScanResult . getResult (). getFirstName (). value ();
} else if ( resultScanStatus == ResultStatus . CANCELLED ) {
// code after a cancelled scan
} else if ( resultScanStatus == ResultStatus . EXCEPTION ) {
// code after a failed scan
}
}
); private val resultLauncher =
registerForActivityResult( TwoSideDocumentScan ()) { twoSideScanResult : TwoSideScanResult ->
when (twoSideScanResult.resultStatus) {
ResultStatus . FINISHED -> {
// code after a successful scan
// use twoSideScanResult.result for fetching results, for example:
val firstName = twoSideScanResult.result?.firstName?.value()
}
ResultStatus . CANCELLED -> {
// code after a cancelled scan
}
ResultStatus . EXCEPTION -> {
// code after a failed scan
}
else -> {}
}
}@Composable
fun createLauncher (): ActivityResultLauncher < Void ?> {
return rememberLauncherForActivityResult( TwoSideDocumentScan ()) { twoSideScanResult : TwoSideScanResult ->
when (twoSideScanResult.resultStatus) {
ResultStatus . FINISHED -> {
// code after a successful scan
// use twoSideScanResult.result for fetching results, for example:
val firstName = twoSideScanResult.result?.firstName?.value()
}
ResultStatus . CANCELLED -> {
// code after a cancelled scan
}
ResultStatus . EXCEPTION -> {
// code after a failed scan
}
else -> {}
}
}
} Setelah pemindaian, result , yang merupakan instance objek OneSideScanResult atau TwoSideScanResult , akan diperbarui. Anda dapat mendefinisikan apa yang terjadi dengan data dalam override fungsi onActivityResult (kode Kotlin juga mengesampingkan fungsi ini tetapi implisit). Hasil dapat diakses dalam metode twoSideScanResult.getResult() ( twoSideScanResult.result di Kotlin).
Mulailah Proses Pemindaian Dengan Menelepon ActivityResultObject dan Memanggil ActivityResultLauncher.launch :
// method within MyActivity from previous step
public void startScanning () {
// Start scanning
resultLauncher . launch ( null );
} // method within MyActivity from previous step
public fun startScanning () {
// Start scanning
resultLauncher.launch()
} // within @Composable function or setContent block
val resultLauncher = createLauncher()
resultLauncher.launch() Hasilnya akan tersedia dalam panggilan balik, yang didefinisikan dalam ActivityResultObject yang didefinisikan pada langkah sebelumnya.
Blinkid membutuhkan Android API Level 21 atau yang lebih baru.
Resolusi pratinjau video kamera juga penting. Untuk melakukan pemindaian yang berhasil, resolusi pratinjau kamera harus setidaknya 720p. Perhatikan bahwa resolusi pratinjau kamera tidak sama dengan resolusi perekaman video.
Blinkid didistribusikan dengan biner Perpustakaan Asli ARMV7 dan ARMV7 .
Blinkid adalah perpustakaan asli, ditulis dalam C ++ dan tersedia untuk beberapa platform. Karena itu, Blinkid tidak dapat bekerja pada perangkat dengan arsitektur perangkat keras yang tidak jelas. Kami telah menyusun kode asli blinkid hanya untuk Android Abis yang paling populer.
Bahkan sebelum mengatur kunci lisensi, Anda harus memeriksa apakah blinkid didukung pada perangkat saat ini (lihat bagian berikutnya: Periksa Kompatibilitas ). Mencoba memanggil metode apa pun dari SDK yang bergantung pada kode asli, seperti pemeriksaan lisensi, pada perangkat dengan arsitektur CPU yang tidak didukung akan menghancurkan aplikasi Anda.
Jika Anda menggabungkan perpustakaan blinkid dengan perpustakaan lain yang berisi kode asli ke dalam aplikasi Anda, pastikan Anda mencocokkan arsitektur semua perpustakaan asli.
Untuk informasi lebih lanjut, lihat bagian Pertimbangan Arsitektur Prosesor.
Inilah cara Anda dapat memeriksa apakah blinkid didukung pada perangkat:
// check if BlinkID is supported on the device,
RecognizerCompatibilityStatus status = RecognizerCompatibility . getRecognizerCompatibilityStatus ( this );
if ( status == RecognizerCompatibilityStatus . RECOGNIZER_SUPPORTED ) {
Toast . makeText ( this , "BlinkID is supported!" , Toast . LENGTH_LONG ). show ();
} else if ( status == RecognizerCompatibilityStatus . NO_CAMERA ) {
Toast . makeText ( this , "BlinkID is supported only via Direct API!" , Toast . LENGTH_LONG ). show ();
} else if ( status == RecognizerCompatibilityStatus . PROCESSOR_ARCHITECTURE_NOT_SUPPORTED ) {
Toast . makeText ( this , "BlinkID is not supported on current processor architecture!" , Toast . LENGTH_LONG ). show ();
} else {
Toast . makeText ( this , "BlinkID is not supported! Reason: " + status . name (), Toast . LENGTH_LONG ). show ();
} // check if _BlinkID_ is supported on the device,
when ( val status = RecognizerCompatibility .getRecognizerCompatibilityStatus( this )) {
RecognizerCompatibilityStatus . RECOGNIZER_SUPPORTED -> {
Toast .makeText( this , " BlinkID is supported! " , Toast . LENGTH_LONG ).show()
}
RecognizerCompatibilityStatus . NO_CAMERA -> {
Toast .makeText( this , " BlinkID is supported only via Direct API! " , Toast . LENGTH_LONG ).show()
}
RecognizerCompatibilityStatus . PROCESSOR_ARCHITECTURE_NOT_SUPPORTED -> {
Toast .makeText( this , " BlinkID is not supported on current processor architecture! " , Toast . LENGTH_LONG ).show()
}
else -> {
Toast .makeText( this , " BlinkID is not supported! Reason: " + status.name, Toast . LENGTH_LONG ).show()
}
}Beberapa pengenal membutuhkan kamera dengan fokus otomatis. Jika Anda mencoba menggunakannya pada perangkat yang tidak mendukung fokus otomatis, Anda akan mendapatkan kesalahan. Untuk mencegahnya, Anda dapat memeriksa apakah pengenal memerlukan fokus otomatis dengan memanggil metode yang dibutuhkan.
Jika Anda sudah memiliki array pengenal, Anda dapat dengan mudah menyaring pengenal yang memerlukan fokus otomatis dari array menggunakan cuplikan kode berikut:
Recognizer [] recArray = ...;
if (! RecognizerCompatibility . cameraHasAutofocus ( CameraType . CAMERA_BACKFACE , this )) {
recArray = RecognizerUtils . filterOutRecognizersThatRequireAutofocus ( recArray );
} var recArray : Array < Recognizer > = .. .
if ( ! RecognizerCompatibility .cameraHasAutofocus( CameraType . CAMERA_BACKFACE , this )) {
recArray = RecognizerUtils .filterOutRecognizersThatRequireAutofocus(recArray)
}Anda dapat mengintegrasikan blinkid ke dalam aplikasi Anda dalam lima cara berbeda, tergantung pada kasus penggunaan dan kebutuhan kustomisasi Anda:
OneSideDocumentScan dan TwoSideDocumentScan dapatUISettings )-SDK menangani sebagian besar pekerjaan, Anda hanya perlu mendefinisikan pengenal, pengaturan, memulai aktivitas bawaan dan menangani hasil, opsi kustomisasi terbatasRecognizerRunnerFragment )-menggunakan kembali pemindaian UX dari aktivitas bawaan kami dalam aktivitas Anda sendiriRecognizerRunnerView ) - SDK Menangani Manajemen Kamera saat Anda harus menerapkan UX Pemindaian KustomRecognizerRunner ) - SKD hanya menangani pengenalan sementara Anda harus menyediakannya dengan gambar, baik dari kamera atau dari file OneSideDocumentScan dan TwoSideDocumentScan ) OneSideDocumentScan dan TwoSideDocumentScan dapat adalah kelas yang berisi semua definisi pengaturan yang diperlukan untuk dengan cepat memulai kegiatan pemindaian bawaan SDK. Ini memungkinkan pengguna untuk melewatkan semua langkah pengaturan seperti UISettings dan RecognizerBundle dan langsung ke pemindaian.
Seperti yang ditunjukkan dalam melakukan pemindaian pertama Anda hanya membutuhkan definisi pendengar hasil, untuk menentukan apa yang akan terjadi dengan hasil pemindaian, dan memanggil fungsi pemindaian yang sebenarnya.
UISettings ) UISettings adalah kelas yang berisi semua pengaturan yang diperlukan untuk kegiatan pemindaian bawaan SDK. Ini mengkonfigurasi perilaku aktivitas pemindaian, string, ikon, dan elemen UI lainnya. Anda harus menggunakan ActivityRunner untuk memulai aktivitas pemindaian yang dikonfigurasi oleh UISettings , ditunjukkan pada contoh di bawah ini.
Kami menyediakan beberapa kelas UISettings yang berspesialisasi untuk berbagai skenario pemindaian. Setiap objek UISettings memiliki properti yang dapat diubah melalui metode setter yang sesuai. Misalnya, Anda dapat menyesuaikan pengaturan kamera dengan metod setCameraSettings .
Semua kelas UISettings yang tersedia tercantum di sini.
Dalam aktivitas utama Anda, buat objek pengakuan yang akan melakukan pengenalan gambar, konfigurasinya dan masukkan ke dalam objek yang dikenali. Anda dapat melihat informasi lebih lanjut tentang pengenal yang tersedia dan RecognizerBundle di sini.
Misalnya, untuk memindai dokumen yang didukung, konfigurasikan pengenal Anda seperti ini:
public class MyActivity extends Activity {
private BlinkIdMultiSideRecognizer mRecognizer ;
private RecognizerBundle mRecognizerBundle ;
@ Override
protected void onCreate ( Bundle bundle ) {
super . onCreate ( bundle );
// setup views, as you would normally do in onCreate callback
// create BlinkIdMultiSideRecognizer
mRecognizer = new BlinkIdMultiSideRecognizer ();
// bundle recognizers into RecognizerBundle
mRecognizerBundle = new RecognizerBundle ( mRecognizer );
}
} public class MyActivity : Activity () {
private lateinit var mRecognizer : BlinkIdMultiSideRecognizer
private lateinit var mRecognizerBundle : RecognizerBundle
override fun onCreate ( bundle : Bundle ) {
// setup views, as you would normally do in onCreate callback
// create BlinkIdMultiSideRecognizer
mRecognizer = BlinkIdMultiSideRecognizer ()
// build recognizers into RecognizerBundle
mRecognizerBundle = RecognizerBundle (mRecognizer)
}
} Mulai Proses Pengakuan dengan Membuat BlinkIdUISettings dan Memanggil ActivityRunner.startActivityForResult :
// method within MyActivity from previous step
public void startScanning () {
// Settings for BlinkIdActivity
BlinkIdUISettings settings = new BlinkIdUISettings ( mRecognizerBundle );
// tweak settings as you wish
// Start activity
ActivityRunner . startActivityForResult ( this , MY_REQUEST_CODE , settings );
} // method within MyActivity from previous step
public fun startScanning () {
// Settings for BlinkIdActivity
val settings = BlinkIdUISettings (mRecognizerBundle)
// tweak settings as you wish
// Start activity
ActivityRunner .startActivityForResult( this , MY_REQUEST_CODE , settings)
} onActivityResult akan dipanggil dalam aktivitas Anda setelah pemindaian selesai, di sini Anda bisa mendapatkan hasil pemindaian.
@ Override
protected void onActivityResult ( int requestCode , int resultCode , Intent data ) {
super . onActivityResult ( requestCode , resultCode , data );
if ( requestCode == MY_REQUEST_CODE ) {
if ( resultCode == Activity . RESULT_OK && data != null ) {
// load the data into all recognizers bundled within your RecognizerBundle
mRecognizerBundle . loadFromIntent ( data );
// now every recognizer object that was bundled within RecognizerBundle
// has been updated with results obtained during scanning session
// you can get the result by invoking getResult on recognizer
BlinkIdMultiSideRecognizer . Result result = mRecognizer . getResult ();
if ( result . getResultState () == Recognizer . Result . State . Valid ) {
// result is valid, you can use it however you wish
}
}
}
} override protected fun onActivityResult ( requestCode : Int , resultCode : Int , data : Intent ) {
super .onActivityResult(requestCode, resultCode, data);
if (requestCode == MY_REQUEST_CODE ) {
if (resultCode == Activity . RESULT_OK && data != null ) {
// load the data into all recognizers bundled within your RecognizerBundle
mRecognizerBundle.loadFromIntent(data)
// now every recognizer object that was bundled within RecognizerBundle
// has been updated with results obtained during scanning session
// you can get the result by invoking getResult on recognizer
val result = mRecognizer.result
if (result.resultState == Recognizer . Result . State . Valid ) {
// result is valid, you can use it however you wish
}
}
}
} Untuk informasi lebih lanjut tentang pengenal yang tersedia dan RecognizerBundle , lihat pengakuan yang dikenali dan pengenal yang tersedia.
RecognizerRunnerFragment ) Jika Anda ingin menggunakan kembali aktivitas built-in kami di dalam aktivitas Anda sendiri, gunakan RecognizerRunnerFragment . Aktivitas yang akan menjadi tuan rumah RecognizerRunnerFragment yang harus diimplementasikan antarmuka ScanningOverlayBinder . Mencoba menambahkan RecognizerRunnerFragment ke aktivitas yang tidak mengimplementasikan antarmuka itu akan menghasilkan ClassCastException .
ScanningOverlayBinder bertanggung jawab untuk mengembalikan implementasi non-null dari ScanningOverlay - kelas yang akan mengelola UI di atas RecognizerRunnerFragment . Tidak disarankan untuk membuat implementasi ScanningOverlay Anda sendiri, menggunakan salah satu implementasi kami yang tercantum di sini sebagai gantinya.
Berikut adalah contoh minimum untuk aktivitas yang menjadi tuan rumah RecognizerRunnerFragment :
public class MyActivity extends AppCompatActivity implements RecognizerRunnerFragment . ScanningOverlayBinder {
private BlinkIdMultiSideRecognizer mRecognizer ;
private RecognizerBundle mRecognizerBundle ;
private BlinkIdOverlayController mScanOverlay ;
private RecognizerRunnerFragment mRecognizerRunnerFragment ;
@ Override
protected void onCreate ( Bundle savedInstanceState ) {
super . onCreate ();
setContentView ( R . layout . activity_my_activity );
mScanOverlay = createOverlay ();
if ( null == savedInstanceState ) {
// create fragment transaction to replace R.id.recognizer_runner_view_container with RecognizerRunnerFragment
mRecognizerRunnerFragment = new RecognizerRunnerFragment ();
FragmentTransaction fragmentTransaction = getSupportFragmentManager (). beginTransaction ();
fragmentTransaction . replace ( R . id . recognizer_runner_view_container , mRecognizerRunnerFragment );
fragmentTransaction . commit ();
} else {
// obtain reference to fragment restored by Android within super.onCreate() call
mRecognizerRunnerFragment = ( RecognizerRunnerFragment ) getSupportFragmentManager (). findFragmentById ( R . id . recognizer_runner_view_container );
}
}
@ Override
@ NonNull
public ScanningOverlay getScanningOverlay () {
return mScanOverlay ;
}
private BlinkIdOverlayController createOverlay () {
// create BlinkIdMultiSideRecognizer
mRecognizer = new BlinkIdMultiSideRecognizer ();
// bundle recognizers into RecognizerBundle
mRecognizerBundle = new RecognizerBundle ( mRecognizer );
BlinkIdUISettings settings = new BlinkIdUISettings ( mRecognizerBundle );
return settings . createOverlayController ( this , mScanResultListener );
}
private final ScanResultListener mScanResultListener = new ScanResultListener () {
@ Override
public void onScanningDone ( @ NonNull RecognitionSuccessType recognitionSuccessType ) {
// pause scanning to prevent new results while fragment is being removed
mRecognizerRunnerFragment . getRecognizerRunnerView (). pauseScanning ();
// now you can remove the RecognizerRunnerFragment with new fragment transaction
// and use result within mRecognizer safely without the need for making a copy of it
// if not paused, as soon as this method ends, RecognizerRunnerFragments continues
// scanning. Note that this can happen even if you created fragment transaction for
// removal of RecognizerRunnerFragment - in the time between end of this method
// and beginning of execution of the transaction. So to ensure result within mRecognizer
// does not get mutated, ensure calling pauseScanning() as shown above.
}
@ Override
public void onUnrecoverableError ( @ NonNull Throwable throwable ) {
}
};
} package com.microblink.blinkid
class MainActivity : AppCompatActivity (), RecognizerRunnerFragment.ScanningOverlayBinder {
private lateinit var mRecognizer : BlinkIdMultiSideRecognizer
private lateinit var mRecognizerRunnerFragment : RecognizerRunnerFragment
private lateinit var mRecognizerBundle : RecognizerBundle
private lateinit var mScanOverlay : BlinkIdOverlayController
override fun onCreate ( savedInstanceState : Bundle ? ) {
super .onCreate(savedInstanceState)
if ( ! ::mScanOverlay.isInitialized) {
mScanOverlay = createOverlayController()
}
setContent {
this . run {
// viewBinding has to be set to 'true' in buildFeatures block of the build.gradle file
AndroidViewBinding ( RecognizerRunnerLayoutBinding ::inflate) {
mRecognizerRunnerFragment =
fragmentContainerView.getFragment< RecognizerRunnerFragment >()
}
}
}
}
override fun getScanningOverlay (): ScanningOverlay {
return mScanOverlay
}
private fun createOverlay (): BlinkIdOverlayController {
// create BlinkIdMultiSideRecognizer
val mRecognizer = BlinkIdMultiSideRecognizer ()
// bundle recognizers into RecognizerBundle
mRecognizerBundle = RecognizerBundle (mRecognizer)
val settings = BlinkIdUISettings (mRecognizerBundle)
return settings.createOverlayController( this , mScanResultListener)
}
private val mScanResultListener : ScanResultListener = object : ScanResultListener {
override fun onScanningDone ( p0 : RecognitionSuccessType ) {
// pause scanning to prevent new results while fragment is being removed
mRecognizerRunnerFragment !! .recognizerRunnerView !! .pauseScanning()
// now you can remove the RecognizerRunnerFragment with new fragment transaction
// and use result within mRecognizer safely without the need for making a copy of it
// if not paused, as soon as this method ends, RecognizerRunnerFragments continues
// scanning. Note that this can happen even if you created fragment transaction for
// removal of RecognizerRunnerFragment - in the time between end of this method
// and beginning of execution of the transaction. So to ensure result within mRecognizer
// does not get mutated, ensure calling pauseScanning() as shown above.
}
override fun onUnrecoverableError ( p0 : Throwable ) {
}
}
} Silakan merujuk ke aplikasi sampel yang disediakan dengan SDK untuk contoh yang lebih rinci dan pastikan orientasi aktivitas host Anda diatur ke nosensor atau memiliki konfigurasi yang diaktifkan (yaitu tidak dihidupkan ulang ketika perubahan konfigurasi terjadi). Untuk informasi lebih lanjut, periksa bagian orientasi pemindaian.
RecognizerRunnerViewBagian ini membahas cara menyematkan pengakuan yang dikenali ke dalam aktivitas pemindaian Anda dan melakukan pemindaian.
RecognizerRunnerView adalah bidang anggota dalam aktivitas Anda. Ini diperlukan karena Anda perlu lulus semua acara siklus hidup kegiatan untuk RecognizerRunnerView .portrait atau landscape . Mengatur sensor sebagai orientasi aktivitas pemindaian akan memicu restart aktivitas penuh setiap kali orientasi perangkat berubah. Ini akan memberikan pengalaman pengguna yang sangat buruk karena baik kamera dan perpustakaan asli yang blinkid harus dimulai ulang setiap saat. Ada langkah -langkah terhadap perilaku ini yang dibahas nanti.onCreate aktivitas Anda, buat RecognizerRunnerView baru yang baru, atur pengakuan yang mengandung pengakuan yang akan digunakan oleh tampilan, mendefinisikan CameraVentSlistener yang akan menangani acara kamera wajib, mendefinisikan ScanResultListener yang akan menerima panggilan ketika pengakuan telah selesai dan kemudian memanggil metode create -nya. Setelah itu, tambahkan tampilan Anda yang harus ditata di atas tampilan kamera.setLifecycle untuk mengaktifkan penanganan otomatis acara LifeCeycle. Berikut adalah contoh minimum dari integrasi RecognizerRunnerView sebagai satu -satunya tampilan dalam aktivitas Anda:
public class MyScanActivity extends AppCompatActivity {
private static final int PERMISSION_CAMERA_REQUEST_CODE = 42 ;
private RecognizerRunnerView mRecognizerRunnerView ;
private BlinkIdMultiSideRecognizer mRecognizer ;
private RecognizerBundle mRecognizerBundle ;
@ Override
protected void onCreate ( Bundle savedInstanceState ) {
super . onCreate ( savedInstanceState );
// create BlinkIdMultiSideRecognizer
mRecognizer = new BlinkIdMultiSideRecognizer ();
// bundle recognizers into RecognizerBundle
mRecognizerBundle = new RecognizerBundle ( mRecognizer );
// create RecognizerRunnerView
mRecognizerRunnerView = new RecognizerRunnerView ( this );
// set lifecycle to automatically call recognizer runner view lifecycle methods
mRecognizerRunnerView . setLifecycle ( getLifecycle ());
// associate RecognizerBundle with RecognizerRunnerView
mRecognizerRunnerView . setRecognizerBundle ( mRecognizerBundle );
// scan result listener will be notified when scanning is complete
mRecognizerRunnerView . setScanResultListener ( mScanResultListener );
// camera events listener will be notified about camera lifecycle and errors
mRecognizerRunnerView . setCameraEventsListener ( mCameraEventsListener );
setContentView ( mRecognizerRunnerView );
}
@ Override
public void onConfigurationChanged ( Configuration newConfig ) {
super . onConfigurationChanged ( newConfig );
// changeConfiguration is not handled by lifecycle events so call it manually
mRecognizerRunnerView . changeConfiguration ( newConfig );
}
private final CameraEventsListener mCameraEventsListener = new CameraEventsListener () {
@ Override
public void onCameraPreviewStarted () {
// this method is from CameraEventsListener and will be called when camera preview starts
}
@ Override
public void onCameraPreviewStopped () {
// this method is from CameraEventsListener and will be called when camera preview stops
}
@ Override
public void onError ( Throwable exc ) {
/**
* This method is from CameraEventsListener and will be called when
* opening of camera resulted in exception or recognition process
* encountered an error. The error details will be given in exc
* parameter.
*/
}
@ Override
@ TargetApi ( 23 )
public void onCameraPermissionDenied () {
/**
* Called in Android 6.0 and newer if camera permission is not given
* by user. You should request permission from user to access camera.
*/
requestPermissions ( new String []{ Manifest . permission . CAMERA }, PERMISSION_CAMERA_REQUEST_CODE );
/**
* Please note that user might have not given permission to use
* camera. In that case, you have to explain to user that without
* camera permissions scanning will not work.
* For more information about requesting permissions at runtime, check
* this article:
* https://developer.android.com/training/permissions/requesting.html
*/
}
@ Override
public void onAutofocusFailed () {
/**
* This method is from CameraEventsListener will be called when camera focusing has failed.
* Camera manager usually tries different focusing strategies and this method is called when all
* those strategies fail to indicate that either object on which camera is being focused is too
* close or ambient light conditions are poor.
*/
}
@ Override
public void onAutofocusStarted ( Rect [] areas ) {
/**
* This method is from CameraEventsListener and will be called when camera focusing has started.
* You can utilize this method to draw focusing animation on UI.
* Areas parameter is array of rectangles where focus is being measured.
* It can be null on devices that do not support fine-grained camera control.
*/
}
@ Override
public void onAutofocusStopped ( Rect [] areas ) {
/**
* This method is from CameraEventsListener and will be called when camera focusing has stopped.
* You can utilize this method to remove focusing animation on UI.
* Areas parameter is array of rectangles where focus is being measured.
* It can be null on devices that do not support fine-grained camera control.
*/
}
};
private final ScanResultListener mScanResultListener = new ScanResultListener () {
@ Override
public void onScanningDone ( @ NonNull RecognitionSuccessType recognitionSuccessType ) {
// this method is from ScanResultListener and will be called when scanning completes
// you can obtain scanning result by calling getResult on each
// recognizer that you bundled into RecognizerBundle.
// for example:
BlinkIdMultiSideRecognizer . Result result = mRecognizer . getResult ();
if ( result . getResultState () == Recognizer . Result . State . Valid ) {
// result is valid, you can use it however you wish
}
// Note that mRecognizer is stateful object and that as soon as
// scanning either resumes or its state is reset
// the result object within mRecognizer will be changed. If you
// need to create a immutable copy of the result, you can do that
// by calling clone() on it, for example:
BlinkIdMultiSideRecognizer . Result immutableCopy = result . clone ();
// After this method ends, scanning will be resumed and recognition
// state will be retained. If you want to prevent that, then
// you should call:
mRecognizerRunnerView . resetRecognitionState ();
// Note that reseting recognition state will clear internal result
// objects of all recognizers that are bundled in RecognizerBundle
// associated with RecognizerRunnerView.
// If you want to pause scanning to prevent receiving recognition
// results or mutating result, you should call:
mRecognizerRunnerView . pauseScanning ();
// if scanning is paused at the end of this method, it is guaranteed
// that result within mRecognizer will not be mutated, therefore you
// can avoid creating a copy as described above
// After scanning is paused, you will have to resume it with:
mRecognizerRunnerView . resumeScanning ( true );
// boolean in resumeScanning method indicates whether recognition
// state should be automatically reset when resuming scanning - this
// includes clearing result of mRecognizer
}
};
} Jika properti screenOrientation aktivitas di AndroidManifest.xml diatur ke sensor , fullSensor atau yang serupa, aktivitas akan dimulai kembali setiap kali perangkat mengubah orientasi dari potret ke lanskap dan sebaliknya. Saat memulai kembali aktivitas, metode onPause , onStop dan onDestroy akan dipanggil dan kemudian aktivitas baru akan dibuat lagi. Ini adalah masalah potensial untuk aktivitas pemindaian karena dalam siklus hidupnya mengendalikan kamera dan perpustakaan asli - memulai kembali aktivitas tersebut akan memicu restart kamera dan perpustakaan asli. Ini adalah masalah karena mengubah orientasi dari lanskap ke potret dan sebaliknya akan sangat lambat, sehingga merendahkan pengalaman pengguna. Kami tidak merekomendasikan pengaturan tersebut.
Dalam hal ini, kami sarankan mengatur aktivitas pemindaian Anda ke mode portrait atau landscape dan menangani perubahan orientasi perangkat secara manual. Untuk membantu Anda dalam hal ini, RecognizerRunnerView mendukung mendukung penambahan tampilan anak yang akan diputar terlepas dari screenOrientation aktivitas. Anda menambahkan tampilan yang ingin Anda rotasi (seperti tampilan yang berisi tombol, pesan status, dll.) Untuk RecognizerRunnerView Metode AddChildView. Parameter kedua dari metode ini adalah boolean yang menentukan apakah tampilan yang Anda tambahkan akan diputar dengan perangkat. Untuk mendefinisikan orientasi yang diizinkan, mengimplementasikan antarmuka orientationAllowedListener dan menambahkannya ke RecognizerRunnerView dengan metode setOrientationAllowedListener . Ini adalah cara yang disarankan untuk memutar overlay kamera.
Namun, jika Anda benar -benar ingin mengatur properti screenOrientation ke sensor atau yang serupa dan ingin Android menangani perubahan orientasi dari aktivitas pemindaian Anda, maka kami sarankan untuk mengatur properti configChanges dari aktivitas Anda ke orientation|screenSize . Ini akan memberi tahu Android untuk tidak memulai kembali aktivitas Anda saat orientasi perangkat berubah. Sebagai gantinya, metode onConfigurationChanged Activity akan dipanggil sehingga aktivitas dapat diberitahu tentang perubahan konfigurasi. Dalam implementasi metode ini, Anda harus menghubungi metode changeConfiguration dari RecognizerView sehingga dapat mengadaptasi permukaan dan tampilan anak -anaknya dengan konfigurasi baru.
Bagian ini akan menjelaskan cara menggunakan API langsung untuk mengenali bitmap android tanpa perlu kamera. Anda dapat menggunakan API langsung di mana saja dari aplikasi Anda, bukan hanya dari aktivitas.
Kinerja pengenalan gambar sangat tergantung pada kualitas gambar input. Ketika manajemen kamera kami digunakan (memindai dari kamera), kami melakukan yang terbaik untuk mendapatkan bingkai kamera dengan kualitas terbaik untuk perangkat yang digunakan. Di sisi lain, ketika API langsung digunakan, Anda perlu memberikan gambar berkualitas tinggi tanpa blur dan silau untuk pengakuan yang berhasil.
Bitmaps Android yang diperoleh, misalnya, dari galeri. Gunakan pengakuan atau pengakuan atau pengakuan dengan pengakuan.Images video yang dibangun dari bingkai video kamera khusus, misalnya, ketika Anda menggunakan manajemen kamera pihak ketiga atau ketiga. Pengakuan akan dioptimalkan untuk kecepatan dan akan bergantung pada redundansi waktu antara bingkai video berturut-turut untuk menghasilkan hasil pengakuan sebaik mungkin. Gunakan pengenalan atau pengenalan atau pengenalanvideoMagWithRecognizer.Images diam saat Anda membutuhkan pemindaian menyeluruh dari satu atau sedikit gambar yang bukan bagian dari aliran video dan Anda ingin mendapatkan hasil terbaik dari InputImage tunggal. Jenis inputimage berasal dari SDK kami atau dapat dibuat dengan menggunakan ImageBuilder. Gunakan pengenalan atau pengakuan atau pengakuan.Berikut adalah contoh minimum penggunaan API langsung untuk mengenali Android Bitmap:
public class DirectAPIActivity extends Activity {
private RecognizerRunner mRecognizerRunner ;
private BlinkIdMultiSideRecognizer mRecognizer ;
private RecognizerBundle mRecognizerBundle ;
@ Override
protected void onCreate ( Bundle savedInstanceState ) {
super . onCreate ();
// initialize your activity here
// create BlinkIdMultiSideRecognizer
mRecognizer = new BlinkIdMultiSideRecognizer ();
// bundle recognizers into RecognizerBundle
mRecognizerBundle = new RecognizerBundle ( mRecognizer );
try {
mRecognizerRunner = RecognizerRunner . getSingletonInstance ();
} catch ( FeatureNotSupportedException e ) {
Toast . makeText ( this , "Feature not supported! Reason: " + e . getReason (). getDescription (), Toast . LENGTH_LONG ). show ();
finish ();
return ;
}
mRecognizerRunner . initialize ( this , mRecognizerBundle , new DirectApiErrorListener () {
@ Override
public void onRecognizerError ( Throwable t ) {
Toast . makeText ( DirectAPIActivity . this , "There was an error in initialization of Recognizer: " + t . getMessage (), Toast . LENGTH_SHORT ). show ();
finish ();
}
});
}
@ Override
protected void onResume () {
super . onResume ();
// start recognition
Bitmap bitmap = BitmapFactory . decodeFile ( "/path/to/some/file.jpg" );
mRecognizerRunner . recognizeBitmap ( bitmap , Orientation . ORIENTATION_LANDSCAPE_RIGHT , mScanResultListener );
}
@ Override
protected void onDestroy () {
super . onDestroy ();
mRecognizerRunner . terminate ();
}
private final ScanResultListener mScanResultListener = new ScanResultListener () {
@ Override
public void onScanningDone ( @ NonNull RecognitionSuccessType recognitionSuccessType ) {
// this method is from ScanResultListener and will be called
// when scanning completes
// you can obtain scanning result by calling getResult on each
// recognizer that you bundled into RecognizerBundle.
// for example:
BlinkIdMultiSideRecognizer . Result result = mRecognizer . getResult ();
if ( result . getResultState () == Recognizer . Result . State . Valid ) {
// result is valid, you can use it however you wish
}
}
};
} Metode ScanResultListener.onscanningDone dipanggil untuk setiap gambar input yang Anda kirim ke pengakuan. onScanningDone dapat menghubungi Metode Call RecognizerRunner.recognize* . Ini berguna saat Anda menggunakan manajemen kamera pihak ketiga atau ketiga.
String (Parsing) Beberapa pengenal mendukung pengakuan dari String . Mereka dapat digunakan melalui API langsung untuk menguraikan String yang diberikan dan mengembalikan data seperti ketika mereka digunakan pada gambar input. Ketika pengakuan dilakukan pada String , tidak perlu untuk OCR. String input digunakan dengan cara yang sama seperti output OCR digunakan saat gambar dikenali.
Pengakuan dari String dapat dilakukan dengan cara yang sama seperti pengakuan dari gambar, yang dijelaskan di bagian sebelumnya.
Satu -satunya perbedaan adalah bahwa salah satu metode pengenalan singleton untuk pengakuan dari string harus disebut:
RecognizerRunner API Direct Singleton adalah mesin negara bagian yang dapat berada di salah satu dari 3 negara bagian: OFFLINE , READY dan WORKING .
RecognizerRunner , itu akan berada dalam keadaan OFFLINE .RecognizerRunner dengan memanggil metode inisialisasi. Jika Anda memanggil metode initialize saat RecognizerRunner , tidak dalam keadaan OFFLINE , Anda akan mendapatkan IllegalStateException .RecognizerRunner akan pindah ke negara READY . Sekarang Anda dapat menghubungi salah satu metode recognize* .recognize* , RecognizerRunner akan pindah ke status WORKING . Jika Anda mencoba untuk memanggil metode ini saat RecognizerRunner tidak dalam keadaan READY , Anda akan mendapatkan IllegalStateExceptionRecognizerRunner's dari utas UIRecognizerRunner pertama kali bergerak kembali ke keadaan READY dan kemudian memanggil metode OnScanningDone dari ScanResultListener yang disediakan.onScanningDone dari ScanResultListener akan dipanggil pada utas pemrosesan latar belakang, jadi pastikan Anda tidak melakukan operasi UI dalam panggilan balik ini. Perhatikan juga bahwa sampai metode onScanningDone selesai, RecognizerRunner tidak akan melakukan pengakuan gambar atau string lain, bahkan jika salah satu metode recognize* telah dipanggil setelah transisi ke status READY . Ini untuk memastikan bahwa hasil pengenal yang dibundel dalam RecognizerBundle yang terkait dengan RecognizerRunner tidak dimodifikasi sementara mungkin digunakan dalam metode onScanningDone .terminate , RecognizerRunner Singleton akan merilis semua sumber daya internalnya. Perhatikan bahwa bahkan setelah menelepon terminate Anda mungkin menerima acara onScanningDone jika ada pekerjaan yang sedang berlangsung ketika terminate dipanggil.terminate dapat dipanggil dari keadaan RecognizerRunner singleton mana punRecognizerRunner singleton dengan metode getCurrentState Baik pengakuan yang dikenali dan RecognizerRunner menggunakan singleton internal yang sama yang mengelola kode asli. Singleton ini menangani inisialisasi dan penghentian perpustakaan asli dan menyebarkan pengakuan ke perpustakaan asli. Dimungkinkan untuk menggunakan RecognizerRunnerView dan RecognizerRunner bersama -sama, karena Singleton internal akan memastikan sinkronisasi yang benar dan pengaturan pengakuan yang benar digunakan. Jika Anda mengalami masalah saat menggunakan RecognizerRunner dalam kombinasi dengan RecognizerRunnerView , beri tahu kami!
Saat Anda menggunakan pengukur gabungan dan gambar dari kedua sisi dokumen diperlukan, Anda perlu menelepon RecognizerRunner.recognize* beberapa kali. Sebut saja dengan gambar sisi pertama dokumen, sampai dibaca, dan kemudian dengan gambar sisi kedua. Pengenalan gabungan secara otomatis beralih ke pemindaian sisi kedua, setelah berhasil membaca sisi pertama. Untuk diberi tahu ketika pemindaian sisi pertama selesai, Anda harus mengatur FirstSiderCognitionCallback melalui metadatacallbacks. Jika Anda tidak memerlukan informasi itu, misalnya ketika Anda hanya memiliki satu gambar untuk setiap sisi dokumen, jangan atur FirstSideRecognitionCallback dan periksa pengakuan yang bersikap di ScanResultListener.onscanningDone, setelah gambar sisi kedua telah diproses.
BlinkIdUISettings dan BlinkIdOverlayController BlinkIdOverlayController mengimplementasikan UI baru untuk memindai dokumen identitas, yang secara optimal dirancang untuk digunakan dengan BlinkIdMultiSideRecognizer baru dan BlinkIdSingleSideRecognizer . Ini mengimplementasikan beberapa fitur baru:
UI baru memungkinkan pengguna untuk memindai dokumen pada sudut apa pun, dalam orientasi apa pun. Kami merekomendasikan memaksa orientasi lanskap jika Anda memindai barcode di sisi belakang, karena dalam tingkat keberhasilan orientasi akan lebih tinggi.
Untuk meluncurkan aktivitas bawaan yang menggunakan BlinkIdOverlayController menggunakan BlinkIdUISettings .
Untuk menyesuaikan overlay, berikan sumber daya gaya khusus Anda melalui metode BlinkIdUISettings.setOverlayViewStyle() atau melalui konstruktor ReticleOverlayView . Anda dapat menyesuaikan elemen yang diberi label pada tangkapan layar di atas dengan memberikan atribut berikut dalam gaya Anda:
KELUAR
mb_exitScanDrawable - ikon drawableBlinkIdUISettings.setShowCancelButton(false)obor
mb_torchOnDrawable - ikon yang dapat ditarik yang ditunjukkan saat obor diaktifkanmb_torchOffDrawable - Ikon Drawable yang ditampilkan saat obor dinonaktifkanBlinkIdUISettings.setShowTorchButton(false)instruksi
mb_instructionsTextAppearance - gaya yang akan digunakan sebagai android:textAppearancemb_instructionsBackgroundDrawable - Drawable digunakan untuk latar belakangmb_instructionsBackgroundColor - warna yang digunakan untuk latar belakangPeringatan Senter
mb_flashlightWarningTextAppearance - gaya yang akan digunakan sebagai android:textAppearancemb_flashlightWarningBackgroundDrawable - drawable digunakan untuk latar belakangBlinkIdUISettings.setShowFlashlightWarning(false)Ikon Kartu
mb_cardFrontDrawable - ikon yang dapat ditarik ditampilkan selama animasi flip kartu, mewakili sisi depan kartumb_cardBackDrawable - ikon yang dapat ditarik ditampilkan selama animasi flip kartu, mewakili sisi belakang kartureticle
mb_reticleDefaultDrawable - dapat ditunjukkan saat reticle dalam keadaan netralmb_reticleSuccessDrawable - dapat ditunjukkan ketika reticle dalam keadaan sukses (pemindaian berhasil)mb_reticleErrorDrawable - dapat ditarik ditunjukkan saat reticle dalam keadaan kesalahanmb_reticleColor - Warna yang digunakan untuk elemen reticle berputarmb_reticleDefaultColor - Warna yang digunakan untuk reticle dalam keadaan netralmb_reticleErrorColor - Warna yang digunakan untuk reticle dalam keadaan kesalahanmb_successFlashColor - warna yang digunakan untuk efek flash pada pemindaian yang berhasil Untuk menyesuaikan visibilitas dan gaya dua dialog ini, gunakan metode yang disediakan dalam BlinkIdUISettings .
Metode untuk mengendalikan visibilitas dialog Pendahuluan adalah BlinkIdUISettings.setShowIntroductionDialog(boolean showIntroductionDialog) dan diatur ke true secara default, yang berarti dialog pengantar akan ditampilkan.
Metode untuk mengendalikan visibilitas dialog onboarding adalah BlinkIdUISettings.setShowOnboardingInfo(boolean showOnboardingInfo) dan diatur ke true secara default, yang berarti dialog pengantar akan ditampilkan.
Ada juga metode untuk mengendalikan keterlambatan "Show Help?" Tooltip yang ditampilkan di atas tombol Bantuan. Tombol itu sendiri akan ditampilkan jika metode sebelumnya untuk menampilkan onboarding adalah benar. Metode untuk mengatur panjang penundaan tooltip adalah BlinkIdUISettings.setShowTooltipTimeIntervalMs(long showTooltipTimeIntervalMs) . Parameter waktu diatur dalam milidetik.
Pengaturan default penundaan adalah 12 detik (12000 milidetik).
Menyesuaikan dan tema elemen pengantar dan orientasi ini dapat dilakukan dengan cara yang sama seperti yang dijelaskan dalam bab sebelumnya, dengan memberikan atribut berikut:
Tombol Bantuan
mb_helpButtonDrawable - drawable yang ditampilkan saat tombol bantuan diaktifkanmb_helpButtonBackgroundColor - warna digunakan untuk latar belakang tombol bantuanmb_helpButtonQuestionmarkColor - warna yang digunakan untuk tombol bantuan latar depanmembantu tooltip
mb_helpTooltipBackground - drawable yang ditampilkan sebagai latar belakang saat membantu tooltip munculmb_helpTooltipColor - warna digunakan untuk latar belakang alat bantu bantuanmb_helpTooltipTextAppearance - Gaya yang akan digunakan sebagai android:textAppearanceDialog Pendahuluan
mb_introductionBackgroundColor - warna yang digunakan untuk latar belakang layar pengantarmb_introductionTitleTextAppearance - gaya yang akan digunakan sebagai android:textAppearancemb_introductionMessageTextAppearance - Gaya yang akan digunakan sebagai android:textAppearancemb_introductionButtonTextAppearance android:textAppearanceBlinkIdUISettings.setShowIntroductionDialog(false)Dialog onboarding
mb_onboardingBackgroundColor - warna yang digunakan untuk latar belakang layar onboardingmb_onboardingPageIndicatorColor - warna yang digunakan untuk indikator halaman melingkar di layar onboardingmb_onboardingTitleTextAppearance - gaya yang akan digunakan sebagai android:textAppearancemb_onboardingMessageTextAppearance - gaya yang akan digunakan sebagai android:textAppearancemb_onboardingButtonTextAppearance - gaya yang akan digunakan sebagai android:textAppearanceBlinkIdUISettings.setShowOnboardingInfo(false) Dialog peringatan yang dipanggil oleh SDK memiliki set properti sendiri yang dapat dimodifikasi dalam styles.xml .
MB_alert_dialog adalah tema yang memperluas tema Theme.AppCompat.Light.Dialog.Alert dan menggunakan warna default tema aplikasi. Untuk mengubah atribut dalam dialog peringatan ini tanpa mengubah atribut lain dalam aplikasi pengguna, tema MB_alert_dialog perlu ditimpa.
< style name = " MB_alert_dialog " parent = " Theme.AppCompat.Light.Dialog.Alert " >
< item name = " android:textSize " >TEXT_SIZE</ item >
< item name = " android:background " >COLOR</ item >
< item name = " android:textColorPrimary " >COLOR</ item >
< item name = " colorAccent " >COLOR</ item >
</ style >Atribut yang tidak ditimpa akan menggunakan warna dan ukuran default tema aplikasi.
Aturan colorAccent digunakan untuk mengubah warna tombol dialog peringatan. Jika atribut colorAccent tema aplikasi diubah di tempat lain, warna tombol dialog peringatan ini juga akan diubah. Namun, tema tema MB_alert_dialog yang menimpa dan atribut ini di dalamnya akan memastikan bahwa hanya warna tombol dalam dialog peringatan Microblink SDK yang diubah. Jika tema aplikasi memperluas tema dari set MaterialComponents (misalnya Theme.MaterialComponents.Light.NoActionBar ), warna tombol yang disebutkan di atas hanya dapat diubah dengan menimpa atribut colorOnPrimary alih -alih atribut colorAccent .
DocumentUISettings DocumentUISettings meluncurkan aktivitas yang menggunakan BlinkIdOverlayController dengan UI alternatif. Ini paling cocok untuk memindai sisi dokumen tunggal dari berbagai dokumen kartu dan tidak boleh digunakan dengan pengenal gabungan karena tidak memberikan instruksi pengguna kapan harus beralih ke sisi belakang.
LegacyDocumentVerificationUISettings LegacyDocumentVerificationUISettings meluncurkan aktivitas yang menggunakan BlinkIdOverlayController dengan UI alternatif. Ini paling cocok untuk pengenal gabungan karena mengelola pemindaian beberapa sisi dokumen dalam pembukaan kamera tunggal dan memandu pengguna melalui proses pemindaian. Ini juga dapat digunakan untuk pemindaian satu sisi kartu ID, paspor, lisensi pengemudi, dll.
String yang digunakan dalam kegiatan bawaan dan overlay dapat dilokalisasi ke bahasa apa pun. Jika Anda menggunakan RecognizerRunnerView (lihat bab ini untuk informasi lebih lanjut) dalam aktivitas atau fragmen pemindaian khusus Anda, Anda harus menangani lokalisasi seperti pada aplikasi Android lainnya. RecognizerRunnerView tidak menggunakan string atau drawable, ia hanya menggunakan aset dari folder assets/microblink . Aset -aset itu tidak boleh disentuh karena diperlukan untuk pengakuan untuk bekerja dengan benar.
Namun, jika Anda menggunakan aktivitas atau overlay bawaan kami, mereka akan menggunakan sumber daya yang dikemas dalam LibBlinkID.aar untuk menampilkan string dan gambar di atas tampilan kamera. Kami telah menyiapkan string untuk beberapa bahasa yang dapat Anda gunakan di luar kotak. Anda juga dapat memodifikasi string itu, atau Anda dapat menambahkan bahasa Anda sendiri.
Untuk menggunakan bahasa, Anda harus mengaktifkannya dari kode:
Untuk menggunakan bahasa tertentu, pada startup aplikasi, sebelum membuka komponen UI apa pun dari SDK, Anda harus memanggil Metode LanguageUtils.setLanguageAndCountry(language, country, context) . Misalnya, Anda dapat mengatur bahasa ke Kroasia seperti ini:
// define BlinkID language
LanguageUtils . setLanguageAndCountry ( "hr" , "" , this ); Blinkid dapat dengan mudah diterjemahkan ke bahasa lain. Folder res di LibBlinkID.aar arsip memiliki values folder yang berisi strings.xml - file ini berisi string bahasa Inggris. In order to make eg croatian translation, create a folder values-hr in your project and put the copy of strings.xml inside it (you might need to extract LibBlinkID.aar archive to access those files). Then, open that file and translate the strings from English into Croatian.
To modify an existing string, the best approach would be to:
strings.xml in folder res/values-hr of the LibBlinkID.aar archive<string name="MBBack">Back</string>strings.xml in the folder res/values-hr , if it doesn't already exist<string name="MBBack">Natrag</string>RecognizerRunner and RecognizerRunnerViewProcessing events, also known as Metadata callbacks are purely intended for giving processing feedback on UI or to capture some debug information during development of your app using BlinkID SDK. For that reason, built-in activities and fragments handle those events internally. If you need to handle those events yourself, you need to use either RecognizerRunnerView or RecognizerRunner.
Callbacks for all events are bundled into the MetadataCallbacks object. Both RecognizerRunner and RecognizerRunnerView have methods which allow you to set all your callbacks.
We suggest that you check for more information about available callbacks and events to which you can handle in the javadoc for MetadataCallbacks class.
Please note that both those methods need to pass information about available callbacks to the native code and for efficiency reasons this is done at the time setMetadataCallbacks method is called and not every time when change occurs within the MetadataCallbacks object. This means that if you, for example, set QuadDetectionCallback to MetadataCallbacks after you already called setMetadataCallbacks method, the QuadDetectionCallback will not be registered with the native code and you will not receive its events.
Similarly, if you, for example, remove the QuadDetectionCallback from MetadataCallbacks object after you already called setMetadataCallbacks method, your app will crash with NullPointerException when our processing code attempts to invoke the method on removed callback (which is now set to null ). We deliberately do not perform null check here because of two reasons:
null callback, while still being registered to native code is illegal state of your program and it should therefore crash Remember , each time you make some changes to MetadataCallbacks object, you need to apply those changes to to your RecognizerRunner or RecognizerRunnerView by calling its setMetadataCallbacks method.
Recognizer concept and RecognizerBundle This section will first describe what is a Recognizer and how it should be used to perform recognition of the images, videos and camera stream. Next, we will describe how RecognizerBundle can be used to tweak the recognition procedure and to transfer Recognizer objects between activities.
RecognizerBundle is an object which wraps the Recognizers and defines settings about how recognition should be performed. Besides that, RecognizerBundle makes it possible to transfer Recognizer objects between different activities, which is required when using built-in activities to perform scanning, as described in first scan section, but is also handy when you need to pass Recognizer objects between your activities.
List of all available Recognizer objects, with a brief description of each Recognizer , its purpose and recommendations how it should be used to get best performance and user experience, can be found here .
Recognizer concept The Recognizer is the basic unit of processing within the BlinkID SDK. Its main purpose is to process the image and extract meaningful information from it. As you will see later, the BlinkID SDK has lots of different Recognizer objects that have various purposes.
Each Recognizer has a Result object, which contains the data that was extracted from the image. The Result object is a member of corresponding Recognizer object and its lifetime is bound to the lifetime of its parent Recognizer object. If you need your Result object to outlive its parent Recognizer object, you must make a copy of it by calling its method clone() .
Every Recognizer is a stateful object, that can be in two states: idle state and working state . While in idle state , you can tweak Recognizer object's properties via its getters and setters. After you bundle it into a RecognizerBundle and use either RecognizerRunner or RecognizerRunnerView to run the processing with all Recognizer objects bundled within RecognizerBundle , it will change to working state where the Recognizer object is being used for processing. While being in working state , you cannot tweak Recognizer object's properties. If you need to, you have to create a copy of the Recognizer object by calling its clone() , then tweak that copy, bundle it into a new RecognizerBundle and use reconfigureRecognizers to ensure new bundle gets used on processing thread.
While Recognizer object works, it changes its internal state and its result. The Recognizer object's Result always starts in Empty state. When corresponding Recognizer object performs the recognition of given image, its Result can either stay in Empty state (in case Recognizer failed to perform recognition), move to Uncertain state (in case Recognizer performed the recognition, but not all mandatory information was extracted), move to StageValid state (in case Recognizer successfully scanned one part/side of the document and there are more fields to extract) or move to Valid state (in case Recognizer performed recognition and all mandatory information was successfully extracted from the image).
As soon as one Recognizer object's Result within RecognizerBundle given to RecognizerRunner or RecognizerRunnerView changes to Valid state, the onScanningDone callback will be invoked on same thread that performs the background processing and you will have the opportunity to inspect each of your Recognizer objects' Results to see which one has moved to Valid state.
As already stated in section about RecognizerRunnerView , as soon as onScanningDone method ends, the RecognizerRunnerView will continue processing new camera frames with same Recognizer objects, unless paused. Continuation of processing or resetting recognition will modify or reset all Recognizer objects's Results . When using built-in activities, as soon as onScanningDone is invoked, built-in activity pauses the RecognizerRunnerView and starts finishing the activity, while saving the RecognizerBundle with active Recognizer objects into Intent so they can be transferred back to the calling activities.
RecognizerBundle The RecognizerBundle is wrapper around Recognizers objects that can be used to transfer Recognizer objects between activities and to give Recognizer objects to RecognizerRunner or RecognizerRunnerView for processing.
The RecognizerBundle is always constructed with array of Recognizer objects that need to be prepared for recognition (ie their properties must be tweaked already). The varargs constructor makes it easier to pass Recognizer objects to it, without the need of creating a temporary array.
The RecognizerBundle manages a chain of Recognizer objects within the recognition process. When a new image arrives, it is processed by the first Recognizer in chain, then by the second and so on, iterating until a Recognizer object's Result changes its state to Valid or all of the Recognizer objects in chain were invoked (none getting a Valid result state). If you want to invoke all Recognizers in the chain, regardless of whether some Recognizer object's Result in chain has changed its state to Valid or not, you can allow returning of multiple results on a single image.
You cannot change the order of the Recognizer objects within the chain - no matter the order in which you give Recognizer objects to RecognizerBundle , they are internally ordered in a way that provides best possible performance and accuracy. Also, in order for BlinkID SDK to be able to order Recognizer objects in recognition chain in the best way possible, it is not allowed to have multiple instances of Recognizer objects of the same type within the chain. Attempting to do so will crash your application.
Recognizer objects between activities Besides managing the chain of Recognizer objects, RecognizerBundle also manages transferring bundled Recognizer objects between different activities within your app. Although each Recognizer object, and each its Result object implements Parcelable interface, it is not so straightforward to put those objects into Intent and pass them around between your activities and services for two main reasons:
Result object is tied to its Recognizer object, which manages lifetime of the native Result object.Result object often contains large data blocks, such as images, which cannot be transferred via Intent because of Android's Intent transaction data limit. Although the first problem can be easily worked around by making a copy of the Result and transfer it independently, the second problem is much tougher to cope with. This is where, RecognizerBundle's methods saveToIntent and loadFromIntent come to help, as they ensure the safe passing of Recognizer objects bundled within RecognizerBundle between activities according to policy defined with method setIntentDataTransferMode :
STANDARD , the Recognizer objects will be passed via Intent using normal Intent transaction mechanism , which is limited by Android's Intent transaction data limit. This is same as manually putting Recognizer objects into Intent and is OK as long as you do not use Recognizer objects that produce images or other large objects in their Results .OPTIMISED , the Recognizer objects will be passed via internal singleton object and no serialization will take place. This means that there is no limit to the size of data that is being passed. This is also the fastest transfer method, but it has a serious drawback - if Android kills your app to save memory for other apps and then later restarts it and redelivers Intent that should contain Recognizer objects, the internal singleton that should contain saved Recognizer objects will be empty and data that was being sent will be lost. You can easily provoke that condition by choosing No background processes under Limit background processes in your device's Developer options , and then switch from your app to another app and then back to your app.PERSISTED_OPTIMISED , the Recognizer objects will be passed via internal singleton object (just like in OPTIMISED mode) and will additionaly be serialized into a file in your application's private folder. In case Android restarts your app and internal singleton is empty after re-delivery of the Intent , the data will be loaded from file and nothing will be lost. The files will be automatically cleaned up when data reading takes place. Just like OPTIMISED , this mode does not have limit to the size of data that is being passed and does not have a drawback that OPTIMISED mode has, but some users might be concerned about files to which data is being written.onSaveInstanceState and save bundle back to file by calling its saveState method. Also, after saving state, you should ensure that you clear saved state in your onResume , as onCreate may not be called if activity is not restarted, while onSaveInstanceState may be called as soon as your activity goes to background (before onStop ), even though activity may not be killed at later time.OPTIMISED mode to transfer large data and image between activities or create your own mechanism for data transfer. Note that your application's private folder is only accessible by your application and your application alone, unless the end-user's device is rooted. This section will give a list of all Recognizer objects that are available within BlinkID SDK, their purpose and recommendations how they should be used to get best performance and user experience.
The FrameGrabberRecognizer is the simplest recognizer in BlinkID SDK, as it does not perform any processing on the given image, instead it just returns that image back to its FrameCallback . Its Result never changes state from Empty.
This recognizer is best for easy capturing of camera frames with RecognizerRunnerView . Note that Image sent to onFrameAvailable are temporary and their internal buffers all valid only until the onFrameAvailable method is executing - as soon as method ends, all internal buffers of Image object are disposed. If you need to store Image object for later use, you must create a copy of it by calling clone .
Also note that FrameCallback interface extends Parcelable interface, which means that when implementing FrameCallback interface, you must also implement Parcelable interface.
This is especially important if you plan to transfer FrameGrabberRecognizer between activities - in that case, keep in mind that the instance of your object may not be the same as the instance on which onFrameAvailable method gets called - the instance that receives onFrameAvailable calls is the one that is created within activity that is performing the scan.
The SuccessFrameGrabberRecognizer is a special Recognizer that wraps some other Recognizer and impersonates it while processing the image. However, when the Recognizer being impersonated changes its Result into Valid state, the SuccessFrameGrabberRecognizer captures the image and saves it into its own Result object.
Since SuccessFrameGrabberRecognizer impersonates its slave Recognizer object, it is not possible to give both concrete Recognizer object and SuccessFrameGrabberRecognizer that wraps it to same RecognizerBundle - doing so will have the same result as if you have given two instances of same Recognizer type to the RecognizerBundle - it will crash your application.
This recognizer is best for use cases when you need to capture the exact image that was being processed by some other Recognizer object at the time its Result became Valid . When that happens, SuccessFrameGrabber's Result will also become Valid and will contain described image. That image can then be retrieved with getSuccessFrame() method.
Unless stated otherwise for concrete recognizer, single side BlinkID recognizers from this list can be used in any context, but they work best with BlinkIdUISettings and DocumentScanUISettings , with UIs best suited for document scanning.
Combined recognizers should be used with BlinkIdUISettings . They manage scanning of multiple document sides in the single camera opening and guide the user through the scanning process. Some combined recognizers support scanning of multiple document types, but only one document type can be scanned at a time.
The BlinkIdSingleSideRecognizer scans and extracts data from the single side of the supported document. You can find the list of the currently supported documents here. We will continue expanding this recognizer by adding support for new document types in the future. Star this repo to stay updated.
The BlinkIdSingleSideRecognizer works best with the BlinkIdUISettings and BlinkIdOverlayController .
Use BlinkIdMultiSideRecognizer for scanning both sides of the supported document. First, it scans and extracts data from the front, then scans and extracts data from the back, and finally, combines results from both sides. The BlinkIdMultiSideRecognizer also performs data matching and returns a flag if the extracted data captured from the front side matches the data from the back. You can find the list of the currently supported documents here. We will continue expanding this recognizer by adding support for new document types in the future. Star this repo to stay updated.
The BlinkIdMultiSideRecognizer works best with the BlinkIdUISettings and BlinkIdOverlayController .
The MrtdRecognizer is used for scanning and data extraction from the Machine Readable Zone (MRZ) of the various Machine Readable Travel Documents (MRTDs) like ID cards and passports. This recognizer is not bound to the specific country, but it can be configured to only return data that match some criteria defined by the MrzFilter .
You can find information about usage context at the beginning of this section.
The MrtdCombinedRecognizer scans Machine Readable Zone (MRZ) after scanning the full document image and face image (usually MRZ is on the back side and face image is on the front side of the document). Internally, it uses DocumentFaceRecognizer for obtaining full document image and face image as the first step and then MrtdRecognizer for scanning the MRZ.
You can find information about usage context at the beginning of this section.
The PassportRecognizer is used for scanning and data extraction from the Machine Readable Zone (MRZ) of the various passport documents. This recognizer also returns face image from the passport.
You can find information about usage context at the beginning of this section.
The VisaRecognizer is used for scanning and data extraction from the Machine Readable Zone (MRZ) of the various visa documents. This recognizer also returns face image from the visa document.
You can find information about usage context at the beginning of this section.
The IdBarcodeRecognizer is used for scanning barcodes from various ID cards. Check this document to see the list of supported document types.
You can find information about usage context at the beginning of this section.
The DocumentFaceRecognizer is a special type of recognizer that only returns face image and full document image of the scanned document. It does not extract document fields like first name, last name, etc. This generic recognizer can be used to obtain document images in cases when specific support for some document type is not available.
You can find information about usage context at the beginning of this section.
You need to ensure that the final app gets all resources required by BlinkID . At the time of writing this documentation, Android does not have support for combining multiple AAR libraries into single fat AAR. The problem is that resource merging is done while building application, not while building AAR, so application must be aware of all its dependencies. There is no official Android way of "hiding" third party AAR within your AAR.
This problem is usually solved with transitive Maven dependencies, ie when publishing your AAR to Maven you specify dependencies of your AAR so they are automatically referenced by app using your AAR. Besides this, there are also several other approaches you can try:
RecognizerRunnerView ). You can perform custom UI integration while taking care that all resources (strings, layouts, images, ...) used are solely from your AAR, not from BlinkID . Then, in your AAR you should not reference LibBlinkID.aar as gradle dependency, instead you should unzip it and copy its assets to your AAR's assets folder, its classes.jar to your AAR's lib folder (which should be referenced by gradle as jar dependency) and contents of its jni folder to your AAR's src/main/jniLibs folder.BlinkID is distributed with ARMv7 and ARM64 native library binaries.
ARMv7 architecture gives the ability to take advantage of hardware accelerated floating point operations and SIMD processing with NEON. This gives BlinkID a huge performance boost on devices that have ARMv7 processors. Most new devices (all since 2012.) have ARMv7 processor so it makes little sense not to take advantage of performance boosts that those processors can give. Also note that some devices with ARMv7 processors do not support NEON and VFPv4 instruction sets, most popular being those based on NVIDIA Tegra 2, ARM Cortex A9 and older. Since these devices are old by today's standard, BlinkID does not support them. For the same reason, BlinkID does not support devices with ARMv5 ( armeabi ) architecture.
ARM64 is the new processor architecture that most new devices use. ARM64 processors are very powerful and also have the possibility to take advantage of new NEON64 SIMD instruction set to quickly process multiple pixels with a single instruction.
There are some issues to be considered:
LibBlinkID.aar archive contains ARMv7 and ARM64 builds of the native library. By default, when you integrate BlinkID into your app, your app will contain native builds for all these processor architectures. Thus, BlinkID will work on ARMv7 and ARM64 devices and will use ARMv7 features on ARMv7 devices and ARM64 features on ARM64 devices. However, the size of your application will be rather large.
We recommend that you distribute your app using App Bundle. This will defer apk generation to Google Play, allowing it to generate minimal APK for each specific device that downloads your app, including only required processor architecture support.
If you are unable to use App Bundle, you can create multiple flavors of your app - one flavor for each architecture. With gradle and Android studio this is very easy - just add the following code to build.gradle file of your app:
android {
...
splits {
abi {
enable true
reset()
include 'armeabi-v7a', 'arm64-v8a'
universalApk true
}
}
}
With that build instructions, gradle will build two different APK files for your app. Each APK will contain only native library for one processor architecture and one APK will contain all architectures. In order for Google Play to accept multiple APKs of the same app, you need to ensure that each APK has different version code. This can easily be done by defining a version code prefix that is dependent on architecture and adding real version code number to it in following gradle script:
// map for the version code
def abiVersionCodes = ['armeabi-v7a':1, 'arm64-v8a':2]
import com.android.build.OutputFile
android.applicationVariants.all { variant ->
// assign different version code for each output
variant.outputs.each { output ->
def filter = output.getFilter(OutputFile.ABI)
if(filter != null) {
output.versionCodeOverride = abiVersionCodes.get(output.getFilter(OutputFile.ABI)) * 1000000 + android.defaultConfig.versionCode
}
}
}
For more information about creating APK splits with gradle, check this article from Google.
After generating multiple APK's, you need to upload them to Google Play. For tutorial and rules about uploading multiple APK's to Google Play, please read the official Google article about multiple APKs.
If you won't be distributing your app via Google Play or for some other reasons want to have single APK of smaller size, you can completely remove support for certain CPU architecture from your APK. This is not recommended due to consequences .
To keep only some CPU architectures, for example armeabi-v7a and arm64-v8a , add the following statement to your android block inside build.gradle :
android {
...
ndk {
// Tells Gradle to package the following ABIs into your application
abiFilters 'armeabi-v7a', 'arm64-v8a'
}
}
This will remove other architecture builds for all native libraries used by the application.
To remove support for a certain CPU architecture only for BlinkID , add the following statement to your android block inside build.gradle :
android {
...
packagingOptions {
exclude 'lib/<ABI>/libBlinkID.so'
}
}
where <ABI> represents the CPU architecture you want to remove:
exclude 'lib/armeabi-v7a/libBlinkID.so'exclude 'lib/arm64-v8a/libBlinkID.so' You can also remove multiple processor architectures by specifying exclude directive multiple times. Just bear in mind that removing processor architecture will have side effects on performance and stability of your app. Please read this for more information.
Google decided that as of August 2019 all apps on Google Play that contain native code need to have native support for 64-bit processors (this includes ARM64 and x86_64). This means that you cannot upload application to Google Play Console that supports only 32-bit ABI and does not support corresponding 64-bit ABI.
By removing ARMv7 support, BlinkID will not work on devices that have ARMv7 processors.
By removing ARM64 support, BlinkID will not use ARM64 features on ARM64 device
If you are combining BlinkID library with other libraries that contain native code into your application, make sure you match the architectures of all native libraries. For example, if third party library has got only ARMv7 version, you must use exactly ARMv7 version of BlinkID with that library, but not ARM64. Using this architectures will crash your app at initialization step because JVM will try to load all its native dependencies in same preferred architecture and will fail with UnsatisfiedLinkError .
libc++_shared.so BlinkID contains native code that depends on the C++ runtime. This runtime is provided by the libc++_shared.so , which needs to be available in your app that is using BlinkID . However, the same file is also used by various other libraries that contain native components. If you happen to integrate both such library together with BlinkID in your app, your build will fail with an error similar to this one:
* What went wrong:
Execution failed for task ':app:mergeDebugNativeLibs'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeJavaResWorkAction
> 2 files found with path 'lib/arm64-v8a/libc++_shared.so' from inputs:
- <path>/.gradle/caches/transforms-3/3d428f9141586beb8805ce57f97bedda/transformed/jetified-opencv-4.5.3.0/jni/arm64-v8a/libc++_shared.so
- <path>/.gradle/caches/transforms-3/609476a082a81bd7af00fd16a991ee43/transformed/jetified-blinkid-6.12.0/jni/arm64-v8a/libc++_shared.so
If you are using jniLibs and CMake IMPORTED targets, see
https://developer.android.com/r/tools/jniLibs-vs-imported-targets
The error states that multiple different dependencies provide the same file lib/arm64/libc++_shared.so (in this case, OpenCV and BlinkID).
You can resolve this issue by making sure that the dependency that uses newer version of libc++_shared.so is listed first in your dependency list, and then, simply add the following to your build.gradle :
android {
packaging {
jniLibs {
pickFirsts.add("lib/armeabi-v7a/libc++_shared.so")
pickFirsts.add("lib/arm64-v8a/libc++_shared.so")
}
}
}
Catatan penting
The code above will always select the first libc++_shared.so from your dependency list, so make sure that the dependency that uses the latest version of libc++_shared.so is listed first. This is because libc++_shared.so is backward-compatible, but not forward-compatible. This means that, eg libBlinkID.so built against libc++_shared.so from NDK r24 will work without problems when you package it together with libc++_shared.so from NDK r26, but will crash when you package it together with libc++_shared.so from NDK r21. This is true for all your native dependencies.
In case of problems with SDK integration, first make sure that you have followed integration instructions. If you're still having problems, please contact us at help.microblink.com.
If you are getting "invalid license key" error or having other license-related problems (eg some feature is not enabled that should be or there is a watermark on top of camera), first check the ADB logcat. All license-related problems are logged to error log so it is easy to determine what went wrong.
When you have to determine what is the license-relate problem or you simply do not understand the log, you should contact us help.microblink.com. When contacting us, please make sure you provide following information:
AndroidManifest.xml and/or your build.gradle file)Keep in mind: Versions 5.8.0 and above require an internet connection to work under our new License Management Program.
We're only asking you to do this so we can validate your trial license key. Data extraction still happens offline, on the device itself. Once the validation is complete, you can continue using the SDK in offline mode (or over a private network) until the next check.
If you are having problems with scanning certain items, undesired behaviour on specific device(s), crashes inside BlinkID or anything unmentioned, please do as follows:
enable logging to get the ability to see what is library doing. To enable logging, put this line in your application:
com . microblink . blinkid . util . Log . setLogLevel ( com . microblink . blinkid . util . Log . LogLevel . LOG_VERBOSE );After this line, library will display as much information about its work as possible. Please save the entire log of scanning session to a file that you will send to us. It is important to send the entire log, not just the part where crash occurred, because crashes are sometimes caused by unexpected behaviour in the early stage of the library initialization.
Contact us at help.microblink.com describing your problem and provide following information:
InvalidLicenseKeyException when I construct specific Recognizer object Each license key contains information about which features are allowed to use and which are not. This exception indicates that your production license does not allow using of specific Recognizer object. You should contact support to check if provided license is OK and that it really contains all features that you have purchased.
InvalidLicenseKeyException with trial license key Whenever you construct any Recognizer object or any other object that derives from Entity , a check whether license allows using that object will be performed. If license is not set prior constructing that object, you will get InvalidLicenseKeyException . We recommend setting license as early as possible in your app, ideally in onCreate callback of your Application singleton.
ClassNotFoundExceptionThis usually happens when you perform integration into Eclipse project and you forget to add resources or native libraries into the project. You must alway take care that same versions of both resources, assets, java library and native libraries are used in combination. Combining different versions of resources, assets, java and native libraries will trigger crash in SDK. This problem can also occur when you have performed improper integration of BlinkID SDK into your SDK. Please read how to embed BlinkID inside another SDK.
UnsatisfiedLinkError This error happens when JVM fails to load some native method from native library If performing integration into Android studio and this error happens, make sure that you have correctly combined BlinkID SDK with third party SDKs that contain native code, especially if you need resolving conflict over libc++_shared.so . If this error also happens in our integration sample apps, then it may indicate a bug in the SDK that is manifested on specific device. Please report that to our support team.
libc++_shared.so Please consult the section about resolving libc++_shared.so conflict.
MetadataCallbacks object, but it is not being called Make sure that after adding your callback to MetadataCallbacks you have applied changes to RecognizerRunnerView or RecognizerRunner as described in this section.
MetadataCallbacks object, and now app is crashing with NullPointerException Make sure that after removing your callback from MetadataCallbacks you have applied changes to RecognizerRunnerView or RecognizerRunner as described in this section.
onScanningDone callback I have the result inside my Recognizer , but when scanning activity finishes, the result is gone This usually happens when using RecognizerRunnerView and forgetting to pause the RecognizerRunnerView in your onScanningDone callback. Then, as soon as onScanningDone happens, the result is mutated or reset by additional processing that Recognizer performs in the time between end of your onScanningDone callback and actual finishing of the scanning activity. For more information about statefulness of the Recognizer objects, check this section.
IllegalStateException stating Data cannot be saved to intent because its size exceeds intent limit . This usually happens when you use Recognizer that produces image or similar large object inside its Result and that object exceeds the Android intent transaction limit. You should enable different intent data transfer mode. For more information about this, check this section. Also, instead of using built-in activity, you can use RecognizerRunnerFragment with built-in scanning overlay.
This usually happens when you attempt to transfer standalone Result that contains images or similar large objects via Intent and the size of the object exceeds Android intent transaction limit. Depending on the device, you will get either TransactionTooLargeException, a simple message BINDER TRANSACTION FAILED in log and your app will freeze or your app will get into restart loop. We recommend that you use RecognizerBundle and its API for sending Recognizer objects via Intent in a more safe manner (check this section for more information). However, if you really need to transfer standalone Result object (eg Result object obtained by cloning Result object owned by specific Recognizer object), you need to do that using global variables or singletons within your application. Sending large objects via Intent is not supported by Android.
Direct API When automatic scanning of camera frames with our camera management is used (provided camera overlays or direct usage of RecognizerRunnerView ), we use a stream of video frames and send multiple images to the recognition to boost reading accuracy. Also, we perform frame quality analysis and combine scanning results from multiple camera frames. On the other hand, when you are using the Direct API with a single image per document side, we cannot combine multiple images. We do our best to extract as much information as possible from that image. In some cases, when the quality of the input image is not good enough, for example, when the image is blurred or when glare is present, we are not able to successfully read the document.
Online trial licenses require a public network access for validation purposes. See Licensing issues.
onOcrResult() method in my OcrCallback is never invoked and all Result objects always return null in their OCR result gettersIn order to be able to obtain raw OCR result, which contains locations of each character, its value and its alternatives, you need to have a license that allows that. By default, licenses do not allow exposing raw OCR results in public API. If you really need that, please contact us and explain your use case.
You can find BlinkID SDK size report for all supported ABIs here.
Complete API reference can be found in Javadoc.
For any other questions, feel free to contact us at help.microblink.com.
