Can anyone guide me how to deploy my developed android app in airwatch ??
Is there any changes in the code to be carried out before we deploy?
As per my knowledge, There is no need to change anything in your app.
You can happily deploy the app to Airwatch from
Device > Staging & Provisioning > Components > Application > Add Application
Simply generate a signed APK and upload it to AirWatch. The signed APK can be generated via cordova CLI or using Android Studio.
If there are restrictions imposed by your AirWatch Admin you may need to whitelist your app by adding its package name in the whitelist.
Remember that anyone can unzip your APK and read the files inside, since it's not compiled. So be careful to remove any relevant data before publishing.
Related
I want to create an app which can be put on a website for users to be downloaded and not to be downloaded from the play store or from the app store, like the way Dream11 does it. I have created an app that works perfectly in the debug mode in both iOS and Android and the flutter build for Android works amazing too. The 'flutter build ipa' command is causing an error-
No valid code signing certificates were found
You can connect to your Apple Developer account by signing in with your Apple ID
in Xcode and create an iOS Development Certificate as well as a Provisioning
Profile for your project by:
1- Open the Flutter project's Xcode target with
open ios/Runner.xcworkspace
2- Select the 'Runner' project in the navigator then the 'Runner' target
in the project settings
3- Make sure a 'Development Team' is selected under Signing & Capabilities > Team.
You may need to:
- Log in with your Apple ID in Xcode first
- Ensure you have a valid unique Bundle ID
- Register your device with your Apple Developer Account
- Let Xcode automatically provision a profile for your app
4- Build or run your project again
5- Trust your newly created Development Certificate on your iOS device
via Settings > General > Device Management > [your new certificate] > Trust
For more information, please visit:
https://developer.apple.com/library/content/documentation/IDEs/Conceptual/
AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html
Or run on an iOS simulator without code signing
Now I am confused whether or not to do these as I won't be releasing on the app store. Is this compulsory to do irrespective of whether the app goes to the app store or not or is there a workaround to create a build version of the app for the iOS?
You really have four options.
Release through App Store
Apple has a rather new program for releasing private apps through the App Store
Release through test flight
Create an enterprise developer account
All of these options require a developer account.
I am a little bit confused about two differents behavior and I would need some help.
I am working on an android application with App Links implemented.
I have configured my project to use a keystore for Released build version.
When I use RUN Application of Release version from Android Studio, my application will be opened as a deeplink (disambiguation dialog open when click on a link).
When I generate a SIGNED APK using the same keystore, my application is opened as an app link (direct to the app without dialog).
I have analyzed the two apps (Build APK & SIGNED APK):
RUN Application : App Link status is in ask mode when application is installed;
Signed APK : App Link status is in always mode when application is installed;
Is anyone could explain me what are the differences between RUN Application and Generate Signed APK which could lead to these two different behavior ?
Thanks
Build APK: this is testing APK you can say.in this, we don't need to use Keystore. And in this build Keys are not restricted as we use in Google maps or Facebook SDK. Not big
Signed APK: This is purely a live build you can say. we use live credentials in this build we normally won't use this build for testing.we generate Signed APK after complete testing normal APK.
BIG DIFFERENCE is that play store only accept the SIGNED APK.
So we generate signed APK normally when we have to submit our app to play store.
I am assuming you created the assetlinks.json using the release keystore.
Actually, in regards to app link, there is no difference between the RUN Application(release build) and the Signed APK.
The verification of the assetlinks.json file is done during the app installation. When you run the application from the android studio, the disambiguation dialog is showing because in the device, you might already have a pre-installed version of your app. So when you run the application, the app is not uninstalled and then installed. It just refreshes the code. So the assetlinks.json verification is not done.
So to test app links while running from android studio, first uninstall the app from the device/emulator, and then try triggering app link. The disambiguation dialog will not be shown.
You don't have to uninstall the app every time you want to run the application. But if you have changed the assetlinks.json file(at server side) or the manifest entry in manifest file, then uninstall the app and then run the application(release build) from android studio. The disambiguation dialog will not be shown.
I used flutter for both Android and IOS. I want to share both applications to the customer for testing purpose. I can export apk file by the following command for Android. I am using Android Studio.
flutter build android --profile
I can get the apk file. I just share this apk to the client. He can install it on his phone without any requirement.
After I run this command in flutter
flutter build ios --profile
It showed the error message
No valid code signing certificates were found
You can connect to your Apple Developer account by signing in with your Apple ID
in Xcode and create an iOS Development Certificate as well as a Provisioning
Profile for your project by:
1- Open the Flutter project's Xcode target with
open ios/Runner.xcworkspace
2- Select the 'Runner' project in the navigator then the 'Runner' target
in the project settings
3- In the 'General' tab, make sure a 'Development Team' is selected.
You may need to:
- Log in with your Apple ID in Xcode first
- Ensure you have a valid unique Bundle ID
- Register your device with your Apple Developer Account
- Let Xcode automatically provision a profile for your app
4- Build or run your project again
5- Trust your newly created Development Certificate on your iOS device
via Settings > General > Device Management > [your new certificate] > Trus
I have no idea how to export to get ipa file. I am new to ios development. And also I am not sure that the customer can install this ipa file on his iphone without using xcode.
Any idea for exporting customer review applications(ipa, apk) in ios development? And which softwares need for customer?
It is possible to install ipa on device over the air, without connecting to Xcode.
You can use services like Crashlytics Beta http://try.crashlytics.com/beta/ or Apple's TestFlight. First one in much easier IMO and does not require a build to be reviewed by Apple review team.
However your build must be signed at least with Ad-Hoc distribution profile and this profile must include target device's unique device identifier UDID.
This answer could be helpful for you https://stackoverflow.com/a/47053605/979822
But before that you should fix everything that was written in your error message.
I made an Android app using Android studio, deployed and ran it directly by using my mobile running Oreo.
It installed successfully. But later I tired to share the APK from my mobile to other mobiles. But none of them are able to Install it.
However, if I build the APK and share the app-debug.apk to other mobiles. It Installs successfully.
I can't build APK and share app-debug.apk it everyone.
I usually deploy it in my mobile, share APK(which used to work before)
Can anyone please help
Please excuse typos, I have typed from mobile.
There might be a signing issue. Is your app signed? The default signing is the debug signing. When you just build and deploy or run it on a connected device, it is signed by default as a debug sign.
If it is not uniquely signed, then running or installing on other devices might not be possible. Look at the app signing instruction and guide by Google, here, if you wish to distribute your app on other devices.
Another problem might be in the security authorization of other devices. Your device on which you are building has the developer options turned on. To run and install unsigned apps you'll need to activate the developer options in the device you want to run it on. Look at this link about Developer Options and how to turn it on.
by default the Android Studio packages just the needed files and installs the app in your mobile. If you share to other mobiles, the app will not install in few devices due to a few reasons like OS version, files mismatch, SHA keys mismatch, etc.
However, if you build the APK and share, the APK is equipped to be installed in any device starting from the minimum SDK version to the target SDK version.
I exported an unsigned apk file that represents a test version of my Android application. I need to distribute this to quite a few users. Is there a simple method to distribute the apk file where it will install the app? I'm trying to avoid the test users from having to download something like Astro or the sdk. Any ideas? I tried putting it out on a global web server and the file downloads but doesn't install. Thanks for the help!
From the android documentation:
The Android system will not install or run an application that is not
signed appropriately. This applies wherever the Android system is run,
whether on an actual device or on the emulator. For this reason, you
must set up signing for your application before you can run it or
debug it on an emulator or device.
So even if your users have the "Allow installing non-market apps" checked, your application will still have to be signed with at least a test key before it can be installed on a physical device.
I just put my experimental apps on the Android market with a description that says "don't install this, it won't work for you" and then give an access key to my testers.