NOTE: Thread has been narrowed down to this issue:
Android SDK's on Appcelerator
I have been using Titanium since the very beginning and love the product. I have had a bit of a holiday from app development and now have some work to do but I have come across an issue which I just cant resolve).
I use to use Genymotion and TiShadow via the command line and that worked fine. However when I started my long absent journey it was post all the platform changes so I downloaded the Studio and everything seemed fine. However for some bizzare reason running apps from the CLI
"ti build -p android --device-id "Xperia" --shadow"
Stopped working ( iOS was fine ) so I carried on with my iOS work and then came back to Android later on. So 3 days later I am in a bit of a pickle as I appeared to have bricked my entire installation of Appcelerator ( probably 5 times over ) trying to find the issue.
So after Android not launching from either CLI or Studio it appeared it was hanging whilst running a ti build -p android - adb seemed to be fine and recognised connected devices when Genymotion was open. However I thought I will reinstall the SDK's and Studio again and see what happens. So all installed correctly however when I clicked on "Download" Android button in Studio to configure the SDK's I could select the ones I would require and then it would download them ( taking some time ) only to inform me that the update had failed or it could not find a current version, when I launched Studio again it hung and would just not load.
So after a couple more reinstalls of node, appcelerator, android SDk's I am in the same boat only now I cant even configure Android SDK's it hangs when I click settings.
I realise there is quite a lot a possibilites for this going wrong but I'm stuggling to find out where to start to diagnose the issue.
My main issue now is the I cant even build for iOS on the simulator as I get this error from the CLI.
/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/hooks/tisdk3fixes.js:160
var pd = data.result[1].options['project-dir'],
^
TypeError: Cannot read property 'options' of undefined
at cli.on.post (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/hooks/tisdk3fixes.js:160:27)
at /Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/hook.js:242:13
at /Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:689:13
at iterate (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:265:13)
at async.forEachOfSeries.async.eachOfSeries (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:284:9)
at _parallel (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:688:9)
at Object.async.series (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:710:9)
at next (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/hook.js:232:11)
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/cli/commands/build.js:28:5
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/titanium-sdk/lib/titanium.js:116:3
at Object.exports.execFile (child_process.js:821:9)
at exports.exec (child_process.js:649:18)
at async.series.cached (/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/node-appc/lib/android.js:81:4)
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:486:21
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:185:13
at iterate (/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:108:13)
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:119:25
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:187:17
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:491:34
at Object.exports.execFile (child_process.js:821:9)
at exports.exec (child_process.js:649:18)
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/node-appc/lib/android.js:68:4
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:486:21
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:185:13
at iterate (/Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:108:13)
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:119:25
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:187:17
at /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA/node_modules/async/lib/async.js:491:34
at Object.run (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/node-appc/lib/subprocess.js:59:8)
at find (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/node-appc/lib/subprocess.js:96:14)
at /Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:945:13
at Immediate.q.process (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:913:25)
at processImmediate [as _immediateCallback] (timers.js:367:17)
at Object.setImmediate (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:200:9)
at _insert (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:861:19)
at Object.q.push (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/async/lib/async.js:888:17)
at Object.findExecutable (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/node_modules/node-appc/lib/subprocess.js:113:8)
at resolveNode (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/titanium.js:97:34)
at /Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/titanium.js:74:5
at Object.<anonymous> (/Users/clarkstudios/.appcelerator/install/5.1.0/package/node_modules/appc-cli-titanium/node_modules/titanium/lib/titanium.js:80:2)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
appc info just hangs as well. I can see another reinstall is imminent but getting to the point where I kind of have no idea what I am doing.
Any help would be great.
First check your Android SDK configuration in Appcelerator studio, Go to
studio/preferance/studio/platform/Android check if your SDK path is configured in Android SDK home. Also, as you have Genymotion installed, run the "appc ti config genymotion.enabled true" and check if the Genymotion path is configured in there. If not. update the paths to the executables as needed. Reference http://docs.appcelerator.com/platform/latest/#!/guide/Installing_Genymotion
Now, Check if your SDK is Fully updated on not, Go to,
Android SDK folder/tools/android which will open Android SDK manager and check if it tells you to update and component. Update and install.
Now In Genymotion check the devices you have, if you followed the above steps, the studio should show the Genymotion emulators.
Try using Titanium SDK 5.1.2.GA with CLI 5.1.0.
Related
I trying to add device conditions in my Xcode 11 so that I can simulate a slower network connection. However, when opening Devices and Simulators window and making sure my device is selected, it says that 'No Conditions Available'
How do I make them appear?
I finally managed to fix this. It appears that you need to have a 'Network Link Conditioner' installed on your Mac (in my case Catalina) for the the option to appear in Devices and Simulator window. To install it, go to Downloads for Apple Developers and download 'Additional Tools for Xcode 11'. Once downloaded, you can find it in the Hardware folder. Interestingly, when trying to install it, I received the following error:
“Network Link Conditioner” preferences is installed with macOS and can’t be replaced.
Despite me unable to find it in preferences. Luckily there is an easy fix described in this answer.
I had the same issue. Try to install the latest system software updates (Xcode Command Line Tools in my case). It worked for me.
I don't know if I'm allowed to ask this question but I really can't figure out how to use ARCore on Android Emulated Device.
According to the official guide I'm supposed to use API 8.1 on pixel/pixel 2 device in order to run any app which uses ARCore. Sadly those emulator don't come with the support for Play Store, and without Play Store I can't Instal ARCore on the device.
The device images that come with built in Play Store can't run ARCore instead. I'm really confused about how am I supposed to test anything for ARCore in this way.
I need it to develop an app for a University program and I need to become familiar with Augmented Reality Development but I can't even get started because of this issue.
Updated: October 20, 2022.
For using ARCore Emulator, at first, you have to create a virtual device with support for AR. I'm running Android Studio Dolphin | 2021.3.1 on macOS Monterey 12.6.
I created Pixel 6 Pro virtual device:
ARCore's targetSdkVersion has been set to Android API level 33.
Here are the steps you have to make in order to get a working Emulator:
Set up Android Debug Bridge. I set up adb for Mac.
Download Google_Play_Services_for_AR_1.34.0_x86_for_emulator.apk from GitHub repository.
Run your AVD.
Type in Bash Terminal the following command (to be sure that the port is 5554):
adb devices
Result:
// emulator-5554 device
Go to the folder where Google_Play_Services_for_AR_1.34.0_x86_for_emulator.apk is located. For instance:
cd ~/Desktop
To install Emulator, type in Terminal the following line, while the virtual device is running:
adb install -r Google_Play_Services_for_AR_1.34.0_x86_for_emulator.apk
Repeat previous steps for additional AVDs you’d like to use.
Delight!
P.S.
Take it into consideration: Android Emulator does not support such ARCore APIs as: Depth API, Geospatial API or Augmented Faces API. That's because Emulator doesn't have corresponding sensors. When any of these features are enabled, the Emulator picture can't render correctly: a screen will be entirely black, although UI elements drawn on top of the Emulator picture still be rendered.
Sergei's answer was right at the time, but the version of the ARCore app in his link (v1.1.0) is now too old. The following worked for me (after many false starts):
VIRTUAL DEVICE SPECIFICATIONS
Device: Pixel API 27
System image: Oreo / API Level 27 / ABI x86 / Android 8.1 (Google Play)
LINK TO ARCORE APK:
https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-5-18091013-release/arcore-1-5-180910139-android-apk-download/download/
Download the ARCore APK to your desktop. In Android Studio, set up and then start the virtual device as specified above, open the Play Store app on it and sign in. Then drag the ARCORE APK file onto the virtual device; it should silently install. Finally, run hellosceneform on the virtual device.
Just install to emulator ARCore_1_1_x86_for_emulator.apk. Just drug to emulator. Check this link https://github.com/google-ar/arcore-android-sdk/releases/tag/v1.1.0
Hi friends I added google play service to genymotion emulator,I drag the zip files of gapps and also arm v1 to it but when I opening the emulator its getting unfortunately google play services has stopped and also when I am trying to add account in it showing loading.. can anyone tell me the solution for it.
I faced this same issue.This issue is generally due to not following order of
flashing Gapps appropriately.Being a beginner in android programming.Well, I learnt following things to keep in mind while setting up google play services:
Download the ARM Translation Installer v1.1 and drag and drop the zip file onto the running Genymotion emulator device. The ARM emulator is only needed for apps that trigger a
INSTALL_FAILED_CPU_ABI_INCOMPATIBLE
error.
You must close and restart the emulator fully before continuing.
The Google Play APK package needed is specific to the Android emulator version. You must use the corresponding Google Play Service package. Otherwise, you may notice problems with Google Play not having Internet connectivity or other strange issues.
If you are using below listed specific versions ,sometimes files you are using get corrupted.
Solution:
Check android version and apk link for gapps to be flashed:
Google Apps for Android 6.0 (see instructions for flashing)
1) (https://www.androidfilehost.com/?fid=96042739161891406 - gapps-L-4-21-15.zip)
2) (https://www.androidfilehost.com/?fid=24052804347835438 - benzo-gapps-M-20151011-signed-chroma-r3.zip)
Google Apps for Android 5.1
(https://www.androidfilehost.com/?fid=96042739161891406 -
gapps-L-4-21-15.zip)
Google Apps for Android 5.0
(https://www.androidfilehost.com/?fid=95784891001614559 -
gapps-lp-20141109-signed.zip)
Google Apps for Android 4.4.4
(https://www.androidfilehost.com/?fid=23501681358544845 -
gapps-kk-20140606-signed.zip)
Google Apps for Android 4.3
(https://www.androidfilehost.com/?fid=23060877490000124 -
gapps-jb-20130813-signed.zip)
Google Apps for Android 4.2
(https://www.androidfilehost.com/?fid=2306087749000018 -
gapps-jb-20130812-signed.zip)
Google Apps for Android 4.1
(https://www.androidfilehost.com/?fid=22979706399755082 -
gapps-jb-20121011-signed.zip)
Update or reinstall Genymotion and Virtual box :
If you are flashing all gapps apk correctly and you are still facing this issue.
You need to check which version of genymotion and virtual box you are using .Use latest version of genymotion and VB.
Uninstall Genymotion and Virtualbox :
If updating or re-installation doesn't work you need to remove old registry files hidden in your computer which are preventing you from flashing Gapps properly.Repeat steps of flashing mentioned above.
Note: Don't forgot to restart genymotion after flashing files.
Hope it helps,Cheers..Happy Coding!!!
I had the same issue and found lots of solutions available on the internet. I followed the steps given in http://www.thecrazythinkers.com/how-to-fix-unfortunately-google-play-services-has-stopped/ and got a perfect solution.
To setup Google Play Service in your genymotion follow my answer in this question, hope it will help you. Question link
I am trying to port my Windows Phone 8 app to Windows 10. I am able to build my app. When I try to deploy my app in Release x86 on a Mobile emulator I hit this error: Symbols for "ntdll.dll" could not be downloaded from Microsoft Symbol Servers
Hence I am trying to run without Debugging. In VS-2015 Debug->Start Without Debugging (in Release mode for x86), I get this error when I use Mobile Emulator:
Unable to activate Windows Store App 'XXXX'. The activation request failed with error "The app didn't start in the required time".
I created a Blank Universal Windows project. I am not sure, why VS is considering this as a Windows Store App.
I followed these steps: File->New->Project->Templates->Visual C#->Windows->Universal->Blank App(Universal Windows)
It looks like you have the Microsoft symbol server set, so the debugger is trying to download the .pdb's for all the publically available .dll's in your app to step through them. Try disabling the symbol server and some other options to get past this:
It's timing out trying to download the symbols and that's causing the debugger to time out. Also, try enabling Just My Code and see if that lets the debugger skip these binaries that you probably don't want to step through:
Last night we have released a free app in the Mac AppStore. The app didn't yet show up when searching for (parts of) the title, however, we could find it by searching for one of our existing Mac Apps and clicking through to our 'Developer Page'.
When 'buying' the app (it's actually free), the icon pops up in LaunchPad and the progress bar for downloading & installing shows. Under Snow Leopard, the icon pops into the Dock and the progress bar for downloading & installing shows.
However, in both cases, as soon as the progress bar is filled, the app directly disappears from the LaunchPad / Dock and can no longer be started.
I've checked my Applications folder, but the app is nowhere to be found. I also checked this on other systems (under user accounts that never develop in XCode), those showed the exact same problem. I've also tried downloading a few other free apps from the Mac AppStore on my own system, these downloaded and installed successfully and don't disappear.
There seems to be a problem with our app that causes this issue, but I have no idea what it could possibly be. I didn't find anyone else suffering from this problem.
First and foremost, I would love to know what causes this so we can fix it.
Secondly, I am wondering how this app ever came through Apple's review process having this issue.
Any ideas?? Thanks in advance!
An Apple Dev on the Apple Developer Forums answered this question:
Do you have a copy of that app elsewhere on the system? App Store will install it over an existing copy, whereever that copy happens to be.
A different user on my system had previously built a debug build of the app from XCode. Apparently, any downloaded versions of Mac Apps are written over those apps -- even if the old version is within the home folder of a different user on your system, any version you purchase/download from the Mac AppStore will overwrite thát version; effectively locking out the downloading user from the app that he may have just paid for.
Imho, that's a crappy way of handling 'updates'. But it's good to know our app is working fine.
Thanks for the help StilesCrisis!
Update: Apple has asked me to file a bug report for this issue, will do.
I'm developing an app on Electron, and for me problem was that I had build files in my project folder, even after I deleted the app which I installed with .dmg in Application folder. So, it seems Mac Store looks throw whole disk space and trying to find app with same app ID, and if it exists, don't rewrite it.
After deleting my .app and .pkg build from the project folder app successfully installed from Mac Store. If it will not work for you, please try to clean app related folder in these directions: ~/Library/Caches and /Library/Application Support. I did it before, and can't guarantee that removing only project build files can help you. Maybe these actions are somehow connected. And removing app build files do not work for you.