I've never deployed an app before on an Android device, I've always worked on iOS devices, and it seems like you can't run/debug an app directly to the device with captive runtime, like in iOS at least.
When I click on run/debug to install the app directly to the device (I'm using IDEA) and the app gets installed, the moment the apps starts a message appears saying that I have to install Air, this didn't happen in iOS.
I wonder if I'm missing some configuration maybe.
Any ideas?
Yes this is certainly possible. It sounds like you aren't actually including the captive runtime (although I realise you think you are).
Unfortunately I don't use IDEA so I can't give you any specifics on that.
I use Flash Pro CC 2014 but it should be possible regardless of the IDE being used. Make sure you're using an upto date version of the AIR SDK.
Related
I have a lot of Android devices that all want to run the same unity app, but the refresh cycle is long to test on all of them... I have to manually update each one when a minor change is made. Currently I'm manually downloading an apk (via http) on each device.
Is there a way to deploy a unity app to lots of Android devices? I have seen reference to this being possible in Android Studio, but I don't see a way to push from Unity to Android Studio for deployment, and it's not as elegant as I would like because I will need to have about 50 devices plugged in to USB. Something over the network would be way better.
I know this can be done with (expensive) enterprise deployment systems, but it's a little impractical when I'm making a change every few minutes.
Is there a way to do this without Android Studio? My build system is OSX, but any other operating system is available. Something like a Jenkins deployment would be pretty awesome.
Anyone have an idea? I was thinking that the app itself could check via http for updates, and it could update itself. It's a bit to code, but maybe is do-able. In that case, you have to manually install the app once per device, but after that it would detect if an update is available.
Once you deploy your app to the Google Play Store via your Google Developer Console you can set up automatic updates on your devices. Every time you deploy new apk your devices will get the newest version automatically.
You can of course deploy development version so only your test users can download it.
The iOS simulator is great for testing websites locally on various Apple devices. Is there an Android equivalent?
I've tried Android studio, but I seem to have to build a device every time (unless I'm doing it wrong). I'm mainly concerned in seeing the sites in the default Chrome browser (Version 53, 59 etc).
What are you trying to test? An app or a website? If you have to "build a device" every time, you are doing it wrong.
The device emulator that you are using in android studio is the intended way to run android without a physical device. Ensure you have properly installed haxm if you are finding the emulator unbearably slow. It may help.
If you really want to try something else, you could try using the genymotion emulator. It is quite comparable to the official one though.
Is is possible to directly deploy apps on ios or android devices just for testing?
My Background:
I am currently developing iOS and Android apps but using only emulators.
Maybe you can consider me as an intermediate mobile developer but newbie in direct installation of application created.
Also, I'm afraid my iPhone or my android devices get destroyed if I will try some of the blogs tutorials found on the net.
You can try your application on actual mobile devices on both platforms.
With Android is pretty straightforward: just plugin your device to your computer's USB port. If you happen to have proper drivers for it, whenever you run your application from Eclipse IDE, you will be asked if you want to run your application directly on the device. Make sure you enable debugging on your device.
With iOS, it's also fairly easy. Just plug your iPhone/iPad/iPodTouch to your Mac, launch XCode and select device before pressing run. You might need to create a provisioning profile for it (you will need a Apple iOS Developer Account for this).
I don't think you will ruin any device just by following (and installing) tutorials from the net.
For Android: Yes, you can run the apps directly from Eclipse or Netbeans on your device, works exactly as with the emulator. To make real apps you have to test them on real devices!
You wont destroy your device. Read the Android SDK "getting started" stuff.
Can't really say about iOS though.
You can always buy a second hand cheap phone and use it.
I started developing apps in the Android emulator and I was surprised about the big difference between the emulator en a real device, which really made it worth to buy one of these terminals.
I'd like to debug a native application for Android, like, for example, the standard browser app. How can I do that, with GDB (or any other debugger). I would prefer a solution for a real device, not an emulator, but the latter is fine too, if the first option is too complicated/impossible (?). Android version I'm interested in is 2.3.4 (latest).
You would have to get the source of the application and build/debug it just like any other app.
https://android.googlesource.com/platform/packages/apps/Browser
I have an Adobe AIR desktop application, built in Flex Builder 3, that I want to run on an android device, specifically a Samsung Galaxy Tablet. I have put the application on an emulator, going through the steps of installing AIR on the emulator, packaging the application as an APK, and installing the application on the emulator. However, when I click the application, it does not run.
Here is my question: is this even possible? Can a desktop application be run on a mobile device with no changes to the code, or does it need to be converted to a mobile application before compiling? Thanks for any and all input,
T
So the answer is yes you can deploy that to a mobile device. As far as changes to the code is concerned, the answer is it depends. If it's a simple application, you shouldn't have to change anything.
Since there is no way (from what I understand) to create .apk files in Flex Builder 3, I am assuming you are going through the ADT command line to package it?
And you are following all the steps on
http://help.adobe.com/en_US/air/build/WSfffb011ac560372f-5d0f4f25128cc9cd0cb-7ffb.html
Once we have that covered, other questions would be: Are you using any modules or a framework? Any error messages?
From what I understand, Android doesn't support mx components, so depending on what you are doing there, yes you might have to change the code in order to make it work for Android.
Hopefully that helps.