Android downloaded files missing

In other words, because Unity HUB fails as a download manager for some of us, I, like others, am forced to use the Installer instead which works perfectly fine to download that multiple GB of filess, but the NDK is missing from the Android package downloaded with said Installer.

Try something else". To be honest, this wasn't happening when i was using Unity X and only started to happens with Unity I can only build the Android Apk with mono right now, which seems to broke my game by forcefully removing some key codes out of the game that result in button missing parts of their codes.

I can't build using il2cpp backend because it now requires a NDK that is not coming with Unity anymore. I have been trying to find a solution for the past few days and I'll be missing the GDWC because of this. Thanks Unity for your lack of understanding.

DaseinPhaos , TymNetwork , himanshuaneja99 and 5 others like this. Joined: Dec 29, Posts: Same issue here. As I have several projects different teams I have several Unity installs. The Hub shows that some of them have add ons. Others do not, and hub will NOT add them. Is there a config file? Seriously, how hard is this to fix, it's been going on a long time. And, insult to injury, many updates to Hub, none of them fixes this. SpiralConDave , Oct 2, Joined: Feb 15, Posts: There is unfortunately no easy solution or config to override this behaviour.

We acknowledge the current limitations and UX behaviour and is something we plan to address in the future. In these cases, if the downloads fails, it would be appreciated if you can submit a defect using the Hub bug reporter so the team can trace this issue in the log files.

Thank you for your understanding, Daniel. DanielTG , Oct 3, Joined: Mar 29, Posts: 2. ShruthiB likes this. Joined: Dec 1, Posts: OmegaNemesis28 , Nov 27, Joined: Sep 3, Posts: Hi there. I have the same issue on Unity I was trying to select installed NDK manually but Unity tells that it require Is it bug or I missed something?

Litovets , Dec 2, LeonhardP , Dec 2, Joined: Aug 18, Posts: 4. UnrealTati , Dec 3, Joined: Mar 13, Posts: Dazo , Dec 4, Active 9 months ago. Viewed 25k times. Improve this question. Bappa Das 5, 3 3 gold badges 16 16 silver badges 36 36 bronze badges.

Faizaan Gagan Faizaan Gagan 1 1 gold badge 7 7 silver badges 20 20 bronze badges. What are the issues you have experienced with Android Studio, exactly? What steps did you attempt? What documentation did you read and follow? I was trying to add an emulator to the studio and it would always give errors and it was displaying the link from which it was downloading the files So I took the link and manually downloaded the zip file..

But now how to make it work with the studio Ok thanks very much I solved it myself Only the downloaded files need to be put in the sdk folder and then we create the emulator, it detects the dowloaded image — Faizaan Gagan. You may post an answer to your question and mark it as accepted so that others would know that such a question has a working solution.

Otherwise you may delete your question if you think that it does not provide any benefit to general audience that way you will remove the downvotes as well, if I am not mistaken. The method given by Faizan worked for me to the T. I have used a download manager to get the zip file and extracted it in the correct folder. When creating the virtual device just make sure you refresh the list of where system images are listed in the create new device window.

Don't click on download again. Add a comment. You don't have to build, sign, and manage multiple APKs or expansion files, and users get smaller, more optimized downloads. 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:. 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.

Note: The patch expansion file is semantically the same as the main expansion file—you can use each file any way you want. 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:. For example, suppose your APK version is and your package name is com. 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. However, some implementations of Android 6. 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. 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. 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.

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. 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.

Normally, you should only use the second patch expansion file when performing updates to the main expansion file. However, if your resources exceed the 2GB limit for the main expansion file, you can use the patch file for the rest of your assets.

To greatly reduce the amount of code you must write and ensure a good user experience during the download, we recommend you use the Downloader Library to implement your download behavior. If you build your own download service instead of using the library, be aware that you must not change the name of the expansion files and must save them to the proper storage location. Once you've finished your app development, follow the guide to Testing Your Expansion Files.

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. Note: The URL that Google Play provides for your expansion files is unique for every download and each one expires shortly after it is given to your app.

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.

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.

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. 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 use the Downloader Library, you need to download two packages from the SDK Manager and add the appropriate libraries to your app. For each library:. 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. 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:. 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 :. You can find the key in the Developer Console under your profile information. This is necessary even when testing your downloads.

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. Notice that this is the class for which you must return the name in your service's getAlarmReceiverClassName method see the previous section.

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.

For example, the sample app provided in the Apk Expansion package calls the following method in the activity's onCreate method to check whether the expansion files already exist on the device:.

In this case, each XAPKFile object holds the version number and file size of a known expansion file and a boolean as to whether it's the main expansion file. See the sample app's SampleDownloaderActivity class for details. The method returns an integer that indicates whether or not the download is required.

Possible values are:. In order to instantiate your IStub by calling CreateStub , you must pass it an implementation of the IDownloaderClient interface and your DownloaderService implementation. The next section about Receiving download progress discusses the IDownloaderClient interface, which you should usually implement in your Activity class so you can update the activity UI when the download state changes.

For example, in the previous code sample for onCreate , you can respond to the startDownloadServiceIfRequired result like this:. After the onCreate method returns, your activity receives a call to onResume , which is where you should then call connect on the IStub , passing it your app's Context.

Word, Excel, and PowerPoint and click the Recover button. You can browse for a different location to save the recovered files. Some users don't know where to view downloads on Android phone and tablet, iPad, and iPhone, here are the related instructions.

You can find all the downloaded files on Android phones and tablets in an app, called Files or My Files. The downloaded files will be listed there in chronological order. The Files or My Files app is located in the app drawer. Open the app and tap the Downloads option to view downloaded files on your phone or tablet. Unlike Android devices that save the files in one place, on the iPad and iPhone, downloaded files are not saved or stored in a single location.

They go to the corresponding apps on your iPhone or iPad. If you don't know the exact location of a file, you can use a free iOS data manager to transfer, download, and organize files on your iPhone or iPad. Daisy is the Senior editor of the writing team for EaseUS. She has been working in EaseUS for over ten years, starting from a technical writer to a team leader of the content group.

As a professional author for over 10 years, she writes a lot to help people overcome their tech troubles. Brithny is a technology enthusiast, aiming to make readers' tech life easy and enjoyable. She loves exploring new technologies and writing technical how-to tips.