Skip to content

Repository for containing documentation, images, and videos for mobile applications. Can be referenced in README.md files.

License

Notifications You must be signed in to change notification settings

bwarring/flutter_app_documents

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 

Repository files navigation

flutter_app_documents

Repository for containing documentation, images, and videos for mobile applications. Can be referenced in README.md files.

FLUTTER PUBLISH ANDROID APK

Updating the app’s version number The default version number of the app is 1.0.0. To update it, navigate to the pubspec.yaml file and update the following line:

version: 1.0.0+1

The version number is three numbers separated by dots, such as 1.0.0 in the example above, followed by an optional build number such as 1 in the example above, separated by a +.

Both the version and the build number can be overridden in Flutter’s build by specifying --build-name and --build-number, respectively.

In Android, build-name is used as versionName while build-number used as versionCode. For more information, check out Version your app in the Android documentation.

When you rebuild the app for Android, any updates in the version number from the pubspec file will update the versionName and versionCode in the local.properties file.


Small snippet from document:

* Enter cd [project]
* Run: flutter build apk --split-per-abi
(The flutter build command defaults to --release.)
  
This command results in three APK files:

1. [project]/build/app/outputs/apk/release/app-armeabi-v7a-release.apk
2. [project]/build/app/outputs/apk/release/app-arm64-v8a-release.apk
3. [project]/build/app/outputs/apk/release/app-x86_64-release.apk

  
Removing the `--split-per-abi` flag results in a fat APK that contains your code compiled for all the target ABIs. Such APKs are larger in size than their split counterparts, causing the user to download native binaries that are not applicable to their device’s architecture.

Load one of the *.apk files listed above. Which file to load depends on what kind of processor is running on your device. If you don't know what kind of processor is running on your device, then unfortunately that system information is not available in most, if not all, device settins. The link in this section heading recommends


note     note

The kind of processor is identified in Instruction Sets property under the System tab. Select appropriate APK based on Instruction Sets value(s).

About

Repository for containing documentation, images, and videos for mobile applications. Can be referenced in README.md files.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published