Our Automation QA team require a simulator build of the test app. Getting below error while building:
Is It Possible to Build and Distribute Simulator builds in AppCenter?
I have contacted Appcenter's Helpdesk. Following is their response :
You can build and distribute apps in App Center that can run on simulators and also on real devices.
For Android, if the build has been correctly signed, the APK can be installed on a real device and deployed to the Play Store. If the build has not been signed, the APK can be run on an emulator.
For iOS simulator, it is required for you to properly code sign the app. You can learn more about code signing for iOS here: https://learn.microsoft.com/en-us/appcenter/build/ios/code-signing
Then please see the steps below to set up code signing when building your app in App Center:
To sign the builds produced from a branch, enable code signing in the configuration pane and upload a provisioning profile (.mobileprovision) and a valid certificate (.p12), along with the password for the certificate.
Download the ipa file to install on a simulator.
Related
I have this error when i test ionic app on IOS device
i have adding the signing but i have the same error
i test this app on browser and emulator is working with xcode but on device ios not working this is the error
Showing Recent Issues
Signing for "MyApp" requires a development team. Select a development team in the Signing & Capabilities editor.
please someone can help me ?
first try to clean and rebuild the project again. But if it works in the browser and emulator, but not on a device. This is a symptom that you havent paid and have a valid anual license of xcode
my apk is 1.4MB but error is "This APK results in unused code and resources being sent to users. Your app could be smaller if you used the Android App Bundle. By not optimizing your app for device configurations, your app is larger to download and install on users' devices than it needs to be. Larger apps see lower install success rates and take up storage on users' devices."
how to fix this error
It's only a warning, not an error.
For an app that small I wouldn't worry.
It's not something that's made its way into the Ionic ecosystem yet but I heard that if you open up your project in Android Studio and then do the build through there you can create an app bundle.
I'm not totally sure that its fully tested for Ionic so you might have issues with this, but Android have published a full guide:
https://developer.android.com/guide/app-bundle#get_started
This is what they say:
Download Android Studio 3.2 or higher—it's the easiest way
to add dynamic feature modules and build app bundles.
Add support for Dynamic Delivery
by including a base module, organizing code and resources for configuration
APKs, and, optionally, adding dynamic feature modules.
Build an Android App Bundle using Android Studio.
If you're not using the IDE, you can instead build an app bundle from the
command line.
Test your Android App Bundle by using it to generate APKs that
you deploy to a device.
Enroll into app signing by Google Play.
Otherwise, you can't upload your app bundle to the Play Console.
Publish your app bundle to Google Play.
I'm trying to publish my Ionic 4 app into Play Store through Android Studio and the option to build to a signed APK is missing. I know there are similar questions to mine already asked here, but their answers are directed for previous versions. I have spent many hours searching through websites and I have typed lots of command prompt commands, such as
ionic cordova build android
and
cordova build --release android
I went to build and did the signed APK a few times, and it gave me a small window about "required updates."
I agreed, then it restarted, and after I went back to build and the option was missing! I tried installing and reinstalling Android Studio. I want to be able to create a signed APK and publish my app to Play Store. Where is the missing option? Please help me figure out how to turn on this feature in my Android Studio version 3.3.2.
Thanks to CodeChanger. Run the emulator, then restart the app. The Signed APK option will appear.
My environment :
Eclipse sdk 3.7.2
Worklight pluin 5.0.5
Android sdk 2.2
First I tried a simple Hello World, everything works fine, android native project was created and I see the corresponding apk file was generated after a build and deploy.
Next I imported a sample project, successfully got it run on the test (localhost) server, able to see the expected result on the android Mobile Browser Simulator but the problem now is I am not seeing the corresponding android apk file got generated (the android native project was created). No errors on the logs, Any idea what could be the problem? How one debug such a problem.
APK will be generated under \bin\ folder once you run your app for the first time.
Connect your Android device to dev machine via USB cable (assuming you got Android SDK etc installed), right click on Android project and do Run as->Android app.
The app will be installed and started on Android device. APK will be generated in \bin folder.
In general, you don't need the device, same thing can be done with emulator.
You can also do an export on the android application project. This is what you would do if you are looking at doing some key signing. This is the way you would want to export it if you are uploading to Google play or an enterprise app store.
Keep in mind, Worklight doesn't build your .ipa, .apk, or etc. It builds you compile ready resources. It will build you the folder structure and the project layers needed to build in the corresponding Native Environment (for apple, you would export to xcode, build it, and run).
I have used Appcelerators Titanium to create an App, and was about to deploy it to my iPad for testing when i ran into some issues. When i try to install the IPA thats been generated through Titanium and Xcode, i get this error:
Can't install application
The Info.plist for application at /Users/User/Music/iTunes/iTunes Media/Mobile Applications/myapp.ipa specifies a CFBundleExecutable of myapp, which does not exist
I've spent a couple of hours messing with the certificates, but Xcode says that the certificates are fine, and the target iPad is in the provisioning profile. The provisioning profile is also installed onto the iPad. This is driving me nuts, and i can't seem to figure it out.