You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deferred components allow developers to the app into multiple apk to reduce its size. This can be used to optimize the initial download and download components only on necessary but it is also mandatory for apk with more than 200MB.
This library initially looks for assets listed on flutter.assets of pubspec.yaml but does not include deferred components assets.
Without deferred components support, apps with more than 200 MB cannot use this library.
Describe the solution
Include the list of assets from every deferred compoment included on pubspec.yaml.
Additional context
Ideally this should create different classes to make clear for users in which compoment the assets is (must be load before usage). But to achive that an initial path level would be necessary even for the assets that does not use deferred compoments which would require significative changed and would generate incompatible assets.
Because of that I believe that as a first step, the library shouldn't cause any breaking changed because of deferred components, and users might be aware of deferred components by its path.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Describe the problem
Deferred components allow developers to the app into multiple apk to reduce its size. This can be used to optimize the initial download and download components only on necessary but it is also mandatory for apk with more than 200MB.
This library initially looks for assets listed on flutter.assets of pubspec.yaml but does not include deferred components assets.
Without deferred components support, apps with more than 200 MB cannot use this library.
Describe the solution
Include the list of assets from every deferred compoment included on pubspec.yaml.
Additional context
Ideally this should create different classes to make clear for users in which compoment the assets is (must be load before usage). But to achive that an initial path level would be necessary even for the assets that does not use deferred compoments which would require significative changed and would generate incompatible assets.
Because of that I believe that as a first step, the library shouldn't cause any breaking changed because of deferred components, and users might be aware of deferred components by its path.
Code of Conduct
The text was updated successfully, but these errors were encountered: