Problemi noti
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Problemi con Android
- Per l'ID lingua in bundle, l'app potrebbe arrestarsi in modo anomalo durante l'upgrade ad AGP 7.0.0 o versioni successive.
Per evitare l'arresto anomalo in
com.google.mlkit:language-id:16.1.1 o versioni precedenti, includi la regola riportata di seguito:
-keep class com.google.mlkit.nl.languageid.internal.LanguageIdentificationJni { *; }
Per evitare l'arresto anomalo in com.google.mlkit:language-id:17.0.0 o com.google.mlkit:language-id:17.0.1, includi la regola riportata di seguito:
-keep class com.google.mlkit.nl.languageid.internal.ThickLanguageIdentifier { *; }
- InputImage costruito da Bitmap con un valore non nullo per rotationDegrees causa un'eccezione MlKit "rotazione non valida" per l'API FaceDetection a partire da
com.google.mlkit:face-detection:16.0.5
e com.google.android.gms:play-services-mlkit-barcode-scanning:16.1.4. Utilizza una versione precedente e attendi la nostra prossima release che include la correzione del problema.
Gli SDK di scansione codici a barre precedenti a com.google.mlkit:barcode-scanning:16.1.0
e com.google.android.gms:play-services-mlkit-barcode-scanning:16.1.3
non funzionano su alcuni dispositivi con la versione camera-camera2:1.0.0-beta08 o successive.
Per aggirare il problema, puoi utilizzare una versione precedente di camera-camera2. Ad esempio:
implementation "androidx.camera:camera-core:1.0.0-beta07"
implementation "androidx.camera:camera-camera2:1.0.0-beta07"
implementation "androidx.camera:camera-view:1.0.0-alpha14"
implementation "androidx.camera:camera-extensions:1.0.0-alpha14"
implementation "androidx.camera:camera-lifecycle:1.0.0-beta07"
I metodi nativi potrebbero essere offuscati da regole personalizzate in com.google.mlkit:language-id:16.1.1 o versioni precedenti.
Includi la seguente regola per mantenerli se riscontri errori come java.lang.UnsatisfiedLinkError:
-keepclasseswithmembernames class com.google.mlkit.nl.languageid.internal.LanguageIdentificationJni {
native <methods>;
}Per le API di riconoscimento del testo, etichettatura delle immagini, rilevamento e monitoraggio degli oggetti, il rendimento con CameraX e Camera2 non è ancora alla pari con Camera1, perché richiede più tempo per eseguire la conversione del formato per le immagini da CameraX e Camera2.
I rilanci di Task
potrebbero essere eseguiti dopo che l'attività o il frammento in cui sono stati registrati è stato distrutto. Ciò potrebbe comportare un'eccezione se il callback
prova ad accedere a un rilevatore che nel frattempo è stato chiuso. Se utilizzi ML Kit in un'attività, puoi registrare un ascoltatore basato sull'attività, che viene rimosso automaticamente quando l'attività viene interrotta. Se utilizzi ML Kit in un frammento o in un altro ambiente, puoi fornire un executor personalizzato che arresti l'esecuzione quando il frammento viene distrutto. Per un esempio, consulta ScopedExecutor.Java nella guida rapida di Vision.
Per l'etichettatura delle immagini con formati diversi da Bitmap, la variante in bundle ha un rendimento migliore rispetto alla variante "snella" che dipende da Google Play Services.
Per Digital Ink com.google.mlkit:digital-ink-recognition:17.0.0 o versioni precedenti
e Estrazione entità com.google.mlkit:entity-extraction:16.0.0-beta2 o versioni precedenti,
verrà visualizzata la seguente eccezione di runtime se imposti targetSdkVersion su 31
e esegui su Android S.
Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
AndroidRuntime: Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.
Questo problema è stato risolto nelle release più recenti.
Se preferisci utilizzare versioni precedenti, puoi impostare targetSdkVersion su un valore inferiore a 31 o aggiungere quanto segue a build.gradle come soluzione alternativa.
// For apps targeting Android S+, add the following
constraints {
implementation 'androidx.work:work-runtime:2.7.0-alpha04'
}
Problemi relativi a iOS
- I simulatori su Mac basati su M1 non sono supportati.
- Il simulatore X86_64 non è supportato per Traduzione
'GoogleMLKit/Translate', '4.0.0' o versioni successive e Risposta rapida 'GoogleMLKit/Translate', '4.0.0' o versioni successive.'GoogleMLKit/SmartReply', '4.0.0'
Salvo quando diversamente specificato, i contenuti di questa pagina sono concessi in base alla licenza Creative Commons Attribution 4.0, mentre gli esempi di codice sono concessi in base alla licenza Apache 2.0. Per ulteriori dettagli, consulta le norme del sito di Google Developers. Java è un marchio registrato di Oracle e/o delle sue consociate.
Ultimo aggiornamento 2025-08-29 UTC.
[null,null,["Ultimo aggiornamento 2025-08-29 UTC."],[[["\u003cp\u003eUpgrading to AGP 7.0.0+ with bundled Language ID may cause crashes, requiring specific keep rules to be added for different versions.\u003c/p\u003e\n"],["\u003cp\u003eInputImage created with Bitmap and rotationDegrees may cause errors with FaceDetection API in specific versions; use earlier versions or await a fix.\u003c/p\u003e\n"],["\u003cp\u003eBarcodeScanning SDKs before 16.1.0/16.1.3 have compatibility issues with camera-camera2:1.0.0-beta08+, consider using earlier camera-camera2 versions.\u003c/p\u003e\n"],["\u003cp\u003eTask callbacks may execute after Activity/Fragment destruction, potentially causing exceptions; use Activity-scoped listeners or custom executors for mitigation.\u003c/p\u003e\n"],["\u003cp\u003eOn Android S with targetSdkVersion 31, Digital Ink and Entity Extraction SDKs before specific versions may cause runtime exceptions regarding PendingIntent flags; upgrade to newer SDKs or apply a workaround.\u003c/p\u003e\n"]]],["Key actions and information regarding Android issues include: adding specific `-keep` rules to avoid crashes when using Language ID with AGP 7.0.0 or later; using earlier versions of Face Detection and Barcode Scanning due to \"invalid rotation\" and camera compatibility issues; adding a rule to fix `UnsatisfiedLinkError` with Language ID. Performance with CameraX/Camera2 is not optimized for Text Recognition, Image Labeling, and Object Detection. Activity-scoped listeners can be registered to prevent exceptions with Task callbacks. Setting `targetSdkVersion` or adding constraints to address Digital Ink and Entity Extraction issues.\n"],null,["Android issues\n\n- For bundled Language ID, the app may crash when upgrading to AGP 7.0.0 or later. To avoid the crash in `com.google.mlkit:language-id:16.1.1` or earlier, include the rule below: \n\n ```scdoc\n -keep class com.google.mlkit.nl.languageid.internal.LanguageIdentificationJni { *; }\n ```\n To avoid the crash in `com.google.mlkit:language-id:17.0.0` or `com.google.mlkit:language-id:17.0.1`, include the rule below: \n\n ```scdoc\n -keep class com.google.mlkit.nl.languageid.internal.ThickLanguageIdentifier { *; }\n ```\n- InputImage constructed by Bitmap with a non zero rotationDegrees causes an \"invalid rotation\" MlKitException for FaceDetection API since `com.google.mlkit:face-detection:16.0.5` and `com.google.android.gms:play-services-mlkit-barcode-scanning:16.1.4`. Please use an earlier version and wait for our next release which includes the fix for this issue.\n- BarcodeScanning SDKs pior to `com.google.mlkit:barcode-scanning:16.1.0`\n and `com.google.android.gms:play-services-mlkit-barcode-scanning:16.1.3`\n do not work on some devices running with camera-camera2:1.0.0-beta08 version or later.\n You can use an earlier version of camera-camera2 to bypass this issue. For example:\n\n ```carbon\n implementation \"androidx.camera:camera-core:1.0.0-beta07\"\n implementation \"androidx.camera:camera-camera2:1.0.0-beta07\"\n implementation \"androidx.camera:camera-view:1.0.0-alpha14\"\n implementation \"androidx.camera:camera-extensions:1.0.0-alpha14\"\n implementation \"androidx.camera:camera-lifecycle:1.0.0-beta07\"\n ```\n\n \u003cbr /\u003e\n\n- Native methods might be obfuscated by custom rules in `com.google.mlkit:language-id:16.1.1` or earlier.\n Include the following rule to keep them if you encounter errors like `java.lang.UnsatisfiedLinkError`:\n\n ```text\n -keepclasseswithmembernames class com.google.mlkit.nl.languageid.internal.LanguageIdentificationJni {\n native \u003cmethods\u003e;\n }\n ```\n\n \u003cbr /\u003e\n\n- For the Text Recognition, Image Labeling, and Object Detection and\n Tracking APIs, the performance with CameraX and Camera2 is still not on par\n with Camera1, because it takes more time to do format conversion for image\n from CameraX and Camera2.\n\n- [Task](https://developers.google.com/android/guides/tasks)\n callbacks might execute after the Activity or Fragment in which they have been\n registered has been destroyed. This might lead to an exception if the callback\n tries to access a detector that has been closed in the meantime. If you are\n using ML Kit in an Activity, you can register an\n [Activity-scoped listener](https://developers.google.com/android/guides/tasks#activity-scoped_listeners),\n which is automatically removed when the Activity is stopped. If you are\n using ML Kit in a Fragment or other environment, you can provide a custom\n executor that shuts down execution when the Fragment is destroyed. See\n `ScopedExecutor.Java` in the [Vision Quickstart](https://github.com/googlesamples/mlkit/tree/master/android/vision-quickstart) for an\n example.\n\n- For Image Labeling with image formats other than Bitmap, bundled variant\n has better performance than \"thin\" variant that depends on Google Play Services.\n\n- For Digital Ink `com.google.mlkit:digital-ink-recognition:17.0.0` or earlier\n and Entity Extraction `com.google.mlkit:entity-extraction:16.0.0-beta2` or earlier,\n you will get the following runtime exception if you set `targetSdkVersion` to 31\n and run on Android S.\n\n Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.\n AndroidRuntime: Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.\n\n This issue is fixed in our more recent releases.\n\n \u003cbr /\u003e\n\n If you prefer using older versions, you can either set `targetSdkVersion` to\n less than 31 or add the following to your `build.gradle` as a workaround. \n\n ```carbon\n // For apps targeting Android S+, add the following\n constraints {\n implementation 'androidx.work:work-runtime:2.7.0-alpha04'\n }\n ```\n\n \u003cbr /\u003e\n\niOS issues\n\n- Simulators on M1-based Mac are not supported.\n- X86_64 simulator is not supported for Translation `'GoogleMLKit/Translate', '4.0.0'` or later and Smart Reply `'GoogleMLKit/SmartReply', '4.0.0'` or later."]]
