I've converted a PWA website into an Android app by using https://appmaker.xyz/pwa-to-apk/ convertor.
The splash icon looks pixelated for some reason. I've tried updating the manifest.json file with the correct icon at 512x512 but changes don't seem to get reflected on the installed app.
I've uninstalled the app, installed it again and did that connected to Wifi and with the phone plugged. Nothing changes.
I'm wondering if perhaps, as I've converted the PWA into a APK now I need to release a new version of the app on Google Play Store in order to update anything regarding manifest.json.
And if not, how do I force an update on the splash icon?
In short, yes, you will need to generate a new APK and release a new version to the Play Store. The reason is that the splash icon is part of the Android application and is generated when the Android package (APK) is created.
The bad news is that, unfortunately, pwa-to-apk doesn't offer the functionality of regenerating the package, and generating a new package for the same PWA will not work since, when updating the application to the Play Store, it must be signed with the same key used to sign the original package.
The good news is that it does allow the developer to download the certificate used to sign the application. If you downloaded the certificate and took note of the key alias and passwords, you will be able to generate a new package with the same name, using the original keys.
With the key saved to your file system, the alias, store password and key password at hand, you can useBubblewrap CLI to regenerate the project. Check out the Quick Start Guide.
A few additional instructions:
When Bubblewrap ask for the Application ID, ensure you are using the same ID used on the Play Store. The id can be seen in the Play Store URL for the application. As an example, the ID for https://play.google.com/store/apps/details?id=com.appspot.pwa_directory is com.appspot.pwa_directory and you need to use this value as the application id.
When Bubblewrap ask for Key store location, type in the path to the keystore file downloaded from pwa-to-apk.
When Bubblewrap ask for Key name, use the value of the alias generated by pwa-to-apk. The alias defaults to android.
Finally, when running bubblewrap build, use the key password and store passwords provided by pwa-to-apk.
With this, Bubblewrap will generate a new package that will not only contain the updated icon, but also uses the latest and greatest libraries available.
Related
I created a progressive web app, and it works perfectly. It prompts for installation and it saves the link on the android home and it shows no url address bar.
Then I used PWA2APK (https://appmaker.xyz/pwa-to-apk/) to create an APK and deploy on play store.
Once built, I downloaded the assetlinks.json, added the certificate SHA-256 modifying the assetlinks.json in this way (I changed values):
[
{
"relation": ["delegate_permission/common.handle_all_urls"],
"target": {
"namespace": "android_app",
"package_name": "xyz.appmaker.pblx",
"sha256_cert_fingerprints": ["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","SHA256: BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
}
}
]
Then I pushed it online, and verified that www.exemple.com/.well-known/assetlinks.json show the values in the browser.
The package name is the same of the APK, and the SHA-256 is the Application signing certificate.
I also added icons, screen capture and all the necessary stuff. the total workflow is validated. So once deployed a version for an internal test, I expected it to work correctly, but it doesn't. The application is installed with a default icon, it shows the rl address bar and it has some load problems.
Did anybody experienced the same issues? How did you solve it?
Thanks.
I am part of the team that build this tool. And as for the question, this can be solved by removing SHA256 from following.
Before:
"sha256_cert_fingerprints":
["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","SHA256:
BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
After
"sha256_cert_fingerprints": ["AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA:AA","BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB:BB"]
This should fix the issues you had with the address bar.
And yes, feel free to reach out in support forum anytime. Happy to help and thanks for using PWA2APK
This is just speculation, but are you using Google Play App Signing? With Google Play App Signing the app certificate should be the one Google signs your app with, not the one you sign with to upload to Google. The documentation is here. Specifically it says, under step 3 of the "New Apps" section.
Step 3: Register your app signing key with API providers
If your app uses any APIs, you usually need to register the certificate of the key Google signs your app with for authentication purposes using the fingerprint of the certificate. Here’s where to find the certificate:
Sign in to your Play Console.
Select an app.
At the left menu, select Release management > App signing.
Copy the fingerprints (MD5, SHA-1 and SHA-256) of your app signing certificate.
If the API provider requires a different type of fingerprint, you can also download the original certificate in .der format and convert it using the transformation tools that the API provider requires.
If you get the SHA-256 as described above and put it in your JSON instead it might work.
Simply copy your sha256 key from play console and paste after your original key in "sha256_cert_fingerprints" and build and deploy.
After uninstall and install the app from playstore
I've just created an app (slash command) and install it in one of my workspaces. But now I want to add the same app to another one. Is it possible without distribution to App Directory?
If you want to add you Slack app to another workspace, you can do so without going through the process of placing it on the App directory.
All you need to do is
add the ability to install your app to an workspace using OAuth 2.0.
enable public distribution
So instead of clicking "Install app to this workspace", which works great for private Slack app, which live in one workspace only, you need a script than can be called from a web browser to run the Oauth installation routine. This is usually done by adding a Slack button to your website.
You also need to enable "public distribution" for your app. Note, that is not the same as putting them on the App Directory, which requires submitting your app and undergoing a review by the Slack team.
Found the answer, in the small grey caption in the app creation form
Your app belongs to this workspace—leaving this workspace will remove your ability to manage this app. Unfortunately, this can’t be changed later.
So I've lost the keystore file for my Xamarin App when my machine crashed. After cursing myself for not saving it, I've finally accepted that I need to create new app in playstore. I know I can unpublish an app in play store. What I wanted to know is, how can I tell the user to uninstall the old app and install the new one?
You can not change the old app in any way, so you are limited in what you can do and you can not force the users to do anything...
Personally I would not un-publish the old one at first, but it really depends upon the number of users and the reviews the app has. ;-)
If your old app has a number of good to great reviews and a better than avg. rating, keep it listed until your new app is at least equal. Google Play Store ranking algorithms use rating and reviews (among other things), so do not throw this away until your new app can match the old one...
You can update the old Application description in the Play Store without changing the .apk:
Add additional content to your old description that users surfing in the store should install the new app. Remember the first 167 characters are used in search results and becomes the metacontent so do not waste those characters...
Include a Url link in your old app description to your new app in the store (play.google.com). This link will be clickable in a browser, but not in the Play App on a device
Make sure to label your new app that is a new application as new and improved-style wording will catch the eye of a user in the Play Store
Also for existing users, make sure the your installed new app icon and name are different and standout from old app (you want to visually drive people to your new app once it is on the device)
If someone installs your new old and still has your old app installed, your new app can check via the PackageManager and prompt the user to uninstall it:
var pm = Application.Context.PackageManager;
var apps = pm.GetInstalledPackages(Android.Content.PM.PackageInfoFlags.MatchAll);
foreach (var app in apps)
{
if (app.PackageName == "com.sushihangover.SomeOldApp")
{
// Display dialog to tell user to uninstall old app...
}
}
If you old app has any New News section that you can publish content to, ability to receive a remote notification and display a message to the user, etc... make use of it to notify the user that there is a brand new app available via the Play Store....
Backup those new keys ;-)
I have created a windows universal app with WinJS in visual studio 2015. Now I can run it from my visual studio. How can i make an exe file of the app so that i can distribute it to my friends? Is it only possible to upload in windows store?
I guess you're talking about an app for Windows 10!?
There are several ways to get this done.
The best way is to distribute it via Windows Store. You can hide the app there so that it is only visible to people who have the direct link to the app.
Your friends can download it directly from the store.
Another option is to provide the live IDs of your friends in the store. Then your friends get an email with a direct link.
The option you might actually be looking for which doesn't involve the store at all is to create an app package and to deploy this package to your friends. (See screenshot)
For Windows Store Apps you won't create an .exe-File, you only create .appx Packages.
Choose not to upload to the store in the next dialog. Then click create.
In the output directory you will find the *.appx file (not an *.exe)
You can distribute the appx via sideloading. Simply copy the content of the output folder to your friends's machine and run the ps1 script in Powershell. This will start the installation of the app.
Little hint: This requires your friends PCs to be enabled for sideloading.
You can set this in the settings dialog. See Screenshot.
In Current Windows Dev account, you can use Promotional codes to distribute the app to your friends instead of using side load.If the app is company app, I recommend by using sideload method.
So I am currently making an app for somebody else that lives in another state. Is there any way that I can somehow upload it (Ad-hoc?) to somewhere, and they can download it on their phone to test out themselves? I'm guessing I would have to know there ID's for their iPhone.
If this is possible, how can I do this? I currently have the $99 developer license.
First open http://www.diawi.com
Now drag and drop your project's .ipa file and your provisioning profile.
After click on send button one LINK is created
Now you can send this link to somewhere and he/she can download your application.
hope it will help you.
#Phil Scarf,
Create a Ad-hoc distribution certificate and add devices to that(using their device uuid's). Compile Xcode project using created distribution certificate. create .ipa file and send distribution certificate and .ipa file. Using both, they can install.
Below links may help you:
http://stackoverflow.com/questions/5265292/xcode-4-create-ipa-file-instead-of-xcarchive
http://stackoverflow.com/questions/4711586/how-to-make-an-ipa-file
There are some sites which gives the facility to upload the .ipa file and then returns a URL to your application and this will not be publicly visible . you just need to share this URL with your client and make sure , that the .ipa file for your app has been signed for the client device other vise it will not install on his device.
site are :- http://www.diawi.com/
https://testflightapp.com/
Of course you can provide them with test build.That is the purpose of adhoc-distribution.
You can provide build in many number of ways. .api file is the output file that you know.Jus run the code copy the api and you can share it
When creating the provision profile we add the list of devices to be tested so add the client udid there and download and install the new profile
and from the developer portal create a adhoc distribution certificate
The best way is to distribute over the air