What is fskaren bundle edition?
FSKAREN (Keyboard related) and the keyboards highlighted are gone from mine already with no effect. FSKAREN bundle edition: fskaren,lenovo,board,bundle,edition, application. FSKAREN bundle edition File Information.
An Android App Bundle is a publishing format that includes all your app’s compiled code and resources, and defers APK generation and signing to Google Play.
Google Play uses your app bundle to generate and serve optimized APKs for each device configuration, so only the code and resources that are needed for a specific device are downloaded to run your app. You no longer have to build, sign, and manage multiple APKs to optimize support for different devices, and users get smaller, more-optimized downloads.
Most app projects won’t require much effort to build app bundles that support serving optimized APKs. For example, if you already organize your app’s code and resources according to established conventions, simply build signed Android App Bundles using Android Studio or using the command line, and upload them to Google Play. Optimized APK serving then becomes an automatic benefit.
When you use the app bundle format to publish your app, you can also optionally take advantage of Play Feature Delivery, which allows you to add feature modules to your app project. These modules contain features and resources that are only included with your app based on conditions that you specify, or are available later at runtime for download Using the Play Core Library.
Game developers who publish their apps with app bundles can use Play Asset Delivery: Google Play’s solution for delivering large amounts of game assets that offers developers flexible delivery methods and high performance.
Watch the following video for an overview of why you should publish your app using Android App Bundles.
Publishing with Android App Bundles helps your users to install your app with the smallest downloads possible and increases the compressed download size limit to 150 MB. That is, when a user downloads your app, the total size of the compressed APKs required to install your app (for example, the base APK + configuration APKs) must be no more than 150 MB. Any subsequent downloads, such as downloading a feature module (and its configuration APKs) on demand, must also meet this compressed download size restriction. Asset packs do not contribute to this size limit, but they do have other size restrictions.
When you upload your app bundle, if the Play Console finds any of the possible downloads of your app or its on demand features to be more than 150 MB, you get an error.
Keep in mind, Android App Bundles do not support APK expansion (*.obb) files. So, if you encounter this error when publishing your app bundle, use one of the following resources to reduce compressed APK download sizes:
The following are the currently known issues when building or serving your app with Android App Bundles. If you experience issues that are not described below, please report a bug.
To learn more about Android App Bundles, consult the following resources.
初期の状態では、プリインストールされている日本語入力アプリ「FSKAREN」を使用して日本語入力ができるようになっています。 ただし、キーボードの設定で「FSKAREN」の利用が無効になっている場合、日本語入力ができないことがあります。
以下の操作手順を行い、「FSKAREN」の利用を有効に設定してください。
Google Play requires that the compressed APK that users download be no more than 100MB. For most apps, this is plenty of space for all the app's code and assets. However, some apps need more space for high-fidelity graphics, media files, or other large assets. Previously, if your app's compressed download size exceeded 100MB, you had to host and download the additional resources yourself when the user opens the app. Hosting and serving the extra files can be costly, and the user experience is often less than ideal. To make this process easier for you and more pleasant for users, Google Play allows you to attach two large expansion files that supplement your APK.
Google Play hosts the expansion files for your app and serves them to the device at no cost to you. The expansion files are saved to the device's shared storage location (the SD card or USB-mountable partition; also known as the "external" storage) where your app can access them. On most devices, Google Play downloads the expansion file(s) at the same time it downloads the APK, so your app has everything it needs when the user opens it for the first time. In some cases, however, your app must download the files from Google Play when your app starts.
If you'd like to avoid using expansion files and your app's compressed download size is larger than 100 MB, you should instead upload your app using Android App Bundles which allows for up to a 150 MB compressed download size. Additionally, because using app bundles defers APK generation and signing to Google Play, users download optimized APKs with only the code and resources they need to run your app. You don't have to build, sign, and manage multiple APKs or expansion files, and users get smaller, more optimized downloads.
Each time you upload an APK using the Google Play Console, you have the option to add one or two expansion files to the APK. Each file can be up to 2GB and it can be any format you choose, but we recommend you use a compressed file to conserve bandwidth during the download. Conceptually, each expansion file plays a different role:
While you can use the two expansion files any way you wish, we recommend that the main expansion file deliver the primary assets and should rarely if ever updated; the patch expansion file should be smaller and serve as a “patch carrier,” getting updated with each major release or as necessary.
However, even if your app update requires only a new patch expansion file, you still must upload a new APK with an updated versionCode in the manifest. (The Play Console does not allow you to upload an expansion file to an existing APK.)
Note: The patch expansion file is semantically the same as the main expansion file—you can use each file any way you want.
Each expansion file you upload can be any format you choose (ZIP, PDF, MP4, etc.). You can also use the JOBB tool to encapsulate and encrypt a set of resource files and subsequent patches for that set. Regardless of the file type, Google Play considers them opaque binary blobs and renames the files using the following scheme:
There are three components to this scheme:
For example, suppose your APK version is 314159 and your package name is com.example.app. If you upload a main expansion file, the file is renamed to:
When Google Play downloads your expansion files to a device, it saves them to the system's shared storage location. To ensure proper behavior, you must not delete, move, or rename the expansion files. In the event that your app must perform the download from Google Play itself, you must save the files to the exact same location.
The getObbDir() method returns the specific location for your expansion files in the following form:
For each app, there are never more than two expansion files in this directory. One is the main expansion file and the other is the patch expansion file (if necessary). Previous versions are overwritten when you update your app with new expansion files. Since Android 4.4 (API level 19), apps can read OBB expansion files without external storage permission. However, some implementations of Android 6.0 (API level 23) and later still require permission, so you will need to declare the READ_EXTERNAL_STORAGE permission in the app manifest and ask for permission at runtime as follows:
For Android version 6 and later, external storage permission needs to be requested at runtime. However, some implementations of Android do not require permission to read OBB files. The following code snippet shows how to check for read access before asking for external storage permission:
If you must unpack the contents of your expansion files, do not delete the OBB expansion files afterwards and do not save the unpacked data in the same directory. You should save your unpacked files in the directory specified by getExternalFilesDir(). However, if possible, it's best if you use an expansion file format that allows you to read directly from the file instead of requiring you to unpack the data. For example, we've provided a library project called the APK Expansion Zip Library that reads your data directly from the ZIP file.
Caution: Unlike APK files, any files saved on the shared storage can be read by the user and other apps.
Tip: If you're packaging media files into a ZIP, you can use media playback calls on the files with offset and length controls (such as MediaPlayer.setDataSource() and SoundPool.load()) without the need to unpack your ZIP. In order for this to work, you must not perform additional compression on the media files when creating the ZIP packages. For example, when using the zip tool, you should use the -n option to specify the file suffixes that should not be compressed: zip -n .mp4;.ogg main_expansion media_files
Most of the time, Google Play downloads and saves your expansion files at the same time it downloads the APK to the device. However, in some cases Google Play cannot download the expansion files or the user might have deleted previously downloaded expansion files. To handle these situations, your app must be able to download the files itself when the main activity starts, using a URL provided by Google Play.
The download process from a high level looks like this:
Caution: It is critical that you include the necessary code to download the expansion files from Google Play in the event that the files are not already on the device when your app starts. As discussed in the following section about Downloading the Expansion Files, we've made a library available to you that greatly simplifies this process and performs the download from a service with a minimal amount of code from you.
Here's a summary of the tasks you should perform to use expansion files with your app:
Once you've finished your app development, follow the guide to Testing Your Expansion Files.
Adding APK expansion files is a feature available when you upload your app using the Play Console. When uploading your app for the first time or updating an app that uses expansion files, you must be aware of the following rules and limitations:
In most cases, Google Play downloads and saves your expansion files to the device at the same time it installs or updates the APK. This way, the expansion files are available when your app launches for the first time. However, in some cases your app must download the expansion files itself by requesting them from a URL provided to you in a response from Google Play's app Licensing service.
The basic logic you need to download your expansion files is the following:
If your app is free (not a paid app), then you probably haven't used the app Licensing service. It's primarily designed for you to enforce licensing policies for your app and ensure that the user has the right to use your app (he or she rightfully paid for it on Google Play). In order to facilitate the expansion file functionality, the licensing service has been enhanced to provide a response to your app that includes the URL of your app's expansion files that are hosted on Google Play. So, even if your app is free for users, you need to include the License Verification Library (LVL) to use APK expansion files. Of course, if your app is free, you don't need to enforce license verification—you simply need the library to perform the request that returns the URL of your expansion files.
Note: Whether your app is free or not, Google Play returns the expansion file URLs only if the user acquired your app from Google Play.
In addition to the LVL, you need a set of code that downloads the expansion files over an HTTP connection and saves them to the proper location on the device's shared storage. As you build this procedure into your app, there are several issues you should take into consideration:
To simplify this work for you, we've built the Downloader Library, which requests the expansion file URLs through the licensing service, downloads the expansion files, performs all of the tasks listed above, and even allows your activity to pause and resume the download. By adding the Downloader Library and a few code hooks to your app, almost all the work to download the expansion files is already coded for you. As such, in order to provide the best user experience with minimal effort on your behalf, we recommend you use the Downloader Library to download your expansion files. The information in the following sections explain how to integrate the library into your app.
If you'd rather develop your own solution to download the expansion files using the Google Play URLs, you must follow the app Licensing documentation to perform a license request, then retrieve the expansion file names, sizes, and URLs from the response extras. You should use the APKExpansionPolicy class (included in the License Verification Library) as your licensing policy, which captures the expansion file names, sizes, and URLs from the licensing service..
To use APK expansion files with your app and provide the best user experience with minimal effort on your behalf, we recommend you use the Downloader Library that's included in the Google Play APK Expansion Library package. This library downloads your expansion files in a background service, shows a user notification with the download status, handles network connectivity loss, resumes the download when possible, and more.
To implement expansion file downloads using the Downloader Library, all you need to do is:
The following sections explain how to set up your app using the Downloader Library.
To use the Downloader Library, you need to download two packages from the SDK Manager and add the appropriate libraries to your app.
First, open the Android SDK Manager (Tools > SDK Manager), and under Appearance & Behavior > System Settings > Android SDK, select the SDK Tools tab to select and download:
Create a new library module for the License Verification Library and Downloader Library. For each library:
Note: The Downloader Library depends on the License Verification Library. Be sure to add the License Verification Library to the Downloader Library's project properties.
Or, from a command line, update your project to include the libraries:
With both the License Verification Library and Downloader Library added to your app, you'll be able to quickly integrate the ability to download expansion files from Google Play. The format that you choose for the expansion files and how you read them from the shared storage is a separate implementation that you should consider based on your app needs.
Tip: The Apk Expansion package includes a sample app that shows how to use the Downloader Library in an app. The sample uses a third library available in the Apk Expansion package called the APK Expansion Zip Library. If you plan on using ZIP files for your expansion files, we suggest you also add the APK Expansion Zip Library to your app. For more information, see the section below about Using the APK Expansion Zip Library.
In order to download the expansion files, the Downloader Library requires several permissions that you must declare in your app's manifest file. They are:
Note: By default, the Downloader Library requires API level 4, but the APK Expansion Zip Library requires API level 5.
In order to perform downloads in the background, the Downloader Library provides its own Service subclass called DownloaderService that you should extend. In addition to downloading the expansion files for you, the DownloaderService also:
All you need to do is create a class in your app that extends the DownloaderService class and override three methods to provide specific app details:
For example, here's a complete implementation of DownloaderService:
Notice: You must update the BASE64_PUBLIC_KEY value to be the public key belonging to your publisher account. You can find the key in the Developer Console under your profile information. This is necessary even when testing your downloads.
Remember to declare the service in your manifest file:
In order to monitor the progress of the file downloads and restart the download if necessary, the DownloaderService schedules an RTC_WAKEUP alarm that delivers an Intent to a BroadcastReceiver in your app. You must define the BroadcastReceiver to call an API from the Downloader Library that checks the status of the download and restarts it if necessary.
You simply need to override the onReceive() method to call DownloaderClientMarshaller.startDownloadServiceIfRequired().
For example:
Notice that this is the class for which you must return the name in your service's getAlarmReceiverClassName() method (see the previous section).
Remember to declare the receiver in your manifest file:
The main activity in your app (the one started by your launcher icon) is responsible for verifying whether the expansion files are already on the device and initiating the download if they are not.
Starting the download using the Downloader Library requires the following procedures:
To receive updates regarding the download progress and to interact with the DownloaderService, you must implement the Downloader Library's IDownloaderClient interface. Usually, the activity you use to start the download should implement this interface in order to display the download progress and send requests to the service.
The required interface methods for IDownloaderClient are:
Tip: For examples of these callbacks that update the download progress UI, see the SampleDownloaderActivity in the sample app provided with the Apk Expansion package.
Some public methods for the IDownloaderService interface you might find useful are:
If you decide to build your own downloader service instead of using the Google Play Downloader Library, you should still use the APKExpansionPolicy that's provided in the License Verification Library. The APKExpansionPolicy class is nearly identical to ServerManagedPolicy (available in the Google Play License Verification Library) but includes additional handling for the APK expansion file response extras.
Note: If you do use the Downloader Library as discussed in the previous section, the library performs all interaction with the APKExpansionPolicy so you don't have to use this class directly.
The class includes methods to help you get the necessary information about the available expansion files:
For more information about how to use the APKExpansionPolicy when you're not using the Downloader Library, see the documentation for Adding Licensing to Your App, which explains how to implement a license policy such as this one.
Once your APK expansion files are saved on the device, how you read your files
depends on the type of file you've used. As discussed in the overview, your
expansion files can be any kind of file you
want, but are renamed using a particular file name format and are saved to
Regardless of how you read your files, you should always first check that the external storage is available for reading. There's a chance that the user has the storage mounted to a computer over USB or has actually removed the SD card.
Note: When your app starts, you should always check whether the external storage space is available and readable by calling getExternalStorageState(). This returns one of several possible strings that represent the state of the external storage. In order for it to be readable by your app, the return value must be MEDIA_MOUNTED.
As described in the overview, your APK expansion files are saved using a specific file name format:
To get the location and names of your expansion files, you should use the getExternalStorageDirectory() and getPackageName() methods to construct the path to your files.
Here's a method you can use in your app to get an array containing the complete path to both your expansion files:
You can call this method by passing it your app Context and the desired expansion file's version.
There are many ways you could determine the expansion file version number. One simple way is to save the version in a SharedPreferences file when the download begins, by querying the expansion file name with the APKExpansionPolicy class's getExpansionFileName(int index) method. You can then get the version code by reading the SharedPreferences file when you want to access the expansion file.
For more information about reading from the shared storage, see the Data Storage documentation.
The Google Market Apk Expansion package includes a library called the APK
Expansion Zip Library (located in
The APK Expansion Zip Library includes the following classes and APIs:
If you're using your expansion files to store media files, a ZIP file still allows you to use Android media playback calls that provide offset and length controls (such as MediaPlayer.setDataSource() and SoundPool.load()). In order for this to work, you must not perform additional compression on the media files when creating the ZIP packages. For example, when using the zip tool, you should use the -n option to specify the file suffixes that should not be compressed:
zip -n .mp4;.ogg main_expansion media_files
When using the APK Expansion Zip Library, reading a file from your ZIP usually requires the following:
The above code provides access to any file that exists in either your main expansion file or patch expansion file, by reading from a merged map of all the files from both files. All you need to provide the getAPKExpansionFile() method is your app android.content.Context and the version number for both the main expansion file and patch expansion file.
If you'd rather read from a specific expansion file, you can use the ZipResourceFile constructor with the path to the desired expansion file:
For more information about using this library for your expansion files, look at the sample app's SampleDownloaderActivity class, which includes additional code to verify the downloaded files using CRC. Beware that if you use this sample as the basis for your own implementation, it requires that you declare the byte size of your expansion files in the xAPKS array.
Before publishing your app, there are two things you should test: Reading the expansion files and downloading the files.
Before you upload your app to Google Play, you should test your app's ability to read the files from the shared storage. All you need to do is add the files to the appropriate location on the device shared storage and launch your app:
Here are some reminders about handling the expansion files:
Because your app must sometimes manually download the expansion files when it first opens, it's important that you test this process to be sure your app can successfully query for the URLs, download the files, and save them to the device.
To test your app's implementation of the manual download procedure, you can publish it to the internal test track, so it's only available to authorized testers. If everything works as expected, your app should begin downloading the expansion files as soon as the main activity starts.
Note: Previously you could test an app by uploading an unpublished "draft" version. This functionality is no longer supported. Instead, you must publish it to an internal, closed, or open testing track. For more information, see Draft Apps are No Longer Supported.
One of the great benefits to using expansion files on Google Play is the ability to update your app without re-downloading all of the original assets. Because Google Play allows you to provide two expansion files with each APK, you can use the second file as a "patch" that provides updates and new assets. Doing so avoids the need to re-download the main expansion file which could be large and expensive for users.
The patch expansion file is technically the same as the main expansion file and neither the Android system nor Google Play perform actual patching between your main and patch expansion files. Your app code must perform any necessary patches itself.
If you use ZIP files as your expansion files, the APK Expansion Zip Library that's included with the Apk Expansion package includes the ability to merge your patch file with the main expansion file.
Note: Even if you only need to make changes to the patch expansion file, you must still update the APK in order for Google Play to perform an update. If you don't require code changes in the app, you should simply update the versionCode in the manifest.
As long as you don't change the main expansion file that's associated with the APK in the Play Console, users who previously installed your app will not download the main expansion file. Existing users receive only the updated APK and the new patch expansion file (retaining the previous main expansion file).
Here are a few issues to keep in mind regarding updates to expansion files:
Related Questions
No More Questions available at this moment!
