apk expansion file not downloading from playstore - android

I am working with the sample apk expansion file downloaded from the SDk. My main expansion file is about 5 MB of size and its format is "main.1.mypackage_name" .
I uploaded my app in play store as a draft application along with the expansion file.But the issue is when the expansion file download progress,one folder is created with the package name under "Android/obb/mypackage". But there is no such file inside that folder.
Sometimes i am getting STATE_FAILED_UNLICENSED message from playstore while the download begins.
What should be the reason of this ? Anything wrong with the file name format or something ? Can anybody help me.

According Goole Play for Developers..
Please note that package names for apk files are unique and permanent,
so please choose wisely. Package names cannot be deleted or re-used in
the future. Keep in mind that if you've lost your keystore, you'll
have to publish the app with a new package name and a new key. You
should also update the description of the original app and unpublish
it.
These 2 links may help you..
Upload Applications
APK expansion Files(See Downloading the Expansion Files point here)

In the Google play Developer console there is an area to add gmail accounts which can receive license responses for testing purposes, you can also change the license response. This can be found in the 'Edit Profile' link (of the old design) or the 'Settings' (in the new design).
Hope this helps.

May help the below solutions:-
Check tag is added in manifest.xml
<uses-permission android:name="com.android.vending.CHECK_LICENSE"/>
Check added all libaray and all the classes in project:-
com.google.android.vending.licensing.
Check licence key added to the project from google play store accoount.
Check Uploaded folder with below format.
main.1.mypackage_name.obb.zip
Thanks!!

Related

Sketchware - Issues Publishing to Play Store

Using the Sketchware app and Android, I am trying to export to the Google Play store, I have to select the .json for the service account to allow it to publish the app.
However, when I try to select the .json file I have downloaded to my phone, I navigate to the directory the .json file is stored in then when I try to click on it, it is greyed out and I cannot click on it.
(P.S.: I have tried contacting Sketchware support. However, it has been over three days now and I understand due to coronavirus the response may be delayed, but I thought I would ask here if anyone has a solution.)
Why are you publishing the app directly from Sketchware to PlayStore?
You better sign the apk usin APK SIGNER app and manually upload the APK to the Play Console.
I have never used Google Play Console before, but I think this could help you:
Download your app
Using Apk Extractor (play.google.com/store/apps/details?id=com.ext.ui) is a software that will help you to get APK file from an pre installed app from Android ONLY. Using this software you can actually get an APK or Android Package that you can use while publishing app
There are many application available on Google Play that can convert your app file to AAB format.
Yes, download Apk editor and select generic key or test key (try them out, there's a few) in settings in the app, and edit the API version to the correct number. And set up a Google Play console account.
Yes, we do have a solution. Send the file to WhatsApp. Then share it from WhatsApp, choose file manager, copy the file to the place that you want, open sketchware, choose the file that you added in the JSON file, and enjoy.

Does the play store link change when uploading a new apk version

When an apk gets uploaded it generates a link for the app to the play store. I want to distribute the link and the QR code in a printable paper. If I upload a new version of the apk, does the link change and render the previous printed paper useless?
Link to application in Google Play is created from package name of your *.apk file and it never changes after update. Moreover you should never change your package name. When you use link like this:
https://play.google.com/store/apps/details?id=com.google.android.apps.maps
You can be sure that it will be permanent. You can read also very old article about things that cannot change in android application.
http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html

Where to upload Expansion File on market?

I have created expansion file with "main.1.packagename.obb" name after searching on the internet.
But I can not find any option on developer account to upload that file.
If anyone can show me screenshot of market that where to upload that file or how to thats appreciated.
I can only find this in my account. Can you please send me any link or screenshot where it actually shows how to upload.
Here is the screen which shows after upload, where is the link to upload expansion file??
I have found the solution.
In new developer console, there is no option to upload apk in first time.
But first upload dummy apk and than upload new apk will enable option to add expansion file.
So its a problem due to new dev console.
Here is the screenshot while adding 2nd apk and than expansion file

Expansion files in the new Google Play developer console

I am trying to upload my app to Google Play using the developer console. As of a week or so ago they have made it so that each app has a unique key string. You have to use the new developer console to get the key for your app. The problem is that there is apparently no way to upload an expansion file, which my app needs, in the new developer console. How then do I get my key, and get my apk with expansion file uploaded to Google Play?
Uploading an expansion file was simple with the old console all you had to do is upload it at the same time you were uploading the apk file.
What is it that I am missing?
This is a known issue of the Google developer console.
You can't add the expansion file to your first APK.
So if you are uploading for the first time, you will need to generate a second APK with a higher versionCode and upload it again. Only then, you will have the option to add your expansion file in the developer console.
From Google documentation:
Note: If you’re uploading a new app, expansion files can’t be added to the first APK file that you upload.
2018 Answer: The upload dialog for your obb file is hidden on the + sign right to your apk.
It is possible to add the expansion pack (the obb file) in the new Google Play.
When you select an application, you need to switch to "Advanced Mode". Once you've uploaded your apk file, an additional field "Expansion File" will become visible. There you have to upload your obb file. (See Screenshot)
You can now upload an expansion file in the new console, you just have to add an initial dummy .apk. In subsequent uploads, it will let you set the expansion file. You don't have to leave the new view at all. Hope that helps
On the new google play console its quite simple.
After uploading your apk it will appear under the upload section as such:
Off to your right you should see the classic three dots which will bring up this window:
Click on "Upload expansion file (.obb)" and there you go
New Developer Console preview
"The following features are not yet supported in the new Developer Console. If you need to use these features, you can click “switch back” at any time to use the old Developer Console.
•APK Expansion Files
•Multiple APK support
•Announcements
•IE9 support
•Partner channel
We’re working on adding these features and many more, so stay tuned!"
For anyone using Apportable to port your iOS builds to Android, you'll need to ensure you have "expansion_files" listed in the FEATURES of your config json file.
Without this, you won't be presented with the option to upload your OBB file(s) after uploading your APK to the Google Play Dev Console.

Apk external data, Android Expansion

I am using concept of Android Expansion which helps us to remove obstacle of 50mb limitation of Apk.
Following all the steps http://developer.android.com/guide/market/expansion-files.html
I understood that you need to follow file format like this [main|patch].<expansion-version>.<package-name>.obb and did the same.
And also Expansion files may be in (ZIP, PDF, MP4, etc.) format.
I uploaded additional expansion files while publishing apk on Google play. At the time of download apk I get all the additional in my Local(Advanced latest Device), But through code I am not able to get the expansable files of my application.
In code looking at the sampleDownloader code I came to know that it requires three parameter (int type, int expansionCode, long fileSize)
here type: main/patch expansionCode: integer value but I am just wondering how to give FileSize in Long(exact)? and second thing its show message like Download failed because the resource could not be found
Any idea?
Update
Done, all steps are shown here
Did you go through Downloading the Expansion Files? It mentions that
If the expansion files are not there with your Application downloaded from Android Market,
You have to perform Application Licensing to get your app's expansion file names, sizes, and URLs.
Perform a request using Google Play's Application Licensing to get your app's expansion file names, sizes, and URLs.
Use the URLs provided by Google Play to download the expansion files and save the expansion files.
UPDATE:
No, its not compulsory that Google Licensing only works with paid Application. There is a clear Note: defined in the Docs itself that any application may use licensing service to initiate the download of an APK expansion file. But, in that case your request will be only for expansion files and not for a check whether the user paid for the app or not.

Categories

Resources