Files
pluriwave/pubspec.yaml
T
FreeTLab 0ef6ce35b4 fix(assets): declare the content subdirectories so onboarding ships
Audit of the same failure family as the shrunk drawables: references by
NAME that nothing validates at compile time.

The whole onboarding and release-notes feature had never shipped. Reading
the installed APK: ZERO entries under assets/content/, while
assets/icons/alarmas/* was present. pubspec declared `assets/content/`, and
Flutter does not recurse -- naming a directory includes the files sitting
directly in it, never its subdirectories. Every content file lives in one
(onboarding/, updates/<locale>/), so none of them were packaged.

On the device that surfaced on every single launch:

  Unable to load asset: "assets/content/onboarding/en.md"

with the file plainly present on disk. That is why it never looked like a
packaging problem. The tell was already in the pubspec: assets/icons/alarmas/
is listed explicitly, so the rule was known once and not applied here.

All 14 content directories are now declared: onboarding/ plus updates/ for
each of the 13 locales.

The guard is a test that loads every file under assets/content/ through
rootBundle, because that is the only thing that proves an asset is declared
and will ship. A test asserting File.existsSync would have stayed green
through all of this -- the files were never missing, only unpackaged. Run
against the unfixed pubspec it fails 26 of 27; with the fix it passes.

Tests: 1165 -> 1192.
2026-08-07 13:05:59 +02:00

101 lines
2.5 KiB
YAML

name: pluriwave
description: "Radio mundial con ecualizador, reconocimiento de canciones y UI premium"
publish_to: 'none'
version: 1.2.26+148
environment:
sdk: ^3.7.0
dependencies:
flutter:
sdk: flutter
flutter_localizations:
sdk: flutter
intl: ^0.20.2
# Audio
just_audio: ^0.9.42
audio_service: ^0.18.15
audio_session: ^0.1.21
# Ya transitiva vía audio_service; directa para poder emitir
# notifyChildrenChanged (subscribeToChildren con BehaviorSubject).
rxdart: ^0.28.0
# UI
cupertino_icons: ^1.0.8
google_fonts: ^6.2.1
flutter_animate: ^4.5.2
cached_network_image: ^3.4.1
shimmer: ^3.0.0
# State
provider: ^6.1.2
# Storage
sqflite: ^2.4.1
path_provider: ^2.1.5
shared_preferences: ^2.3.4
# Network
http: ^1.2.2
# Utils
path: ^1.9.1
share_plus: ^10.1.3
file_picker: ^8.1.7
uuid: ^4.5.1
url_launcher: ^6.3.1
geolocator: ^13.0.4
geocoding: ^3.0.0
package_info_plus: ^8.3.1
# Ads (activar cuando tengamos Ad Unit IDs)
# google_mobile_ads: ^5.3.0
# In-app purchase
# in_app_purchase: ^3.2.0
# Song recognition (activar con AudD key)
# permission_handler: ^11.3.1
dev_dependencies:
flutter_test:
sdk: flutter
flutter_lints: ^5.0.0
sqflite_common_ffi: ^2.3.7+1
flutter:
generate: true
uses-material-design: true
assets:
- assets/images/
- assets/icons/
- assets/icons/alarmas/
- assets/audio/
- assets/mockups/
- assets/generated/
# Flutter NO recurse: declarar 'assets/content/' incluye solo los
# ficheros sueltos de esa carpeta, nunca los de sus subcarpetas. Todo
# el contenido vive en subcarpetas, asi que NADA de esto viajaba en el
# APK -- verificado abriendo el binario instalado: cero entradas de
# assets/content. El onboarding reventaba en cada arranque con
# 'Unable to load asset: assets/content/onboarding/en.md' aunque el
# fichero existe en disco. Mismo fallo de familia que los drawables
# resueltos por nombre: referencia sin validacion en compilacion.
- assets/content/
- assets/content/onboarding/
- assets/content/updates/ar/
- assets/content/updates/bn/
- assets/content/updates/de/
- assets/content/updates/en/
- assets/content/updates/es/
- assets/content/updates/fr/
- assets/content/updates/hi/
- assets/content/updates/id/
- assets/content/updates/it/
- assets/content/updates/ja/
- assets/content/updates/pt/
- assets/content/updates/ru/
- assets/content/updates/zh/