Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Support Native Media Gallery Indexing / scanFile API on Android (Serious Python)

オープン
  • 何か問題がありますか？
#226 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
android, dart, flutter
領域
mobile

調査の方向性

まず Flutter クライアントの Dart 側ハンドラーと、提案されている MethodChannel のエントリーポイントを追跡し、次に Serious Python が Python にサービスを公開する方法を調べます。クロスプラットフォームのメディアスキャン API が公開され、PyJNIus のワークアラウンドを必要とせずに Android ファイルがネイティブの MediaStore から認識できるようになれば完了です。

索引モデルが issue の本文から書いたものです。

説明

Context

When building multi-platform Python applications with Flet and compiling them for Android using Serious Python, apps often need to download or save media files (videos, photos, audio) to public user directories (such as the standard Download/ folder).

The Problem

When a file is downloaded or created directly on the filesystem under public storage (e.g., /storage/emulated/0/Download/), other Android apps (like WhatsApp, Instagram, TikTok) and the native system Gallery do not show the new file automatically.

The files are technically present on disk, but they remain invisible to other apps until the user manually opens the Android system File Manager. Opening the File Manager forces a system-level ContentObserver folder scan, which finally registers the files in the Android MediaStore database.

What We Tried (And the JNI / PyJNIus Traps)

We attempted to solve this within Python code using PyJNIus (jnius) to manually trigger the Android MediaScannerConnection.scanFile() API. However, doing this from Python runs into several major JNI and Serious Python structural blocks:

1. PyJNIus Background Thread Attachment Trap

Flet events and background tasks run on Python background worker threads (like asyncio or threading loops). PyJNIus calling Java methods from a background thread fails silently or crashes unless jnius.attach_thread() is explicitly called beforehand.

import jnius
jnius.attach_thread()  # Required, but undocumented and highly prone to runtime errors
2. Changing Host Activity Class Names

To initialize MediaScannerConnection, we need the application Context. In Serious Python, finding the host activity via class lookups is brittle because class names vary between Serious Python versions:

  • Older: com.flet.serious_python_android.PythonActivity
  • Newer: com.flet.serious_python.PythonActivity
  • Fallback lookups like android.app.ActivityThread.currentApplication() frequently return null when called from Python worker threads.
3. JNI Signature Matching Failures

PyJNIus has trouble converting Python list structures to Java String[] array signatures expected by scanFile(Context, String[], String[], OnScanCompletedListener). Developers have to construct Java arrays manually via JNI reflection:

Array = autoclass('java.lang.reflect.Array')
String = autoclass('java.lang.String')
paths_arr = Array.newInstance(String, len(file_paths)) # Brittle reflection setup
4. Android 9+ Implicit Intent Blocks

Fallback intent broadcasts like android.intent.action.MEDIA_SCANNER_SCAN_FILE are ignored on Android 9+ unless explicitly targeted to the Media Provider package (-p com.android.providers.media), making shell-based workarounds highly complex and security-restricted.

Proposed Solution (Feature Request)

To make Flet a truly first-class framework for mobile development, Flet should expose a native, cross-platform media indexing API (for example, page.scan_media(path) or a new page.storage_paths.scan_file(path) service method).

How it should work under the hood:
  1. The Flet Flutter client should handle the media scanner connection natively on the Dart side.
  2. In Dart, triggering a media scan on Android is extremely simple and does not suffer from classloader or background-thread JNI issues: 
    // Dart side handler
import 'package:flutter/services.dart';
// Native MethodChannel triggers MediaScannerConnection.scanFile on the Android Activity thread
  3. By delegating this to the Flutter shell, Python developers wouldn't need to write brittle PyJNIus wrappers, deal with JNI JVM thread-attachments, or worry about changing package class names between Serious Python releases.

This feature is essential for any Flet application that downloads user-facing files (photos, videos, PDF documents, audio) to public directories on Android.

主要言語
Dart
スター
325
フォーク
46
平均マージ
14時間 53分
マージ済み PR（30日）
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

flet-dev/serious-python のほかの issue

flet-dev/serious-python の issue をすべて見る

似ている issue

Dart の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。