I'm using unity android, and I'm trying to upload my app.
It's a 80Mo app, so I had to split it.
Here is how I set up the Other Settings in player prefs (unity3d):
Bundle identifier: com.CompanyName.APKName (that's an example obviously )
Bundle Version: 1.0
Bundle Version Code: 1
Minimum API: (lowest) 2.0.1
Device filter: Armv7 only
Install Location: Prefer Extern
Graphics Level: OpenGL ES 2.0
Internet: Auto
Write Access: Internal only
API: .NET 2.0 subs
The product name is different than the APK name.
My files are named:
- APK: APKName
- Expansion file: main.1.com.CompanyName.APKName
In the build settings, nothing is changed (Development Build is still False).
(I'm not using a patch file).
My problem is that when I upload the APK Expansion file, it gets stuck on "processing". Apparently it's an internal error that occurs, and google play is failing the upload but doesn't display anything on the screen. I've been trying to upload that for days now and I can't find anything that helps online.
EDIT: On chrome I get stuck to processing and with firefox, I get stuck to 99%...
I've see theses post StackOveflow post 1 StackOverflow post2 but nothing changes for me.
I'm following this tutorial: tutorial unity to google play
EDIT: I can't access my app through the old console... I get the following message:"Failed to load application list. Try again later."
Thanks for the help
Boris
Ok I did it!!!
I had to create another version of my app with a higher version number. Then I went to the old console, as my app wasn't accessible through the old console I had to upload again my first APK by clicking on upload apk. Once uploaded the old console shows an error saying that there is already an app with that package name. After closing the error message the app is accessible through the old console and therefore from there I was able to upload my version 2 (the new one) APK + main OBB. After that, from the old console, I deactivated the old version and deleted it. I went back to the new console design and this is it !!!!
Sorry for posting with a second account I'll delete the first one.
if you keep example work in you application package name you cannot upload apk into google play..
Related
I am not really a mobile developer but this project was on the board and I was interested so I took it. I made several changes to this Xamarin.forms app and published the changes to the Apple App Store successfully but I am having an issue deploying to Google Play. I may very well not understand this process so bare with me.
I have access to a developer account, our store page, and an admin user account. On the apps console page on the production tab I am editing the current release. "Releases are signed by Google Play".
In Visual Studio for Mac 2022 v17.3 the project.mobile.droid package builds successfully every time with no errors (release is selected here). The android packaging format is set to tab, which is what I want. But when I try to archive for publishing I get the error:
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets(2,2): Error XA4310: `$(AndroidSigningKeyStore)` file `C:/Users/tortis1/AppData/Local/Xamarin/Mono for Android/Keystore/prodensity/prodensity.keystore` could not be found. (XA4310) (Density.Mobile.Droid)
First thing I notice is Users/tortis1/AppData. Maybe I'm unaware of something but there is no tortis1 in my Users folder so I have no idea how to track this down. I have looked for a keystore file in the project and I could find these in the Debug folder: android_debug_keystore.flag, android_debug_keystore.flag, and debug.keystore.
I have not set up any kind of singning rules or credentials in VS for Mac. Have I skipped some step or am I missing something? If you need any further information please let me know.
I have tried working through similar questions like this: How do I generate Google Play Console upload key using Xamarin Forms? , but I can't get it to archive at all.
I'm trying to upload our RN app to Huawei AppGallery but can't seem to get past the package verification. I've manually verified app bundle according to the documentation here.
Uploading from my browser (Firefox 100.0, Win11) results in "Failed to parse the manifest file for the AAB package" error shown just after upload finished, without any processing.
I also tried uploading via API service (using this Fastlane plugin). While upload was successfully completed and shown as processing in the Packages section of AppGallery, it resulted with a similar but slightly different error "Failed to parse the app package."
Finally I attempted to upload an universal apk, but with no luck it failed with an "amp.pkgState.100" message.
I think I'm missing some required steps or critical information but after broad search on the documentation and forums, couldn't find any information or guide specific for RN apps.
Additional information:
App bundle was successfully uploaded to Google Player.
App signing is configured to be managed method in AppGallery.
Trying debug instead of release bundle didn't work neither.
App does not contain and Huawei SDK.
Other configuration is not much different from default RN app.
Screenshot of failed uploads:
After countless tries and searching, I'm now able to successfully upload app bundle. It seems like all required fields in "App information" page including screenshots must be filled before proceeding to upload app package.
I uploaded an aab to the play console and finally got it listed on the play store. This app was written in Python and Kivy, and I was able to generate the aab by first running buildozer then running the script through Android Studio by following various instructions around the net.
I can download an apk from the play console which is generated from the aab, and it works just fine. However, when I install the app from the play store it closes as soon as it opens. However, I dont get a true crash report.
This is my first real app, and I'm a little lost on how to proceed.
Questions:
Any idea what's going on here?
What's the difference between the apk generated from the play console vs whatever is installed from the play store?
How can I diagnose this issue if I don't have access to the apk with the issue?
I got it to work by using a dev version of Buildozer to create the aab instead of using Android Studio.
The instructions can be found here by scrolling down to Release Builds:
https://github.com/Android-for-Python/Android-for-Python-Users#how-to-create-a-release-bundle-aab
Use Firebase Crashlytics, it logs crashes in the firebase console. You can use it in cases you can't access the apk. It requires some setup but is pretty easy. In your case, however, I think you can see the stacktrace in Android Studio if you set no filter and manually search for your app in LogCat.
Rather than aab upload file in .apk it will properly run.It is not good scenario to use apk bcz it increase the app size.When we use aab file to upload some files are not working bcz of this crash occurs.
I want to publish my Xamarin.Forms App to Google Play Store. But when I upload the APK it gives me warning and disables roll-out option. It says we need to use Android App Bundle (.aab) format so that APK can be optimized for size and resources.
Currently, Visual Studio 2019 Archive option does not support the Android App Bundle. I have taken latest update of Visual Studio 2019 but still above format is not supported.
I googled and found some link to do this from the command prompt by modifying some settings in the Project file. But the build returns errors after couple of minutes with exit code 1.
This is frustrating as I can't publish it to Google Play Store. I have already published the iOS version of App.
Any help here will be very much appreciated.
Me and my team are currently releasing to Google Play with no problems our app as APK.
The App Boundle is a nice way to release smaller applications by delivering just what the device that downloads your application needs. The Xamarin Show published recently a video on this topic, that could be of interest for you:
https://www.youtube.com/watch?v=_IOZ0SUKZq4
Through the following images i show how we upload/publish our APK:
First, in the image below you see that APKs are still supported:
APK uploads correctly:
Then we are able to save and review the APK:
APK is uploaded with warning:
The warning states:
For now we just ignore the warning and go on to roll out:
In case that after following those steps your Start Rollout option is not yet enabled, it might be the case that you still have some other Listing Sections for your Application. After you introduce all the information required by Google, the Start Rollout option must be available.
I develop android application and when create APk from this application (with Generate Signed APK) and when install this apk in other devices not install and show me this error on phone : App not installed
how can i fix it?
This is usually caused when you have a debug apk that is signed with a different certificate and you are trying to install a release version with a different certificate. If you have a debug apk on the device try uninstalling it and try again.
For me, **disabling Google Play Protect** options from play store app worked , and i was able to get rid of the App not Installed error.
Check the play protect option available in Google Play Store Navigation menu.
android:extractNativeLibs="true"
in AndroidManifest.xml file fixed the problem for me.
<application
// ...
android:extractNativeLibs="true"
Notes: I got this error when building with App Center and all the signing was handled by app center.
For easier debugging just drag and drop the apk file in the android emulator.
Your will get a more detailed message why the app is not installed.
Previously I tried all the Play protect things and checked the build.gradle file contains no release info in signingConfigs and that there's no signingConfig in buildTypes.release just as described in the other answers from this page.
delete build folder from your project and then build project again.. working for me
File an appeal with Google Play Protect
Proper way to create URL to download your APK file
You need to make a direct link to download application, not to a drive.
First, I uploaded my application on google drive and shared the link.
after submitting the apeal I instantly received a mail
Hi
You recently submitted an appeal for an app with Google Play Protect.
The link you have provided does not lead to an APK file or the file is
corrupted. Please submit a new appeal and check that you are providing
the link to the correct APK file.
Thank You, Google Play Protect Team
Upload your APK file to dropbox (didn't try any other platform)
Get sharable link (link setting should be Anyone with this link can view the file.)
Your link will something like this https://www.dropbox.com/s/xxxxxxxxxx/ApplicationName.apk?dl=0
Change the ending apk?dl=0 to apk?dl=1 (Changing it to 0 will make the link to direct download the APK, try it yourself and see.)
Your new link should be like this https://www.dropbox.com/s/xxxxxxxxxx/ApplicationName.apk?dl=1
Use any URL Shortner
Your acceptable link is ready
If you don't know what is your Application package name, then go to your AndroidManifest.xml
There will be line package="com.example.MyApplication"
After submitting it if everything goes correct you may receive a mail instantly from Google
Hi
You recently submitted an appeal for an app with Google Play Protect.
We have successfully received the appeal for your app. Our team will
review the app and any information you have provided.
Thank You, Google Play Protect Team
Don't expect any other reply from Google Play Protect Team, In my case, I didn't receive any mail, But the issue was solved, After a 2-3 business day the issue was fixed while installing the application I no longer received the Blocked by Play Protect warning. and App not installed
I know this is an old thread, but I have had the same "App not installed" issue that I have been struggling with, this is how I solved it.
Connect your device to your computer, and just before you start installing the app, run this command from commandline:
adb logcat > logcat.txt
And stop it right after you get the "App not installed" message. (Ctrl + c).
The reason for starting and stopping it just around the install process is because logcat is very "chatty".
Have a look in the generated text-file to find the error. It can be like finding the needle in a haystack, but I found my error just before "packageinstaller.InstallFailed" log-line.
The error looked like this:
10-10 21:36:43.402 1549 1940 E NativeLibraryHelper: Library 'libjsc.so' is not page-aligned - will not be able to open it directly from apk.
10-10 21:36:43.402 1549 1940 W NativeHelper: Failure copying native libraries [errorCode=-2]
10-10 21:36:43.403 1549 1940 E PackageInstallerSession: Commit of session 1728055717 failed: Failed to extract native libraries, res=-2
I fix this issue by correct the targetSdkVersion from build.gradle file.
My solution for this issue, I monitored the Logcat and could see the error because my app was not installed.
I received message DOWNGRADE VERSION, added a VersionCode in BuildGradle and for me it's working.