Package Adoption Request: pdfx
@jeroen-meijer ci sta già lavorando.
Dal 10/6/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Package Adoption Request: pdfx (ScerIO/packages.flutter)
Package Link: https://pub.dev/packages/pdfx
Original Repository: https://github.com/ScerIO/packages.flutter
Description of the problem
The pdfx package is a widely used PDF rendering plugin, but the original repository is completely abandoned. It currently fails to build against modern Flutter tooling pipelines due to outdated native build configurations.
The main critical blockers are:
- AGP 9 Incompatibility: The Android build configuration is severely outdated and breaks under recent Android Gradle Plugin requirements.
- Swift Package Manager (SPM): The iOS side lacks proper modern SPM support, which is increasingly becoming the standard for Flutter iOS builds.
Since moving to architectural alternatives like pdfrx is not a viable option for us due to specific API dependencies, we had to fix these AGP 9 and SPM integration blockers in our own fork.
Our Contribution
We have successfully patched the native Android (AGP 9) and iOS (SPM) build layers in our own fork. It compiles and runs flawlessly in our production pipeline.
Our working fork repository:
https://github.com/qeepcologne/packages.flutter
Commitment Note
I do not have the specific domain knowledge or the time to act as a permanent maintainer for this package's core features. However, I want to deliver our working build fixes to the Flutter Community so that the organization can officially adopt the package, take over ownership on pub.dev, and unblock the ecosystem.
I am ready to open a Pull Request against a new Flutter Community branch as soon as the adoption process is initiated.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 1.7k
- Fork
- 127
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fluttercommunity/community
-
Package Proposal: com.jarvis.androidForse già presa @jeroen-meijer l’ha presa 27 giorni fa. Apertapackage proposal
fluttercommunity/community#180 · 1 assegnatario ·
-
Package Proposal: offline_sync_flutterForse di nuovo libera @jeroen-meijer l’ha presa 90 giorni fa e non c’è nessuna pull request aperta. Apertapackage proposal
fluttercommunity/community#179 · 1 commento · 1 assegnatario ·
-
Package Proposal: Docker ImageForse di nuovo libera @jeroen-meijer l’ha presa 152 giorni fa e non c’è nessuna pull request aperta. Apertapackage proposal
fluttercommunity/community#177 · 1 commento · 10 reazioni · 1 assegnatario ·
-
Package Proposal: geolocatorForse di nuovo libera @jeroen-meijer l’ha presa 282 giorni fa e non c’è nessuna pull request aperta. Apertapackage proposal
fluttercommunity/community#175 · 3 commenti · 5 reazioni · 1 assegnatario ·
-
Package Proposal: flutter_facebook_authForse di nuovo libera @jeroen-meijer l’ha presa 301 giorni fa e non c’è nessuna pull request aperta. Apertapackage proposal
fluttercommunity/community#174 · 1 assegnatario ·