I have been trying for days to get a simple app any app made in livecode to display either on my tablet, smartphone or emulator. It just doesn't work. Here is what I have done:
I have installed my sdk and pointed livecode to it in preferences.
Picked 2.3 as my version
Check my google usb drivers and they are up to date.
I followed live code's step by step and no success. I am thinking that since I am running windows 7 not a Mac, maybe this cant be done. It seems all the developers run Mac's?
I even tried to make a .apk, It made the file but " There was a problem parsing the package" once I got it on my Galaxy tab. I made sure that I checked the box to allow programs to run on my tablet. So I am still stuck.
To see if the SDK is working correctly you could try to use the Android SDK emulator first.
Open the Android SDK Manager and select the menu Tools->Manage AVDs.
There you can create a virtual Android device and run it.
If the virtual device is running you can see the virtual device under "Development->Test Target in Livecode. Select it and either select "Test" under "Development" or press the "Test" button. Does this work?
That error message means that the operating system on your device is preventing the app from being installed. The most likely reason for this is that you haven't changed the "Allow installation of apps from Unknown Sources" setting on your Galaxy Tab. There are other reasons and solutions for this error message - to see them visit Panagiotis's excellent blog post on the LiveCode website, your error message is in the fifth example
https://livecode.com/how-to-deploy-apps-to-android-devices/
Related
When im run android studio, or run emulator for android studio with manually or with cmd, always get bluescreen.
it say "your pc ran into problem and needs to restart. we're just collecting some error info, and then we'll restart for you"
Stop code: IRQL Not Less or Equal
how can i fix it ?
im trying download another emulator and following tutorial on youtube, but it didn't work
It depends on various factor,
I happened to get this issue because of my old PC with Lesser RAM size(4GB) and to rectify it, I connected my Android phone to PC for debugging/running apps from Android Studio.
You need to enable USB Debugging in your phone for that purpose.
NOTE:
You can view this blog post I made, which addresses the same issue.
https://whysurfswim.com/2015/07/11/sick-of-your-avd-theres-a-alternate-for-it/
I had almost same problem. When I tried to install my app in emulator(Ram 8gb), my emulator crashes but kept running in background. As a result, I was unable to shut down my pc and have to disconnect power for shutting down.
use your phone for debugging your app. you can connect your phone using wifi. link here
Sometimes it happens beacause of outdated drivers, try updating your drivers to latest version, and update the windows 10 to latest version. Also try by deleteing your current emulator device and create new device by enabling software renderer. For lower end pcs like yours I would recommend to use real device instead of emulators ans use ssds for better performances.
why I am getting this error when I am trying to run my application in real device not simulator
ApplicationVerificationFailed: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ttjwEf/extracted/DSP.IOS.app : 0xe8008016 (The executable was signed with invalid entitlements.)
error MT1006: Could not install the application '/Users/macbookpro/Documents/gitProject/DSPMobileGit/DSP.Mobile/DSP.iOS/DSP.IOS/bin/iPhone/Debug/device-builds/iphone6.2-9.3.5/DSP.IOS.app' on the device 'Mohamed’s iPhone': Your code signing/provisioning profiles are not correctly configured. Probably you have an entitlement not supported by your current provisioning profile, or your device is not part of the current provisioning profile. Please check the iOS Device Log for details (error: 0xe8008016).
here steps I did to run my app
First I created project in Xcode with same bundle name and let Xcode handle Provisioning
when I tried to run in Visual studio it dosent work
Second I create manual provisioning with wild id but it dosent work
I note something each time I set my signing identity and provisioning profile , when I back to screen I find it back to none again
may be that is the reason
Using Visual Studio for Mac 2019
First, determine whether the problem is entitlements. Find tab "Deploying to Device", and look at the full message starting with
"ApplicationVerificationFailed: Failed to verify code signature of ..."
Look for:
... The executable was signed with invalid entitlements.
In that case, see https://stackoverflow.com/a/43055084/199364.
The below answer is for the other likely situation:
... no valid provisioning found for this device.
On newer versions of Visual Studio for Mac + Xamarin iOS (or Xamarin Forms, deploying to iOS):
Connect the phone to Mac via USB cable.
Popup on phone, select "Trust" this computer.
In VS, Open Info.plist.
Make sure the "Application" tab is selected at the bottom of the pane.
Select "Automatic Provisioning".
Follow the instructions.
When successful, you'll see (below "Automatic Provisioning" radio button):
Apple ID: your-apple-id-email
Team: your-company-name-or-your-developer-name
(Green checkmark) Ready to deploy app to connected device.
IMPORTANT:
Even if you have previously setup Automatic Provisioning for a different device, you still need to open Info.plist / Application tab after attaching this new device. (After doing this once per device, you can switch which device is attached, without repeating.)
If Xcode has never seen the device before, it can take MINUTES before Xcode has validated it and attached it. See following paragraph if you'd rather see Xcode giving you a message about what its doing (and spinning a busy indicator). Won't be any faster, but is more obvious that something useful might be happening. (On older Xcodes, people have reported delays up to 10-15 minutes.)
If having trouble getting it to see your phone, google for instructions to open XCode and add your phone as a device known to XCode (XCode menu Windows / Devices and Simulators / Devices tab). That is, it may be easier to first get it working under XCode, then go back to VS, disconnect and reconnect the cable to phone, try instructions above again.
Using Visual Studio (Windows) 2022
Personally, I always FIRST get the phone|tablet recognized using XCode, connecting it to Mac. See instructions above.
Then:
Connect device to PC.
Automatic Provisioning is found in YourApp.iOS / Properties / iOS Bundle Signing.
Select Team.
if it works => "Automatic provisioning completed successfully."
OPTIONAL:
Disconnect device from PC, connect it to Mac - should be listed under "Remote Devices" in VS on Windows.
TBD: Not sure why I failed to get it to be listed as a Local Device, when it was attached to PC.
I had the same issue in a Xamarin.iOS project. I found a workaround. The reason was the update from Xamarin.Swift4 package 4.0.0.1 to 4.0.0.2.
After I downgraded back to 4.0.0.1 the issue no more exist.
I created an issue report at github: https://github.com/Flash3001/Xamarin.SwiftSupport/issues/25
I just installed Android Studio (v1.4) on Ubuntu 15.04 (64) and am unable to connect to my Moto G (Android 5.0.2) to run the application I made from a tutorial.
When asked to choose a device, I get the following choice for my device:
TA9290IPXK [NULL] No, minSdk(API 14)>deviceSdk(API 1) TA9290IPXK
I already enabled USB debugging on the device. when running 'adb devices' I get " ?????????????? no permission " and after killing and restarting the adv server it displays the proper serial ID but when going back to Android Studio it still does not work.
Has anyone encountered this issue ? Can someone provide a suggestion of solution please.
An obvious reason for that error message “No, minSDK(API 14) > deviceSDK(API 1)”, which I didn´t find so far mentioned neither at StackOverflow nor by other forums:
If the AVD Manager option for a virtual device “Emulated Performance - [ ] Use Host GPU” is unchecked, the Android simulator works just on "API 1" level :-(.
So if you try to execute a standard Android app ( e.g. "API 14" level ) with this setting,
The Android desktop screen is not displayed but just black screen with “android” in white letters.
When executing “Run / Device Chooser / Choose a running device / Compatible” again, there is the error message “No, minSDK(API 14) > deviceSDK(API 1)”, if “minSDKVersion 14” is set in the project configuration file “app”.
-
Why should you ever try to run the Android simuator with unchecked option?
Well...If your Win8 or Linux computer really provides OpenGL2 graphics, you may operate the simulator with default setting “Emulated Performance - [x] Use Host GPU”.
But if your Win8 or Linux computer just provides OpenGL1 graphics, as my legacy Win8-32bit notebooks “ASUS Eee PC T101MT” and “Dell Vostro 1000” with standard Windows drivers by Microsoft, the Android Simulator crashes by the error message “APPCRASH”, “Fault Module name: libOpenglRender.dll”.
And so by unchecking the option, you can´t run Android apps requiring a usual API level ( API 14,... ) :-(.
Read this article about the incomplete rollout of OpenGL2 drivers for Win,Linux and MacOX on current and legacy computers :-(:
https://github.com/processing/processing/wiki/OpenGL-Issues
Sincerely
Rolf
Ok I found the solution
Turns out I had 2 ADB installed in different Paths and Android studio was getting one of them that was not the correctly configured. I also had not properly set up the udev rules.
Here are the step I took to get it fixed
1. Remove ADB that was installed manually
2. Modify the udev rules to add the devices (It turns out that both my Nexus 7 and Moto G were not Asus and Motorolla respectively but Google inc instead. I acquired the right Vendor ID code using "lsusb" It returns XXXX:YYYY the vendir iD is the XXXX
3. Add the location of the right adb to path ( /Sdk/platform-tools/)
4. Then rebooted all of the devices (computer and android devices) and it seems it worked.
Sorry for not giving out all the terminal lines that were entered, being novice with Ubuntu it may have been a lot more confusing than helping.
Hopefully it can help someone that is in the same situation.
You have to set to connect as camera(even after usb debugging is already enabled)
Thanks to #Jorch914
i already found the solution to this. in order to solve this one, is go to Gradle > Build.gradle(module:app) > and then change the minSdkVersion that is compatible with your phone. Hope this help! :)
I cant find information on this error anywhere. I am connecting to a brand new lumia icon (AKA lumia 929). Dev account is registered. I have attempted:
reinstalling windows phone SDK
restarting phone
restarting computer
ensured the app runs on the emulators properly. the only required capability of this app is network. Capabilities have not been changed from the defaults since the project was created. none of the manifest xml files have been touched.
ensured phone software version is up to date
ensured apphub account is valid and active
ensured the windows phone developer registration tool worked, unregistered and re-registered the phone to make sure
restarting the "ip over usb" windows service thingy
changing the platform built target to ARM or AnyCpu (no difference, same error)
tried alternate deployment methods such as windows phone power tools (the xap deploy) and I get the same error when trying to connect (so I know it's not an issue with visual studio, nor is it an issue with the app code)
I can successfully deploy separate code to a separate WP7 device (so I know it's not an issue with the computer)
tried multiple usb ports
tried two separate laptops
tried visual studio 2013 and 2012
The behavior is this:
Connect the phone via usb and unlock it
Attempt to connect to phone via windows phone power tools OR deploy an app via visual studio
System hangs for about 90 seconds and seems to time out
Error appears
I am able to view the phone contents, name it and explore it on my laptop, but when it comes time to deploy something I am stuck.
Error message is simply: 0x89371B01
What does that mean? Has anyone else run into this?
Have you checked the device drivers on your Windows 8.1 machine? It could be a driver issue with your USB drivers on the computer.
I have also found that, once you get it connected, going into the Device Manager and deleting the device from there and forcing it to reload has helped me in the past.
Out of curiosity, try running "sfc /scannow" at a command prompt on the PC. It may require admin elevation. I've seen some bizarre behaviors due to dll problems in sxs in win 8.1, wondering if this could be caused by that kind of thing.
Couple of things to try:
Have you installed the GDR3 Emulators and tried running it on the 1080p emulator? It looks like the 929 is a 1920x1080 phone and will have the latest the latest updates installed. First place to check.
Based on this feedback in another stackoverflow question it looks like someone was having a similar issue and disabling Hyper-V resolved it for him. If you disable Hyper-V and it works, try re-enabling it and see if you still have the issue.
jmshapland had the correct answer for me, with the same issue. Disabling Hyper-V did the trick! No thanks to microsoft phone dev center forum posting on the issue..
http://social.msdn.microsoft.com/Forums/wpapps/en-US/24bd3e48-e7b4-4d00-8d69-193f49989ce0/0x89731b01-error-during-deploy-to-device?forum=wpdevelop
Looks like I'll be disabling Hyper-V to test on my device, and re-enabling to work in emulator mode:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
and
dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All
OK I was able to come up with a repeatable solution for the issue. Im HOPING that by posting this I dont tempt fate and have the phone not work again!
Here are the steps I did to resolve it (not sure if all of them are necessary):
On phone, disable wireless
Connect phone to laptop
Open device manager and click to show ALL HIDDEN DEVICES (including hidden devices is important)
Uninstall ALL phone-related devices (one in portable devices, several in USB
devices) anything that mentions lumia must go
Disconnect/reboot phone
Reboot laptop (there seems to be a process keeping the port open)
I had connectivity, then I lost it, then I re-gained it using these steps and it seems to be reliable for me (so far)
I would like to know if there is a tool simillar to mymobiler for Wince 5.0 which I can use to control the device from my desktop.
I use mymobiler (v1.25) but I believe it controls only devices running on WM5 and above.
Any help would be highly apprecited as the screen of my device has stopped working.
I use MyMobiler myself when I am coding for WinCE5.0 (not very often but I do know that it works.)
In your extracted MyMobiler zip file is three versions of remote.exe.
remote.exe
remote.exe.50
remote.exe.40
The only one I have gotten to work on wince5 is remote.exe.40
Just rename the existing remote.exe file (remote.exe.wm) [you may have to click tools, folder options, and uncheck hide extensions for known file types]
Next rename remote.exe.40 to remote.exe.
After that you are good to go. Copy remote.exe to the device through activesync (xp) or WMDC (>XP) and launch it on the device. It was a bit funny connecting for me the first time - I click connect on pc, then had to click the tray icon on the device, and click connect.
Good Luck!
Link to Video Showing it Running 1
This does work, the auto-install doesn't seem to work but if you copy the remote.exe over as mentioned (any location will do), then start remote.exe, click on the MYMobiler icon in the tray and select Connect, it will attach to your PC like the WinMobile version does.
Also, check the ini files in the MyMobiler directory. There's some details on the features/options.
I can confirm that Dave and Mike's solutions work on Windows CE 7 as well.
I was getting an error with the AYGSHELL.dll library when starting My Mobile after the gun was connected.
Run Mymobiler.exe before you connect the scanner to the PC and then connect to the PC using the tray icon from the gun. No error.