Is there a way to build several versions of the same application. The only information that differs is the name of the application, the package and a folder with auduo files embedded in the app?
I use react-native.
Build 8 apks with the same code but different name, package name and audio assets.
Related
I have a question about the file accessing process from the asset folder of android which uses play asset delivery. I have done setup with the play asset delivery for deploying my android application as the size of the app is more than 150Mb.
I followed the google documentation for setting up the play asset delivery module - install_time_asset pack module and moved my asset files to the file structure given below:
Below is the code structure I followed for accessing the files.
Earlier I was not able to access the file in the install_time_asset_pack assets- install_time1.txt so I change the setting from edit configuration to run app from bundle instead of the APK.
From this setting, I am able to access the asset folder files from both main assets and install pack assets.
Now I published the app to Google play console internal testing module for closed testing and downloaded the application from the play store application but during testing that application, I was not able to access the files from assets, what could be the possible reasons for that misbehavior?
I found the answer to this question as I was optimizing the apk size I have added the minifyEnabled true which is causing the problem at runtime as it removes a few object classes to reduce the apk size.
After removing this flag, the downloaded apk is running fine now.
I found out a copy of my app on the Google Play store - my APK with a different package name, app icon, and in-app images.
I assume the uploader used some apk tool to change these images and the package name somehow.
But how can an app with a different package name use the original's Firebase project? Afaik we need to declare allowed package names on the Firebase project console, and have a google-services file that declares that as well?
The app was developed with Flutter, don't think that matters.
I am building an android application which has combined functionalities of Native(Android-Kotlin) and React-Native.
We have a requirement to update index.android.bundle file at runtime after the user installed an application. How can I achieve this requirement?
I am having the following queries on the same.
Can I place index.android.bundle file outside of assets folder in android?
Where can I place Fonts and Drawable assets which are used by react-native functionality?
Requirement is:
After the user installing an application. If we have any updates in react-native functionality without re-publishing an application in play-store, we have to download and update the index.android.bundle file in the assets folder.
As per Android restrictions, we cannot add or change any file in assets folder at run-time/dynamically.
As we know that the extension of Android app is .APK. likewise, I want to know the app extension of android things app.
The extension for Android Things app is also .apk.
See Create a build for an Android Things product
...applications are compiled and packaged into a single file with the .apk extension (an Android application package file)
Each and every android application is bundled as an apk file. When an apk file is installed different entites (files) of the application are stored in different parts of the system. For example i have found that real player stores its files in the following places of the android file system
/data/data/com.real.RealPlayer
/data/app/com.real.RealPlayer-1.apk
/data/dalvik-cache/data#app#com.real.RealPlayer-1.apk#classes.dex
/data/system/packages.list
/data/system/packages.xml
/data/data/com.sec.android.app.twlauncher/databases/launcher.db
How can i do this for every installed application on my phone/emulator?? Is it the right way to parse apk file and find the places where all the parts of the app are stored?? Any ideas?
On normal non-rooted phones an application can see only its own files, due to security restrictions.