Kotlin did not recognize a java nullable return, hence my AnkiDAO assumed the result of the function to always be non null, which caused a null exception if the note in Anki had been removed. Second bug for anki failures (issue #65).

Author: licryle

crossPlatform/src/androidMain/kotlin/fr/berliat/hskwidget/data/dao/AnkiDAO.android.kt

@@ -106,7 +106,10 @@ actual class AnkiDAO(context: Context) {
     }
 
     actual suspend fun getNote(noteId: Long): AnkiNoteInfo? =
-        withContext(Dispatchers.IO) { AnkiNoteInfo(api.getNote(noteId)) }
+        withContext(Dispatchers.IO) {
+            // Even if Kotlin recognize as NoteInfo!, it's not correct, should be NoteInfo?
+            api.getNote(noteId)?.let { AnkiNoteInfo(it) }
+        }
     actual suspend fun addNote(modelId: Long, deckId: Long, fields: Array<String>, tags: Set<String>?): Long?
             = withContext(Dispatchers.IO) { api.addNote(modelId, deckId, fields, tags) }
     actual suspend fun updateNoteTags(noteId: Long, tags: Set<String>): Boolean